Self-hosted publishing for agents
Your agent's work.
Ready to read.
Your agent writes the plan. Keryx gives it a home,
a shareable link and a history you can follow.
One binary · HTML in, a URL out · PDF when you need it
keryx upload ./plan.htmlA link ready for review.Keep your judgment in the loop
Make the plan worth reading.
Your agent can take on more work. You still need to understand its choices.
A long plan is easy to skim. Ask for a document that puts the options, risks and decisions where you can see them, then question it before the work begins.
Launch with a smaller first release.
Decide how much to ship, check the risk, then give the agent a clear next step.
The layout makes the decision visible before you read every detail.
Compare the scope
| Option | What ships | Trade-off |
|---|---|---|
| Focused releaseProposed | Publishing + usage docs | Earlier feedback; sharing guide follows. |
| Full release | Publishing + every guide | More complete; delays the first release. |
Check the risk
Before release, ask someone outside the project to install the binary and publish their first document using only the guide.
Release condition: a successful upload from a fresh setup.
Your decision
Ship the focused release, or wait for the full set of guides?
Make the work easier to question.
HTML gives a plan room for comparisons, diagrams and clear decisions. Keryx gives it a link you can return to. Read it, challenge it, and guide the next revision.
Why HTML works for agent output · Anthropic ↗Illustrative HTML document. Margin notes explain the design, not an in-app commenting feature.
The document stays yours
One link.
A history you can follow.
Keep improving the draft without losing what came before. Share a specific version when a decision needs a fixed reference.
Explore the publishing workflow ↗- 01
Write
Your agent creates the HTML.
- 02
Publish
Keryx gives it a shareable link.
- 03
Review & revise
You guide the next version.
Start with your next plan