The flight recorder for AI coding

AI agents don't fail because they're stupid.
They fail because they're new.

Every confident, wrong line of AI code costs you tokens, review cycles, and trust. Decispher captures the decisions, conventions, and constraints from the conversations your team is already having in Slack, GitHub, and Jira, then serves them back to every human and every agent that needs them. Automatically.

Get early access
Public beta·Set up in minutes·No credit card
Humans
Dashboard · Slack · Jira · IDE
+
AI agents
Claude · Cursor · Copilot · MCP
NEWChat Clipboard · transfer mid-task context across sessions, machines & AI toolsNEWBranch Story · every branch has a story, never start a session cold again
Open source

Our enforcement layer, Decision Guardian, is open source and free. It blocks pull requests that violate a decision on record. Read the code, star it, run it in CI today.

DecispherHQ/decision-guardian61GitHub Action
The problem

Your team has the answers.
Your new hires and AI agents don't.

Every engineering team has two kinds of knowledge. The explicit kind lives in GitHub: code, READMEs, tickets. The tacit kind lives in people's heads: why the architecture is that way, what was tried and failed, which invariant must never break. AI agents only see the first one.

PROBLEM · 01
Confidently wrong code
Your AI agent re-introduces a bug your team fixed nine months ago. The convention it violated was decided in a Slack thread and never written down. The fix becomes another invisible constraint the next model will also miss.
cost · review cycles + tech debt
PROBLEM · 02
Token waste
Every agent call dumps 8,000 tokens of guessed-at context because nobody curates it. You pay Claude to rediscover what your team already figured out. The bigger your codebase, the worse the bill and the slower every call.
cost · ~40% of agent budget, every call
PROBLEM · 03
Onboarding decay
Every new engineer spends three months reverse-engineering institutional history from Git blame and lunch conversations. Knowledge that should be a one-query answer turns into a months-long apprenticeship.
cost · 90 days to productive output
PROBLEM · 04
Context amnesia between sessions
Your AI agent rebuilds the same mental model every session. Yesterday's reasoning, the approach it already abandoned, the constraint it learned the hard way: all gone when the session ends. The next session starts from zero and repeats the mistakes.
cost · repeated work, repeated mistakes
The numbers

Receipted, not estimated.

Every claim Decispher makes ships with a number you can verify on your dashboard. The Context Health Score is the metric your CTO will check on Monday morning.

~40%
FEWER TOKENS
Median reduction in tokens per agent query, receipted per call on your dashboard, not a flat-rate estimate.
2.9×
LESS CONTEXT
The tiered Context Map serves a tiny spine inline and fetches the rest on demand over MCP. Agents pull ~500 tokens, not ~8,000. Nothing dropped, just deferred.
9
AGENT FORMATS
.cursorrules · CLAUDE.md · AGENTS.md · .windsurfrules · .clinerules · copilot-instructions.md · 3 more, plus the committed .decispher/ Context Map, all kept in sync.
0
BEHAVIOR CHANGE
Engineers keep writing Slack messages and PR descriptions exactly as they always have. Decispher does the rest.
0
COLD STARTS
Branch Story opens every coding session with a briefing of what is already known about the branch. Agents resume mid-thought instead of relearning it.
What Decispher is

Three jobs. One system of record.

Decispher reads the conversations your team already has, structures the durable signal into seven canonical context units, and serves them back to every consumer that needs them: humans in their IDE and dashboard, AI agents over MCP.

01 · Capture

From the work, not on top of it.

Bots listen in Slack channels. Webhooks watch GitHub PRs and reviews. The Jira app reads ticket threads and feeds context back when an agent picks the ticket up. No new tool for engineers, no manual documentation step. Decisions are extracted from the conversations, tickets, and PRs your team is already having.

02 · Fuse

The same decision, said three times, becomes one.

A five-step LLM pipeline classifies every message, extracts the structured why, and fuses fragments across channels. Same idea in Slack and PR description? Merged. Multi-source agreement boosts confidence. Conflicts are flagged.

03 · Serve & enforce

Every consumer, the right amount, on demand.

Humans get search, “Ask Decispher,” and PR comments. Agents get MCP tools and 9 native instruction files. And when code contradicts a decision on record, the PR gets flagged before a reviewer ever opens the diff.

Feature 01 · Capture

Read where the work happens. Change nothing.

Ninety percent of engineering decisions are made in conversation and never documented. If you can't capture there, you can't capture at all. Decispher plugs in as a Slack bot, a GitHub webhook, and a Jira app. Your team writes the same messages they always have; we do the rest.

Sources · 3 live · 3 in pilot
SlackLive
GitHubLive
JiraLive
TeamsSoon
LinearSoon
NotionSoon
Pipeline · five steps · the same engine for every source
01 · Detect02 · Extract03 · Enrich04 · Format05 · Dedup
Output · seven canonical context-unit types
DECISION"chose React over Vue"
CONVENTION"all API routes versioned"
CONSTRAINT"never store JWT in localStorage"
RATIONALE"BullMQ — no cold starts"
HISTORY"Prisma tried '22, failed"
OWNERSHIP"@auth-team owns JWT"
PLAN"monorepo before Q4"
Feature 02 · Context Fusion

