footon

Footon turns Claude and Codex JSONL transcripts into sanitized share links. Raw transcripts remain local. Only user and assistant prose from an explicitly approved draft can be published.

raw JSONL -> Rust draft + local scanners -> explicit approval -> Cloudflare edge rescan -> share link

The remote MCP endpoint is https://footon.dev/mcp. It uses OAuth 2.1 with passwordless email sign-in and exposes share, service-key, and sanitized remote report tools.

The application is Rust end to end. Topcoat owns route and method matching and builds the Tailwind stylesheet; workers-rs provides the Cloudflare D1, email, Turnstile, and runtime bindings. Node remains only for Wrangler packaging and deployment.

CLI

cargo install footon --locked
footon signin you@example.com
footon draft thread.jsonl --title "Public title" --output footon-draft.json
footon publish footon-draft.json
footon publish footon-draft.json --private
footon fetch https://footon.dev/s/example
footon key-create "Auth0 production" auth0-prod --scope "logs:write logs:read"
footon reports --system auth0-prod

Sign-in stores a refreshable session in the operating system credential store; normal command output never includes access or refresh tokens. Drafting makes no network request. Publishing is a separate command and refuses plain HTTP except for localhost tests. See cli/README.md for the full contract.

Public shares are free forever and readable by anyone with the link. Private shares require Pro and named Viewer or Editor access. footon fetch tries a share anonymously first, then uses the stored session only when the private share requires authentication. See docs/access-control.md for the role and billing contract.

Pro owners can issue hashed, scoped, revocable service keys for any named auth or infrastructure system. A remote system can submit bounded log summaries without giving Footon its upstream provider credential. See docs/service-keys.md for scopes, limits, report redaction, retention, and CLI examples.

Share URLs use HTTP content negotiation. Browsers receive the dense HTML reader by default. Agents can send Accept: text/markdown; footon fetch does this and writes the exact Markdown response to stdout. Explicit equal-quality HTML and Markdown preferences resolve to Markdown.

Related MCP server: agentops-mcp

OAuth migration boundary

The Rust OAuth service uses new D1 tables and the interactive scopes keys:manage, logs:read, shares:read, and shares:write. Service keys can receive only logs:read, logs:write, shares:read, and shares:write. Existing OAuth clients, authorization codes, access tokens, and refresh tokens are intentionally not migrated. Existing share rows remain in the original shares table and remain readable, including v1 share documents.

Development

npm install
npm run check
npm run dev

npm run check formats, lints, tests, and builds the complete Rust workspace. Apply D1 migrations before running a fresh local Worker or deploying:

npx wrangler d1 migrations apply footon --local

Safety boundary

The official CLI combines redact-core with independent credential, key, connection-string, path, and metadata removal. The Worker validates the exact footon.share.v2 shape and rejects remaining high-signal secrets and personal data. No scanner can prove arbitrary text is secret-free, so explicit local review remains mandatory.