Run it
The Worker, R2, and D1 catalog sit in your Cloudflare account. You choose what is published and when it is deleted.
Markdown becomes a readable document. An HTML prototype becomes an interactive demo. People open it; agents can read and revise the source.
Agent-native publishing.
Self-hosted in your Cloudflare account.
An agent publishes Markdown. A teammate reads: A beautiful doc in the browser. An agent builds HTML prototype. A teammate plays with: Interactive demo. Local agent packages ZIP archive. Cloud agent downloads: Downloadable bundle.
In this example, a teammate opens a rollout plan and passes its link to another agent. It can use the source as a reference, or replace it when you allow writes.
share.your.co/
Maya asks Claude Code to publish the rollout plan. It returns the link above, ready to open in a browser.
Noah opens the document and gives the same link to Codex. Codex reads the source to understand the rollout.
With writes allowed, Noah asks Codex to tighten the plan. Codex replaces the source. Reopen the original link to read the update.
Illustrative agent sessions. The people, files, and links are examples.
A document to read, a prototype to explore, a package to work from. Three real links, published on the maintainer’s own Energon. Open them.
Ordinary Markdown becomes a readable page. The same address serves the source to an agent.
zark-muckerberg.md. Headings, a table, and two Mermaid diagrams, in a short fictional story.
Open it in a browser to read the rendered page. Fetch the same address from an agent to get the source.
Prepared HTML becomes a working site. Nobody signs up to look.
A floating Energon cube that follows the pointer and responds to touch and phone tilt.
Open it on a laptop or a phone. Move the pointer, tilt the phone, tap the cube.
Files stay in their original format. The package moves through a URL. Nothing syncs.
two-cubes.zip. Two 320 × 320 images of the cube on midnight and violet backgrounds.
Download it in a browser, or point an agent on another machine at the address and let it fetch the package.
Real links on share.trev.in, the maintainer’s own Energon. No expiry is set; the owner can delete them at any time. getenergon.com hosts none of these files.
Edit in your own tools. Keep code and version history in git. Energon publishes the work so people and agents can read, reference, and revise it.
Published work stays in your Cloudflare account. You choose who can write and how long it stays available.
The Worker, R2, and D1 catalog sit in your Cloudflare account. You choose what is published and when it is deleted.
Links are open by default. A share password is a shared secret, not a per-reader permission list.
Creator only, or anyone with a token on your Energon. Last write wins. Reading never requires permission to edit.
Every Energon ships a skill for Claude Code, Cursor, Codex, Copilot, and other agent plugins. You approve a one-time code. The agent gets its own token. The token acts as you and expires. You never paste a secret into chat.
Each link has its own password, write policy, and expiry. Work that needs per-reader permissions belongs in a tool with per-user access control.
Open by default. Add a password when a link needs a gate.
Creator only, or anyone with a token on this Energon. Reading is never restricted by it.
Pick a lifetime when you publish, or never if your Energon allows it. Delete any time.
Duplicate to explore another direction. The copy has its own link and settings.
Cloudflare Access in front of the hub. Your IdP, your rules.
An agent gets a token when you approve its code, or when you mint one by hand. Tokens expire and can be revoked.
Published work is served from its own hostname, separate from the hub, so a link never inherits a login session.
Expiry presets, write-policy defaults, and a platform quota. Set in one config.
Deploy once from your own private repository. Files sit in your Cloudflare account. MIT licensed.
Your work in your own Cloudflare account, under your control and reachable from the agents and machines you use.
One Energon for the team. People and their agents publish, share, and update at the same URLs.
Start with your agent. You can choose your repository, Cloudflare account, hostnames, and settings together.
Give your agent the deployment brief. It follows the installation instructions, asks for missing choices, and creates a private repository with upstream Git history if needed.
Your agent helps choose sign-in, write access, and retention settings. Use separate hub and content addresses, such as energon.your.co and share.your.co.
Your agent handles setup and verification. You sign in and approve its connection, then it publishes and checks a test file.
Follow the deployment guide, or copy the prompt for your agent.
A Cloudflare Worker, R2 storage, and a D1 catalog in your account.
Cloudflare Access gates the hub. Tokens carry your Energon’s prefix.
You set expiry presets, write-policy defaults, and platform quota.
getenergon.com explains the project. It does not provide an Energon account or host your files.
MIT licensed. Requires Workers Paid. Usage charges may apply.