01
Publish
A person drops a folder or a file in the hub. An agent calls the API with ordinary files. Markdown renders as a document; a ready-to-serve folder becomes a working site.
Built for agents. Ready for people.
Agent-native publishing for documents, prototypes, and working files.
Agents publish, read, reference, and revise. People open, explore, and upload directly. Markdown renders as a document; prepared HTML renders as a working site. Permitted updates keep the same URL across sessions and agent tools.
No repo to create. No deployment pipeline to configure. No new link for every update.
How it works
One link, from first draft to reference.
Energon holds the documents, previews, and working files around your code. Code stays in git.
02
Read and reference
Open it in a browser, or hand the link to a teammate, a client, or an agent on another machine tomorrow. Links are open by default — add a share password when they shouldn’t be. Reading never requires permission to edit.
03
Revise at the same link
Ask an agent for a change and reopen the same address. Write policy decides who may replace it. Last write wins; no merges, no revision history — that stays in your repo.
You’re in control
Share with your team or the world. You set the rules.
Every link carries its own password, write policy and expiry. Every instance decides who signs in, which agents hold tokens, and how long work lives. Links are open by default so handing off is easy; a share password is a shared secret, not an ACL — work that needs per-reader permissions belongs elsewhere.
Per link
Set when you publish. Change any time.
Share password
Open by default; add a password when a link needs a gate. Energon stores only a hash.
Who can write
Only the creator, or anyone with a token on this host. Reading and referencing are never restricted by it.
Expiration
Pick a lifetime when you publish, or never if your host allows it. Delete any time; expiry is only the automatic stop.
Independent copy
Duplicate to explore another direction. The copy has its own link, owner, password and expiry.
Per instance
Set once by whoever runs the host.
Who signs in
Cloudflare Access in front of the hub, plus the email domains allowed to mint tokens. Your IdP, your rules.
Which agents
An agent gets a token only when a signed-in person approves its code — or mints one by hand. Tokens carry your prefix, expire on your schedule, and can be revoked any time.
Where content lives
Published work is served from its own hostname, separate from the hub, so a link never inherits a login session.
Retention defaults
Expiry presets, the longest allowed lifetime, the default write policy, and a platform quota — all set in one config.
Agents are the design centre
Ask your agent. Get back a link that lasts.
No hub to open, no editor to drive, no secrets to paste. Every instance ships a skill for compatible agent tools — Claude Code, Cursor, Codex, Copilot and other Agent Plugins clients. Connecting is a conversation too: the agent asks, you approve it with a one-time code while signed in, and it receives its own token — scoped to your account, expiring on your schedule, revocable any time.
- Connect by approving a code — no token to copy, no secret in your chat history
- Publish a file or a prepared site — the agent hands you the link
- Point another agent at that link tomorrow; it reads the work without changing it
- Ask for a change and the same address shows the new contents
Fork and run
Your instance, in your Cloudflare account.
Energon is self-hosted: fork the repo, deploy once, and every agent and person you work with gets one place to publish, read and revise. The instance generates its own agent skill, so connecting a new tool is an install, not a project. MIT licensed.
Just you
Your briefs, prototypes and working files on infrastructure you own, reachable from every agent and machine you use — today and next month.
Your whole team
The same instance for everyone. Teammates and their agents publish to one place, hand links across desks, and revise at the same address.
Either way, standing one up is the same three steps — and the same things stay in your hands.
Three steps
01
Fork
Fork tmchow/energon into your GitHub. Your fork becomes the marketplace your agents install from.
02
Name it
One command renders the skill for your host — its plugin, marketplace and token env are all derived from the name.
npm run skill:init -- --name bumblebee --origin https://energon.bumblebee.co03
Deploy
Configure your Cloudflare resources and deploy. Cloudflare Access gates the hub; content gets its own hostname.
npx wrangler deployFull walkthrough, including Cloudflare resources and Access policy: deploy an instance.
What stays yours
Your infrastructure
A Cloudflare Worker with isolated R2 storage and a D1 catalog, deployed to your account. You choose what to publish and share.
Your identity
Cloudflare Access gates the hub. Tokens are minted by your people and carry your instance’s prefix.
Your retention
You set the expiry presets, write-policy defaults, share-password rules and platform quota.
Run your own instance.
MIT licensed. Requires Workers Paid; usage charges may apply.
getenergon.com explains the project. It does not provide an Energon account or host your files.