agent-render

Artifact viewer

Zero-retention artifact viewer for AI outputs.

Artifact content lives in the URL fragment, so in static mode the static host does not receive artifact content on the page request.

Fragment links can still appear in browser history, screenshots, copied messages, extensions, and other places you share or run your browser.

static export5 rendererszero retention

Protocol shape

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

Why does this URL look weird?

Static boundary

The browser decodes markdown, code, diffs, CSV, and JSON locally from the fragment after the shell loads.

Source code, issues, releases, and self-hosting notes.

ProtocolPayload format docs

Fragment key, codecs, envelope fields, and size limits.

SafetySecurity page

The current security posture and zero-retention boundaries.

EcosystemOpenClaw

The agent ecosystem this viewer was built to support.

Try itLoad a sample below

Click any sample to populate the viewer from the URL hash.

Fragment inspector

Current URL state

Empty

Add a fragment payload to start rendering artifacts.

Fragment budget

0 / 8,192

Codec

plain

Artifacts

0

Hash preview

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

Viewer shell

Initialize your Artifact

Select a fragment above to render it here. Payloads stay off the host request path, but links still need care.

markdowncodediffcsvjson

Getting started

Pick a sample or paste your own content above.

No fragment in the URL yet.

Step 1

Pick a sample fragment below.

Step 2

The payload decodes client-side from the URL hash.

Step 3

The renderer displays the artifact without contacting a server.

Security

Read the security page

Fragment payloads stay out of the static host request path, but links are not secret-safe.

Read the privacy tradeoff

Hosting

Single static route. Works on any static host.