The same decision, said three times,
becomes one record.

A constraint mentioned in Slack, repeated in a PR description, and confirmed in a design doc should not become three rules. Decispher's Fusion engine embeds every fragment, finds the ones that mean the same thing, and merges them into a single, multi-sourced unit. Cross-channel agreement raises confidence. Disagreement raises a flag.

6
RELATIONSHIP TYPES
EXTENDS · CONFIRMS · CONTRADICTS · SUPERSEDES · SAME_TOPIC · UNRELATED
0.95
DEDUP THRESHOLD
Cosine similarity over 1536-d embeddings. Above this, an incoming fragment is treated as a near-exact resend and deduplicated.
0.94
AVG MULTI-SOURCE CONFIDENCE
When two channels independently corroborate a decision, confidence jumps from 0.71 to 0.94.
Feature 03 · Relationship Linker

A database of decisions is just a list.
A graph is a memory.

Decispher persists the relationships between context units, not just the units themselves. Every new decision is classified against your existing graph: does it confirm, extend, contradict, or supersede something we already know? The result is a queryable map of how every choice your team has made depends on every other one.

knowledge_edges · live
9 units · 8 edges · sample project
CONFIRMS
two units corroborate the same claim
EXTENDS
one unit builds on another
CONTRADICTS
two units cannot both be true
SUPERSEDES
one unit replaces another over time
SAME_TOPIC
two units share a domain
DERIVED_FROM
one unit explains the other's why
Feature 04 · Context Map + Live Context

Commit the rules. Serve the rest live.

Dumping every decision into CLAUDE.md wastes tokens on every call. Dumping nothing makes the agent guess. Decispher does neither. A tiered .decispher/ map lives in your repo with a tiny always-loaded spine, and the deep detail is served on demand over MCP. Agents discover, narrow, and deep fetch, paying only for the tokens they actually use.

PER QUERY
~500
tokens pulled
VS BASELINE
~8,000
tokens avoided
PER QUERY
~40%
fewer tokens · receipted
GENERATION
0
LLM calls · deterministic
Layer 01 · Committed
Context Map

Generated by Decispher, opened as a PR, version-controlled in your repo. Every agent loads it for free on every session. No fetch, no cost.

.decispher/
├── overview.md · topic index
├── index.json · machine-readable map
├── context-rules.json · CI enforcement
└── topics/
   ├── auth.md · 12 units
   ├── database.md · 18 units
   └── billing.md · 9 units
CLAUDE.mdAGENTS.md.cursorrules.windsurfrules.clinerulescopilot-instructions.md
12 native formats · auto-PR on every change
Agent
↓ load freefetch live →
Claude · Cursor
Copilot · Windsurf
Layer 02 · Served live
Live Context · MCP

The deep detail stays in Decispher and is served over the Model Context Protocol. Three tools, one chain: discover what exists, narrow to a topic, deep-fetch the unit. Every call is receipted.

1list_topicsfreediscover the topic namespace
2get_context_for_topic1 creditspine inline plus IDs of the rest
3get_decision1 creditfull body for one decision
Every call writes a row to the ledger
Net effect: agents pull ~500 tokens they need, instead of the ~8,000 they'd guess at. Nothing dropped, just deferred.
↓ 40% fewer tokens per query · receipted, not estimated
Feature 05 · Ask + MCP

Humans ask in plain English. Agents query the same memory over MCP.

Every “why did we…” gets an instant, cited answer, served in dashboard chat, a Slack command, or a GitHub PR comment. The same memory is exposed to AI agents through 12 MCP tools, so every coding tool your team uses reads from one source. Every answer cites the units it came from. No source, no claim.

three real questions · streaming live
For agents · one install, 12 MCP tools
Claudevia claude.ai
CursorMCP plugins
ClineVS Code
WindsurfMCP catalog
ContinueMCP-compliant
CodySourcegraph
$ npx -y @decispher/mcp-server# works with claude code, cursor, cline, windsurf
decispher.check_intentpre-flight check before any code change. Returns BLOCKED, WARN, or CLEAR
decispher.search_decisionssemantic search across all 7 context types. Filter by type or search everything
decispher.get_constraintsfetch all active architectural constraints the agent must not violate
decispher.check_conventionsretrieve all active coding conventions before writing code
decispher.get_context_for_filesymbol-graph plus embedding retrieval for one file or up to 10 at once
decispher.ask_knowledge_baseAI-synthesised answer with cited sources from the knowledge base
decispher.list_topicsdiscover the project's topic namespace. Free, no credits consumed
decispher.get_context_for_topiccurated context cluster for a topic: spine units inline, expansion IDs returned
decispher.get_decisionfull body for any context unit by ID: rationale, alternatives, affected files
decispher.capture_decisionwrite new knowledge back into the team's knowledge base from inside an agent
decispher.copy_chatportable conversation snapshot. Server returns a clipKey that works across machines and AI tools (7-day TTL)
decispher.paste_chatrestore a snapshot by clipKey. Becomes the new session's working memory · free
+6 freeTurn on Branch Story and agents get six more tools for branch-keyed memory: store_read, store_write, and four more. All free.Learn more
Chat Clipboard · transfer context across sessions, machines, and AI toolsNEW · v0.2

