agent-render

agent-render is a fully static, zero-retention artifact viewer for AI-generated outputs.

Built for the OpenClaw ecosystem, agent-render focuses on fragment-based sharing for markdown, code, diffs, CSV, and JSON so the payload stays in the browser URL fragment instead of being sent to a server.

OpenClaw

agent-render was built to make OpenClaw agents better at sharing artifacts across chat surfaces that render markdown, diffs, and structured data poorly.

• Website: https://agent-render.com
• OpenClaw: https://openclaw.ai
• ClawdHub skill: https://clawdhub.com/skills/agent-render-linking

Status

• Markdown, code, diff, CSV, and JSON all render in the static shell
• Fragment transport supports plain, lz, deflate, and arx, with automatic shortest-fragment selection across packed/non-packed wire formats
• The arx substitution dictionary is served at /arx-dictionary.json so agents can fetch it for local compression
• The viewer toolbar copies artifact bodies to the clipboard, downloads them as files, and (for markdown) supports browser print-to-PDF
• Deployment target: static hosting, including Cloudflare Pages

Included Renderers

• markdown - GFM rendering with safe sanitization, copy/download/print flows from the shell, and premium code fences that reuse the CodeMirror viewer stack
• code - read-only CodeMirror view with line numbers, wrap toggle, syntax-tree-aware rainbow brackets, and maintained indentation markers
• diff - review-style multi-file git patch viewer with unified and split modes
• csv - parsed table view with sticky headers and horizontal overflow handling
• json - lightweight read-only tree view plus raw code view, with graceful malformed JSON fallback

Principles

• Fully static export with Next.js App Router (default product)
• Fragment-based payloads (#...) so the static host never receives artifact contents
• Public-safe naming and MIT-compatible dependencies
• Optional self-hosted mode for server-backed UUID links (see below)

Self-Hosted UUID Mode (Optional)

In addition to the default static/fragment-based product, agent-render includes an optional self-hosted server mode that stores payloads in SQLite under UUID keys.

When to use it:

• Payloads exceed the ~8 KB fragment budget
• Links are shared on platforms that mangle long URLs
• You want short, stable links like https://host/{uuid}
• Agent-driven workflows that create and manage artifacts programmatically

What it provides:

• REST API for creating, reading, updating, and deleting artifacts
• UUID-based viewer links that render the same UI as fragment links
• 24-hour sliding TTL with automatic expiry
• SQLite storage — no external database required
• Docker Compose and daemon deployment options

Quick start:

npm run build
npm run selfhosted:dev

Then create an artifact via the API and visit http://localhost:3000/{uuid}.

See docs/deployment.md for Docker Compose, daemon, and auth setup options. See skills/selfhosted-agent-render/SKILL.md for agent workflow guidance.

The self-hosted mode is an add-on. The existing static fragment-based viewer remains the default product and continues to work as-is.

Local Development

npm install
npm run dev

Local Preview

For the real export-only runtime story:

npm run build
npm run preview

Set NEXT_PUBLIC_BASE_PATH before npm run build when you want to preview a subpath deployment locally.

Contributing

• Public exported functions/components in src/lib/** and src/components/** must have a preceding /** ... */ JSDoc block.
• Internal helpers are intentionally excluded from this rule to keep documentation noise low.
• Run npm run check:public-export-docs (included in npm run lint and npm run check) before opening a PR.

Verification

npm run lint
npm run typecheck
NEXT_PUBLIC_BASE_PATH=/agent-render npm run build

The home page includes sample fragment presets for every artifact type, including a malformed JSON case for error handling.

The fragment examples are encoded with the same transport used by the app, so larger samples naturally switch to the shortest available transport.

Bundle Notes

The shell keeps first load lean and defers renderer-heavy code until needed. The remaining largest deferred dependency is the diff stack, which stays because it still delivers the strongest review-style unified/split UX for real git patches.

Docs

• docs/architecture.md - architecture and tradeoffs
• docs/payload-format.md - fragment protocol, limits, and examples
• docs/deployment.md - deployment notes (including self-hosted mode)
• docs/dependency-notes.md - major dependency and license notes
• docs/testing.md - test commands, screenshot workflow, and CI notes
• skills/selfhosted-agent-render/SKILL.md - self-hosted UUID mode skill for agents

Zero Retention

The project keeps artifact contents in the URL fragment so the static host does not receive the payload during the page request. This improves privacy for shared artifacts, but the link still lives in browser history, copied URLs, and any client-side telemetry you add later.

Zero Data Retention by design means the deployed static host does not receive artifact contents as part of the request. It does not mean the data disappears from places like browser history, copied links, screenshots, or any client-side analytics you may add later.

License

MIT