SpecShip builds a live knowledge graph of your code, specs, and tests — so your AI agent explores structurally instead of re-reading files, your requirements never silently drift, and every token is accounted for.
Every session your agent re-reads the same files to rebuild the same mental map — paying input tokens to relearn what it already knew an hour ago.
A function gets refactored, a field gets renamed — and the requirement that depended on it is now a lie. Nobody notices until production does.
SpecShip indexes your repository into a typed knowledge graph, then layers analytics, drift detection, and automation on top of it. Each surface reads from the same source of truth.
tree-sitter extracts functions, classes, routes and tests; SpecShip synthesizes the edges between them. 4,000+ nodes, force or hierarchical.
Link RFC-2119 requirements to the symbols that satisfy them. When code moves, the link drifts and lands in a review queue — not in prod.
specship_explore & specship_search let agents query structure, not files.
Every Claude Code session, priced by model, prompt and cache rate — across all your projects.
SpecShip mines your transcripts for recurring patterns and proposes durable fixes — memory rules, skills, hooks — that you preview and apply in one click on the Improvements page.
spec-implement, verify and fix — run in isolated git worktrees with an approval gate before merge.
See the whole CLAUDE.md hierarchy — managed, user, project, imports — plus the notes your agent writes itself.
SpecShip parses every file with tree-sitter and stores the result in a local SQLite graph: typed nodes for code, specs, tests and routes, with extracted and synthesized edges between them.
Write requirements in plain RFC-2119 prose and link each one to the symbol that satisfies it. SpecShip re-verifies those links on every index and surfaces anything that has drifted, broken, or was never implemented. One principle everywhere: a surface may only promise what it can prove.
SpecShip exposes the graph to your agent over the Model Context Protocol. Instead of dumping whole files into context, the agent asks a structural question and gets back exactly the symbols, callers and linked specs it needs.
SpecShip reads your Claude Code session transcripts and turns them into a real ledger: cost over time, by model, by prompt, by project — with cache-hit analytics that show what you're already saving and what you're leaving on the table.
Bundled workflows like spec-implement run in an isolated git worktree: plan, implement, test, then pause for your approval before anything merges. Reject with a comment and the agent revises in the same worktree, then pauses again — rejection is feedback, never lost work.
Index your first repo in under a minute. The core runs entirely local — your code and transcripts never leave your machine. The two optional integrations that do talk to a service (JIRA, Designer) are strictly opt-in.