Publish one Markdown document on an existing Energon instance, then open its browser link and keep it for later use. Choose the browser path if the file is on your machine, or the agent path if your agent has it, because both create the same kind of published loose file.

Publish your first document

Before you begin

Have a Markdown file ready and review its contents before publishing. You need your instance’s hub address and permission to sign in. For agent publishing, complete Connect an agent first.

Publish through your agent

Ask your connected agent to publish a file it can access:


Publish launch-brief.md on our Energon for seven days. Give me the browser link and keep the agent link for later reference.

The agent checks the instance’s retention options, publishes the document, and reports the returned link and expiry. If seven days is unavailable, choose a lifetime the host supports. You do not need to construct API requests or paste a token into the conversation.

Or upload from your browser

Open your instance’s hub and sign in.
Select Choose files and pick your Markdown file, or drop it into the upload area.
Review the staged URL and filename. Set Expiration to seven days for this example, choose Who can write, and leave Optional password empty only if anyone with the link may read it. Nothing is written while the file is staged.
Select Publish and open the returned link. Keep the link for future reference.

launch-brief.md staged with a seven-day expiration, creator-only writes, and the Publish button.

The file appears in your hub catalog whether you published it directly or through an agent.

A published launch-brief.md in the Energon hub catalog.

Open the document

The browser renders the Markdown as a readable page. The Raw link retrieves its source. An unprotected link does not require the reader to sign in to Energon.

The launch brief rendered as a document, with a Raw link.

These screenshots show a disposable local instance with a seven-day document lifetime. The public page includes the filename, size, and update time. Your host and account will differ.

Return to it later

Give the link to the same agent in a later session, or another agent that needs the document:


Read the brief at <published link> as reference and summarize the open questions. Do not change it.

Agents can fetch the public URL, supplying the share password if required, or use the authenticated API URL with their own instance token. Keep credentials separate from the document and link.

Revise or make a copy

When you want to update the published document, make the intent explicit:


Update the brief at <published link> with the new launch date. Keep its existing URL.

The agent checks write permission and replaces the existing object. Refresh the same browser link to see the result. To explore an alternative, ask for an independent copy instead; it has a new identity and its own settings.

Uploading another loose file through the hub creates a new identity. Use an agent or the API to replace an existing file at its current URL. Replacement does not extend expiry, and Energon keeps no revision history.

Publish a prototype next

Prepare a folder with index.html and its assets, building the project first if necessary. Select the folder in the hub, or ask your agent to publish the prepared output as a site. A ZIP uploaded in the hub is unpacked as a site; use the API when an archive should remain one downloadable file.

Manage shared work covers site imports, updates, and copies. Publish through the HTTP API shows the equivalent requests for scripts and integrations.