No more decisions undone in good faith.
A teammate's agent reverts what you decided three weeks ago. The tests pass. You find out on a Friday.
Rationale links team decisions and their reasons to the code.
Early access · Guided setup
› Replace the queue?
Consumers expect order
Preserve event order.
› Parallelize event sends?
Sam: preserve event order
Keep events in order.
› Cache account totals?
Rejected: stale balances
Use fresh balances.
› Reuse cached balances?
Mina: use fresh balances
Fetch balances on demand.
› Hand off the export.
Keep memory use bounded
Stream export rows.
› Resume the export task.
Noor: stream export rows
Resume the streaming path
› Move EU data?
Region rule: EU only
Keep data in the EU.
› Move records to the US?
Inez: keep data in the EU
Keep records in the EU.
› Refactor all billing?
Scope: invoice dates only
Limit the patch.
› Edit invoice validation?
Sam is editing this file
Check with Sam first.
› What did sales agree?
Sales source not connected
Ask for the missing source
› Use the old API limit?
Revisit: API limit changed
Review the latest reason.
What we eliminate
A teammate's agent reverts what you decided three weeks ago. The tests pass. You find out on a Friday.
“EU customers' data never leaves the EU region” arrives as a constraint no technical choice overrides.
When two people, or two teams, touch the same thing, they know before they collide. Not at merge time.
Your agent starts out knowing what was decided. Fewer explaining prompts, fewer failed attempts.
The pull request keeps the diff. Rationale keeps the why, who decided it and what was ruled out.
How it works
01 · Capture
Install once per laptop. After each session, the client extracts the decisions on that same machine.
02 · Record
Question, choice, reasons, what was ruled out and when to revisit it. Tied to its files and its task.
03 · Give context
What was decided, who is on it and what is left. In Claude, ChatGPT or Cursor, over MCP.
04 · Warn
When an agent is about to touch a file a decision is anchored to, the decision arrives first.
$ curl -fsSL https://rationalehq.com/install.sh | sh
$ rationale init
✓ Signed in as sam@acme.dev · workspace acme
✓ Hooks added to Claude Code and Codex
✓ Capturing. Nothing else to do. › make the webhook retries faster, 3 attempts is too slow
● Reading app/jobs/webhook_delivery_job.rb
● Edit app/jobs/webhook_delivery_job.rb · MAX_ATTEMPTS = 3 → 10
Rationale · a decision is anchored to app/jobs/webhook_delivery_job.rb
D-42 Retry policy for partner webhooks
⏺ I stopped before changing it. Ana chose 3 attempts on purpose: two partners block us above 5 requests a minute (D-42). I can add jitter and a longer backoff within those 3 attempts, or you can ask Ana to revisit D-42. Which one?
What we believe
See the choice, its alternatives and when to revisit it.
Illustrative team decisions
EU customers' data never leaves the EU region.
Trials end without asking for a card.
3 retry attempts for partner webhooks.
See its source, evidence and whether it was inferred or confirmed.
Decisions stay linked to tasks, tickets, pull requests and files.
Unconnected sources and unlinked projects are clearly marked.
Integrations
Capture each session, with pre-edit warnings and #handle context.
Capture and context in the CLI, ChatGPT app and IDE extension.
Read and record decisions over MCP.
Link decisions to pull requests, reviews and issues.
Turn tickets and epics into tasks with their decisions.
Keep tasks in Rationale and ask agents to open them.
Not built yet. We build in the order teams request integrations.
Security
«The pull request keeps the diff. Nobody keeps the why. I built Rationale for my own team first: several people, several agents, the same code every day.»
Your agent provider processes session excerpts under your own agreement. Rationale receives extracted decisions, short evidence quotes and file references, not full transcripts. Decision content is encrypted at rest. Separately, an owner can authorize document reads through knowledge sources.
Claude Code today, with capture and edit-time warnings; Codex in beta. Claude, ChatGPT, Cursor and any client that speaks MCP can read and record decisions through our remote connector.
No. Connect them and tickets, epics and pull requests carry their decisions. Without a tracker, tasks live in Rationale.
Keep using those for instructions and memory. Rationale adds decision records linked to tasks and files, with reasons, evidence and revisit conditions. Capture hooks and MCP bring that context into supported agent workflows.
We are in early access and onboarding teams one by one. Plans come soon; we will publish them before anyone is charged.
On servers in the United States, run by an EU company under the GDPR. Our privacy policy lists every provider and what each one processes.
Try a guided two-week pilot with three people and one repository.
Plans are published before anyone is charged.