Deterministic screenshot docs

Deterministic screenshot docs

docsxai

Write a flow once. Replay it forever. docsxai walks your running web app, follows written flows, and emits screenshot-rich user docs that re-render byte-identically in CI - no agent in the execution path.

Get startedAgent runbook

$ pnpm add -g docsxai

docsxai · run

# docsxai run —flow publish-post

runpublish-post4 steps, 4 annotations

# docsxai diff —fail-on warn

diffdriftnone detected

totals0 changed, sev none

# docsxai render

render.viewer/open index.html

running app

app.example.com

Publish post

publish-post.flow.yamlgoto /editorfill titleclick publishexpect toast

walk the flow

annotated doc

publish-post · step 3

Publish post

1

1Press Publish to push the post live.

replay on every change · no agent in the run

Why it exists

Screenshot docs rot the moment the UI moves. docsxai treats them as a build artifact: a written flow is the source, the rendered doc pack is the output, and a re-run is the refresh.

// execution

Deterministic CI replay

A frozen clock, pinned locale, timezone, and viewport: the same flow against the same target state produces byte-identical screenshots. Baseline the pack, gate CI on pixel-level drift with diff —fail-on warn.

// calibration

Agent calibration, any MCP host

An agent authors the flow-file once, through the Claude Code plugin or the standalone MCP server, with lint, diagnose, and actionability probes at write-time. After that, every run is agent-free: no model in the loop, no token bill per refresh.

// plugins

A plugin runtime with teeth

Publishers, renderers, lint rules, and auth strategies extend the engine through a namespaced, capability-declared, sha256-locked runtime. Confluence and Starlight ship as first-party plugins.

// output

Docs as code, rendered three ways

One doc pack, three deliveries: an interactive viewer with halos and callouts, a production Astro Starlight site, or burned-annotation PNGs pushed to Confluence as ADF. Redactions mask sensitive UI before any pixel hits disk.

Run your first flow

Read the flow-file format