Scribe

The system of record for AI-driven work

Know what your agents were asked to do, what they decided, and which commits shipped it.

A ledger is a small, structured record an agent keeps for every piece of work, from the first plan to the merge. Work survives context resets and handoffs, reviewers see the intent behind a PR, and the record stays linked to the code.

Download the ViewerSee pricing

The problem

Agents ship faster than anyone can record why.

Jira tracks tickets
It holds the request, not the agent's plan, its decisions, or which requirement each commit met.
Confluence holds documents
Written once, then stale, with no link to the code that implements them.
git records diffs
It shows what changed, not the intent or what was left out. Squash merges break the trail.
Agents forget
Long tasks span resets, forks and handoffs. Without a record, every session starts over.

How it works

One ledger per task, kept by the agent itself.

The ledger plugin opens a ledger on its own for any non-trivial task in Claude Code. Every ledger follows the same lifecycle.

  1. 01InitSets the goal and records the git commit the work starts from.
  2. 02DesignWrites requirements and acceptance checks. An approved plan is copied in word for word.
  3. 03BriefHands the next step to a fresh session or another agent, with its files, check and boundaries.
  4. 04UpdateAdds a dated log entry, rewrites the status and records the commits for that step.
  5. 05CloseWrites As built: what shipped, how it differed from the plan, what was deferred. Then archives.
STATUS.md
Current phase, next actions and open questions, kept small.
Read by: Every new agent session
LOG.md
One dated entry per step. Append-only.
Read by: People and agents searching the history
design.md
Goal, approach, requirements, acceptance checks, out of scope and As built.
Read by: Reviewers, auditors and new team members
manifest.json
A machine-readable copy, plus commits, patch IDs, branch, merge commit and PR.
Read by: CI, dashboards and integrations
An open contract

manifest.json follows a published JSON Schema. Minor versions only add fields, so CI, dashboards and your own tools can build on ledgers without depending on the plugin.

Traceable through real workflows

Commit SHAs and patch IDs at each step, and the merge commit and PR at close, so a PR still matches its ledger after a squash or rebase. The plugin only reads git.

Local by default

Ledgers live on your machine. Commit them to the repo, share a folder, or sync them to a Scribe workspace when your team is ready.

Pricing

Free where ledgers are written. Paid where teams use them.

The local tools stay free. Teams pay for the hosted services that turn ledgers into shared visibility and checks.

Community
Free for every developer, forever.

$0

  • Ledger plugin for Claude Code
  • Desktop Viewer for every project on your machine
  • Versioned manifest.json schema
  • CI gate reference design
Download the Viewer
TeamPilot open
Per seat, priced modestly next to your AI seat.

Free during the pilot

  • Everything in Community
  • Hosted ledger sync and search across repos
  • Shared workspaces and team dashboards
  • Manifest-based CI gates and PR-to-ledger linking
Join the design-partner pilot
Enterprise
Annual contract.

Contact us

  • Everything in Team
  • SSO, audit export and retention controls
  • Self-hosted option
  • Jira and Confluence sync, agentic validation
Contact us

Download

Get the Scribe Viewer.

See every ledger across your projects, with live updates as agents work. Runs offline on your machine.

Viewer for Windows
Version 0.1.0, 64-bit installer. macOS and Linux builds are coming.
Coming soon
Ledger plugin for Claude Code
Install it in Claude Code, and every non-trivial task gets a ledger.
Coming soon