agent-render

Zero Data Retention by design

Artifact viewer

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

agent-render opens markdown, code, diff, CSV, and JSON artifacts from a single static link, so someone can understand the payload without uploading it anywhere.

fully static exportproduct-minded shellrenderer slots ready

Protocol shape

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

Why it exists

Agent outputs get flattened in chat. agent-render keeps them readable, portable, and static-host friendly.

SourceBrowse the GitHub repo

Inspect the payload format, renderer shell, and deployment notes behind the static viewer.

EcosystemUse the ClawdHub skill

Help OpenClaw agents emit `agent-render` links intentionally across chat surfaces and workflows.

How to try itLoad any sample fragment below

Pick a sample, update the hash, and the viewer opens without sending the artifact body to the host.

Try it now

Make a shareable artifact link from pasted content.

Pick a format, paste the artifact, and generate a real `agent-render` URL in the browser. No backend, no upload step, no extra route.

Compression is chosen automatically through the same fragment helper used by the viewer.

Example fragments

Load a sample envelope

6 presets

Each preset uses the same fragment transport as the live product, so you can try the viewer shell with realistic payload sizes and renderer combinations in one click.

markdown790 chars

Maintainer kickoff

1 artifact ready for fragment decode.

code247 chars

Viewer bootstrap

1 artifact ready for fragment decode.

diff462 chars

Phase 1 sample diff

1 artifact ready for fragment decode.

csv299 chars

Data export preview

1 artifact ready for fragment decode.

json424 chars

Release bundle

3 artifacts ready for fragment decode.

json220 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>

What happens next

Once a fragment is present, the shell decodes the envelope in-browser, selects the active artifact, and swaps this empty state for the renderer-specific stage without changing the route model.

Viewer shell

Renderer staging area

This stage becomes the live artifact surface once a fragment is active. The payload stays in the URL hash, the route stays export-friendly, and each artifact kind can render inside the same shell.

markdowncodediffcsvjson

Ready for fragment decode

Choose a sample payload to populate this shell

public-safe

First-run flow

The live renderer stage appears here as soon as a fragment is selected.

Add a fragment payload to start rendering artifacts.

Step 1

Pick a sample fragment to update the hash in place.

Step 2

The shell decodes the envelope client-side and activates the chosen artifact.

Step 3

Artifact-specific renderers take over this stage without sending the payload to a server.

Security posture

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

Route model

The app remains a single export-friendly route for Cloudflare Pages and other static hosts, even as richer artifact viewers plug into the shell.

Supported artifacts

Markdown, code, diff, CSV, and JSON all share the same shell contract, so the homepage can explain the product before the first payload ever lands.