agent-render

Zero Data Retention by design

Editorial technical viewer

Share artifacts in the URL, keep the server out of the payload.

The shell now supports markdown, code, diff, CSV, and JSON artifacts while keeping fragment-native sharing and static hosting constraints intact.

fully static exportcontributor-friendly shellrenderer slots ready

Protocol shape

#agent-render=v1.<codec>.<payload>

Hosting model

One route, fragment-only payloads, and a shell that stays portable across GitHub Pages and other static hosts.

Example fragments

Load a sample envelope

6 presets
markdown1,007 chars

Maintainer kickoff

1 artifact ready for fragment decode.

code335 chars

Viewer bootstrap

1 artifact ready for fragment decode.

diff646 chars

Phase 1 sample diff

1 artifact ready for fragment decode.

csv379 chars

Data export preview

1 artifact ready for fragment decode.

json605 chars

Release bundle

3 artifacts ready for fragment decode.

json302 chars

Malformed manifest

1 artifact ready for fragment decode.

Fragment inspector

Current URL state

Awaiting fragment

Add a fragment payload to start rendering artifacts.

Fragment budget

0 / 8,000

Codec

plain

Artifacts

0

Size budget0%

Hash preview

#agent-render=v1.plain.<base64url-encoded-json>

Viewer shell

Renderer staging area

No artifact is active yet. Choose a sample fragment to populate the payload inspector and viewer metadata.

markdowncodediffcsvjson

Ready for fragment decode

Choose a sample payload to populate this shell

public-safe
Add a fragment payload to start rendering artifacts.

Security posture

Payloads stay in the hash, renderers stay client-side, and artifact-specific viewers can land without changing transport semantics.

Route model

The app remains a single export-friendly route for GitHub Pages and other static hosts.

Next up

Markdown, code, diff, CSV, and JSON now share the same viewer shell and fragment contract.