Shipping AI agents that break in production?

Prevent Claude Code’s mistakes automatically.

Better decisions at every step, with fresh evidence of what 141,440 AI builders shipped, broke, and fixed.

Read-only. Code, paths, and history stay on your machine.

What Dorsal prevents

For each: looks like · costs · with Dorsal

  1. Wrong Product

    Users don’t want it

    A failed project

    Users

  2. Bad Design

    Works sometimes

    A rewrite

    A solid design

  3. Stale Integrations

    Last month’s API

    A broken build

    This month’s API, dated

  4. Faulty Code

    A stream of bugs

    Days of rework

    Fixes with evidence

  5. Silent Failures

    Reports success, fails

    Lost users

    User trust

How Dorsal Improved a Real Product

Keelo.AI builds AI agents for enterprise clients. It checks its design decisions with Dorsal, and Dorsal reviews its pull requests.

“Always using it. It influences almost every plan stage for us.”
Founder and CEO, Keelo.AI Enterprise Agents

Keelo.AI Enterprise Agents · design decision and pull requests · 2026-08 to 2026-09

1

design decision reversed

6

pull requests reviewed

10

bugs fixed

One repo per customer, with the agents inside. Claude Code had recommended one repo per agent.

Dorsal: “the repo boundary is the ownership boundary”, from 7 records including Microsoft’s ADR-0032 (2026-07-21)

decision record 0095 · commit e114651 · prevents Bad Design

Fixed why no release could install on the Amazon Linux 2023 boxes: the path check now resolves the lib64 symlink before comparing.

Dorsal: NVIDIA garak hit the identical failure and fixed it by resolving both sides (garak #1860).

2026-09-14 · commit a47eb53 · prevents Faulty Code

The build gate now catches a broken eval it used to announce as finished. It compares failing check ids against the base, in place of the exit code.

Dorsal: TensorRT-LLM’s CI hid added regressions by exempting a whole case on a regressed base; Qwen Code compares the set of failures.

2026-09-14 · commit 531d8d98 · prevents Silent Failures

Each fix is one commit on its own branch, checked by a second agent: the proof fails before the fix and passes after. Keelo adopted some of them.

Quoted from Keelo’s decision record and the pr-fix handover.

Two steps, about a minute

Install Dorsal

Claude Code checks Dorsal before each major decision.

  1. 1

    Connect Dorsal to Claude Code

    One command, read-only, no account. The token is already in it.

    Run this in your terminal
    Preparing your secure install command…

    Preparing a temporary read-only token for the complete command…

    On your phone? Send the command to your inbox for later.

  2. 2

    Tell Claude Code when to use it

    Paste this into ~/.claude/CLAUDE.md for all your projects, or into one project’s CLAUDE.md. On Codex, use AGENTS.md.

    Add to CLAUDE.md
    ## Dorsal
    Before you commit to a decision at any of these steps, check it against Dorsal:
    - Product: what to build, and what others already shipped
    - Architecture: the design, stack, libraries and data model
    - Integrations: the current version of each API, SDK, library and model
    - Code: known failures of the libraries you touch
    - Production: how similar systems fail silently, and how they caught it
    Cite the dated records you used. If Dorsal has nothing relevant, say so and go on.
    Send Dorsal general questions only. Never code, file paths or secrets.

    Then restart Claude Code. It loads both at startup.

The spec

What a check runs on, measured

Ranked by what matters most in a check. Independence first.

LLMs between the record and Claude Code

Zero

Retrieval is deterministic. Claude Code does the judging, with your project context.

Claims that open to a source

100%

Every record links to its origin and carries its date. When the graph has nothing, Dorsal says "no record found" instead of guessing.

Freshness

24h

The graph updates daily. The date is on every record.

Records Claude Code can check

480,793

What 141,440 AI builders shipped, broke, and fixed. Sources include GitHub, official docs, arXiv, Discord, and Hacker News.

Cost of the PR #29 fix

176k tokens

2 High bugs found, reproduced, fixed on a branch and verified by a second agent, in 12.9 minutes. The web-search version of one review burned 5.4M.

Inspect the data

A live sample from the graph Claude Code queries.

253,147

GitHub releases, PRs, issues, and more

219,394

Official Docs

224,579

abstracts from Reddit, Discord, YouTube, X, arXiv, Hacker News, and more

Or just ask it something

Two steps. About a minute.

Read-only. Code, paths, and history stay on your machine.