dorsalCustomer evidence
Get Dorsal
From real builds

Claude Code had a plan.
Dorsal changed it.

Dorsal helps you build better software by showing your coding agent what 152,134 AI builders and scientists have already learned. Updated daily.

Get Dorsal

new records added today.

What are you working on?

From first idea to final verification.

Relevant experience at every step.

  1. Product

    Discover ideas. Challenge assumptions.

  2. Design

    Compare architectures before committing.

  3. Integrations

    Check current APIs, libraries, and limits.

  4. Code

    Reuse working patterns and proven fixes.

  5. Verification

    Find what to test and how.

Three examples
02Thorsten Freitag/Dependencies

Less to maintain.
Versions pinned.

A Dorsal-backed review led Thorsten to approve a dependency cleanup. His coding agent removed 43 unnecessary packages and pinned the remaining versions.

“43 unneeded software packages removed and the rest pinned”

Thorsten’s coding-agent report

Implemented with owner approval
43

unnecessary packages removed

Remaining dependencies pinned
Commit 3eb2380529 Sep 2026
Read the source excerpt

Report: 29 Sep–9 Oct 2026 · September 29 npm-packages entry

“CHANGED: owner ‘yes, do 1’, from Claude’s Dorsal library review → 43 packages removed, all pinned”

The report references decision 258 and commit 3eb23805, with the owner’s approval recorded.

03Waterius/Firmware tests

Outside evidence.
A fix tested on the bench.

Dorsal supplied evidence for a finding in Waterius’s firmware-test audit. The resulting fix was accepted and verified on the live bench.

“fixes verified on the live bench”

Coding-agent usage report shared by Evgeny, Waterius

Read the customer report
Verified on the live bench
01Outside finding
02Fix accepted
03Bench verification
Firmware-test audit7 Sep 2026
Evidence & scope

Report: 18 Aug–28 Sep 2026 · September 7 bench-test audit

“Finding 1 rests on a Dorsal record”

The other two findings came from local code. The report says all three fixes were accepted and verified on the live bench.

Your next build

Give your agent more to work with.

Get Dorsal

Two steps, about a minute

Get Dorsal

Claude Code checks Dorsal before each major decision.

  1. 01

    Connect Dorsal to your coding agent

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

    Read-only. Your data stays local.
    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. 02

    Tell your agent 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 your coding agent. It loads both at startup.

Skill + API

Or get Dorsal as a skill

The skill calls the Dorsal API over HTTPS when your agent needs evidence. Until then it adds 367 characters to the agent’s context. The MCP server adds 13,102. Same graph, same records. Works in Claude Code and Codex. Step 2 applies here too.

How the skill works →API reference →