Mid-task in Cursor, context window filling up? Say "copy this chat to decispher" and get back a short dsk-clip-… key. Open Claude Code at home, paste the key, keep going. Hand the key to a teammate, they pick up your work in their IDE. The snapshot is Redis-only, ephemeral, never enters the knowledge graph. Paste is always free.

Same key, any IDECursor → Claude Code → Cline
Cross-machineWork → home → laptop
Cross-teammatePair-programming hand-off
Snapshot TTL7 days · ephemeral
Feature 06 · Branch Story

Every branch has a story. Don't let it evaporate.

An AI agent rebuilds its understanding of a branch from scratch every session. Yesterday's reasoning, the constraint you found the hard way, the approach that didn't work: all gone by morning. Branch Story keeps it. One command attaches Decispher to Claude Code or Cursor, then every session opens with a briefing of what's already known and quietly records what's new.

branch story · feat/payment-retriesresuming
$ npx decispher init# one command, then it's invisible
01
Pre-flight briefing
Resume a branch and read the last state, the open questions, the decisions on record, and what was already tried, before you touch a line.
02
Recording light
A status indicator shows when Decispher is capturing. Nothing happens silently, and you can pause it any time.
03
Story Mode
A chapter-by-chapter replay of how a branch reached its current state, linked from every PR. Reviewers see why, not just what.
04
Déjà vu detection
A warning the moment you start down a path that was already tried and abandoned on this branch. The longer it runs, the more it catches.
05
Session Receipt
Every PR gets a summary: decisions made, constraints discovered, approaches dropped, with a link straight to the replay.
06
Save Context
One click promotes anything worth keeping into the team knowledge base, from the Branch Store, Story Mode, or the receipt.
Decispher · Branch Story for VS CodeMarketplace

The Branch Store, Story Mode, Save Context, and “why is this line here” lookups, right inside your editor. Works in VS Code, Cursor, Windsurf, and other VS Code forks via Open VSX.

Branch Store sidebarStory ModeSave ContextWhy is this line hereRecording light
Install from the Marketplace

Seen enough? Your agents are still guessing.

One command wires Decispher into Claude Code, Cursor, or any MCP client. Your team keeps working exactly as before.

Get early access
Integrations

Plug into the stack your team already uses.

Capture from where the work happens, serve to every tool that writes code. No new habits for engineers, no migration project. Everything below is live today.

Slack
Bot listens in engineering channels
Live
GitHub
PRs, commits, and review threads
Live
Jira
Ticket context, in and out
Live
Claude Code
CLAUDE.md plus live MCP tools
Live
Cursor
.cursorrules plus live MCP tools
Live
VS Code
Branch Story extension, any fork
Live
See all integrations
The flywheel

Every PR makes Decispher smarter than yesterday.

Decispher isn't a one-time integration. It's a loop. Decisions feed the Context Map; the map writes the committed rules; agents follow them; Lens watches what actually fires; the score re-ranks every rule. Every cycle through the loop, the context gets denser and the agents get more accurate. The longer it runs, the harder it is to leave.

01
Decision lands
A new context unit is captured from Slack, GitHub, Jira, or a coding session.
02
Map regenerates
The Context Map orchestrator rewrites the committed files. Deterministic, only the topics that changed.
03
Agent ships code
Claude / Cursor / Copilot writes PRs against the compiled rules.
04
Lens scans the PR
Match telemetry: which rules actually fired on real code?
05
Relevance updated
Hot rules climb. Stale rules decay. Loop repeats, sharper every cycle.
Compound interest, on engineering memory.
Every Lens scan makes the Context Map smarter. Every regeneration makes the next scan more relevant. Competitors building the same surface area without the full loop catch up to last month's Decispher.
Public beta · early access open

Stop paying Claude to rediscover
what your team already figured out.

Run npx decispher init and Branch Story starts briefing your sessions the same day. In the background, Decispher reads your Slack, GitHub, and Jira history, builds your Context Map, and ships a PR with the .decispher/ directory. You approve. Your agents wake up smarter every morning after.

Checking availability…
No credit card · drop-in MCP server · pause capture any time
Raw messagesNever stored long term. Decispher keeps the extracted decision, not your Slack history.
EncryptionEvery context unit is encrypted at rest with a key derived per company.
CaptureAlways visible. A recording light shows when capture is on, and you can pause it any time.
EnforcementDecision Guardian is open source. Read the code that gates your pull requests.
EnterpriseSSO, custom data residency, higher effort tiers, and a dedicated onboarding. Talk to us about a plan that fits your team.
Contact us