Image Energon

Publish the work.
Keep it moving.

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.

One agent publishes.
Another picks it up.

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/f/k7Qm2x/rollout-plan.md

  1. 01

    Claude Code publishes

    Maya asks Claude Code to publish the rollout plan. It returns the link above, ready to open in a browser.

  2. 02

    You read. An agent references.

    Noah opens the document and gives the same link to Codex. Codex reads the source to understand the rollout.

  3. 03

    Codex revises. Same link.

    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.

Same move. Different work.

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.

  1. A document to read.

    Ordinary Markdown becomes a readable page. The same address serves the source to an agent.

    Markdown file

    zark-muckerberg.md. Headings, a table, and two Mermaid diagrams, in a short fictional story.

    You, or an agent

    Open it in a browser to read the rendered page. Fetch the same address from an agent to get the source.

    Open the documentView the source

  2. A prototype to explore.

    Prepared HTML becomes a working site. Nobody signs up to look.

    HTML prototype

    A floating Energon cube that follows the pointer and responds to touch and phone tilt.

    You

    Open it on a laptop or a phone. Move the pointer, tilt the phone, tap the cube.

    Open the prototype

  3. A package to work from.

    Files stay in their original format. The package moves through a URL. Nothing syncs.

    ZIP · two PNGs

    two-cubes.zip. Two 320 × 320 images of the cube on midnight and violet backgrounds.

    You, or an agent

    Download it in a browser, or point an agent on another machine at the address and let it fetch the package.

    Download the ZIP

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.

Your account. Your call.

Published work stays in your Cloudflare account. You choose who can write and how long it stays available.

Run it

The Worker, R2, and D1 catalog sit in your Cloudflare account. You choose what is published and when it is deleted.

Share it

Links are open by default. A share password is a shared secret, not a per-reader permission list.

Decide who writes

Creator only, or anyone with a token on your Energon. Last write wins. Reading never requires permission to edit.

Connect an agent in one step.

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.

  • Point another agent at that URL tomorrow. It can read without changing it.
Agent session · laptopMon 9:12 AM
Connect to our Energon, then publish q3-brief.md and give me its link.
To connect me, open energon.your.co/connect and enter 4821 3907. … Connected as ada@your.co. Published — anyone with the link can open it; it expires in 7 days.
requested a connection · you approved it · 90-day tokenuploaded q3-brief.md (12.1 KB)
share.your.co/ada/f/k7Qm2x/q3-brief.md
Illustrative agent session. Links serve current contents until expiry or deletion.

Public by default. You set who can write.

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.

Per link. Set when you publish. Change any time.

Share password

Open by default. Add a password when a link needs a gate.

Who can write

Creator only, or anyone with a token on this Energon. Reading is never restricted by it.

Expiration

Pick a lifetime when you publish, or never if your Energon allows it. Delete any time.

Independent copy

Duplicate to explore another direction. The copy has its own link and settings.

Per Energon. Set once by whoever runs it.

Who signs in

Cloudflare Access in front of the hub. Your IdP, your rules.

Which agents

An agent gets a token when you approve its code, or when you mint one by hand. Tokens expire and can be revoked.

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, write-policy defaults, and a platform quota. Set in one config.

Your Energon, in your Cloudflare account.

Deploy once from your own private repository. Files sit in your Cloudflare account. MIT licensed.

Just you

Your work in your own Cloudflare account, under your control and reachable from the agents and machines you use.

Your whole team

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.

Setup overview

01

Ask your agent

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.

02

Choose your settings

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.

03

Deploy and connect

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.

What stays yours

Your infrastructure

A Cloudflare Worker, R2 storage, and a D1 catalog in your account.

Your identity

Cloudflare Access gates the hub. Tokens carry your Energon’s prefix.

Your retention

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.

Want to deploy your own Energon?

MIT licensed. Requires Workers Paid. Usage charges may apply.