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

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

new records in the last 7 days.

What are you working on?

From first idea to final verification.

Relevant experience at every step.

Product
Discover ideas. Challenge assumptions.
Design
Compare architectures before committing.
Integrations
Check current APIs, libraries, and limits.
Code
Reuse working patterns and proven fixes.
Verification
Find what to test and how.

Three examples

01Keelo.AI/Design & planning

The architecture
plan changed.

Claude Code proposed one repository per agent. Evidence from Dorsal changed Keelo’s plan to one repository per customer, with that customer’s agents inside.

The repository boundary now follows customer ownership.

“Always using it. It influences almost every plan stage for us.”

Founder & CEO, Keelo.AI

7 Dorsal records informed the decisionIncluding Microsoft’s ADR-0032

Claude Code’s initial plan

One repo per agent

Agent AAgent BAgent C

Changed with Dorsal

Keelo’s adopted plan

One repo per customer

Customer repository

Agent AAgent BAgent C

Decision 0095Commit e114651

Then, through the buildTwo examples from six PR reviews

Code

A blocked installer. A verified fix.

Dorsal surfaced NVIDIA garak’s fix for the same Linux path failure. Keelo’s agent applied the pattern; a second agent tested it.

Before FAILAfter PASS

PR #59 · commit a47eb53

Verification

A build gate that catches the failure.

Evidence from TensorRT-LLM and Qwen Code informed the fix: compare failing check IDs with the base, instead of trusting the exit code.

Fix checked by a second agent

PR #29 · commit 531d8d98

Evidence & scope

Design: Keelo’s customer card cites decision 0095, commit e114651, and seven Dorsal records, including Microsoft’s ADR-0032 dated 21 July 2026. It records the change from one repository per agent to one per customer.

Code and verification: the PR handover attributes the installer repair to NVIDIA/garak #1860 and the build-gate repair to patterns from TensorRT-LLM and Qwen Code. A second agent checked the fixes on local branches. Keelo adopted some of the handover’s changes; the report does not establish that both fixes shown here shipped.

Read the architecture decision and its evidence in the Keelo decision report.

02Thorsten Freitag/Dependencies

43 packages removed.

Thorsten approved a Dorsal-backed cleanup. His coding agent removed the unnecessary packages and pinned the remaining versions.

“43 unneeded software packages removed and the rest pinned”

Coding-agent report · 29 Sep 2026

Decision 258 · Commit 3eb23805

03Waterius/Firmware tests

Verified on the live bench.

Dorsal backed one finding in Waterius’s firmware-test audit. Waterius accepted the fix and verified it on hardware.

“Finding 1 rests on a Dorsal record”

“fixes verified on the live bench”

Coding-agent report · 7 Sep 2026

Read the customer report ↗

Two steps, about a minute

Use this inside your coding agent.

Connect Dorsal to Claude Code or Codex, then tell it when to check the evidence.

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.

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 →

Claude Code had a plan. Dorsal changed it.