Your agents do the work.
Your people make the calls.
When a coding agent reaches a decision it shouldn’t make alone, it files a structured request to CruxDeck — context, options, tradeoffs and screenshots already packaged. The right person decides. The agent reads the answer and carries on.
CruxDeck is not yet available.
Which retry strategy should payment capture use?
Filed by Claude Code · 2 screenshots · linked to JIRA-481
- ARetry immediately, up to three times
- Simplest change
- Can double-charge on a timeout
- BExponential backoff with idempotency keysAgent recommends
- Safe to retry on timeouts
- Touches the order schema
Today, the developer is the courier.
The agent stops and asks. Someone copies the question into Slack or a ticket, chases the person who can answer, and pastes the reply back into the session. The context gets trimmed on the way, the options get lost, and the reasoning lives in a thread nobody will find again.
Agents stall
Work waits on a human who doesn’t know they’re being waited on.
Reviewers guess
A one-line question in chat strips out the options and tradeoffs the agent already worked out.
Decisions vanish
Next month, nobody — human or agent — can find what was decided, or why.
The agent does the packaging. You do the judging.
CruxDeck flips who does the administrative work. Your agent assembles the decision; a person spends their time only on the call itself.
- 01
The agent asks
When it reaches a call it should not make alone, your coding agent files a Decision Request through the CruxDeck MCP server: the question, the background, the options with their pros and cons, its own recommendation, and any screenshots or files.
- 02
The right person sees it
The request lands in a reviewer’s inbox, marked as blocking the agent or not, with a notification so nobody has to remember to look.
- 03
A human decides
Compare the options side by side and choose one, answer with something else, or ask the agent for more information. Add an explanation, and it stays with the decision.
- 04
The agent carries on
The agent reads the outcome back through MCP — the chosen option or written answer, with any explanation the reviewer added — and gets on with the work. Nobody pastes anything anywhere.
One MCP server. Your agent does the rest.
CruxDeck connects to your coding agent through an open-source MCP server (Apache-2.0). The agent gets tools to file a decision, attach screenshots and files, link related decisions, and read the outcome.
- Works with Claude Code and Codex. Both supported from launch.
- Its own credential. The agent connects with a scoped token, limited to one organization, optionally one project, and the permissions you grant. Revoke it at any time.
- Never the final say. An agent can file, update and withdraw its own requests. Only a person can resolve one.
- Setup instructions arrive with the published package at launch.
Built for the moment a judgment call appears.
Decisions, not threads
A question, real options, pros and cons, and the agent’s recommendation — structured, so a reviewer can judge without reconstructing the conversation.
Blocking, or not
The agent says whether it is waiting. Blocking requests surface first; the rest can be reviewed while work proceeds, or simply recorded for the team.
See what the agent means
Screenshots, files and links sit beside the options, so a UI choice is a comparison you can look at, not a description you have to imagine.
A memory of every call
Each decision keeps its question, options, answer, any explanation, its reviewer and its history. Your team — and your agents — can find what was decided and why.
Agents never hold your credentials
Agents connect with their own scoped, hashed, revocable tokens. And an agent can never answer its own question: only a person resolves a decision.
Fits the tools you have
Link decisions to GitHub and Jira, and review from Slack or Microsoft Teams. CruxDeck is not another tracker — it handles the judgment calls your tracker was never built for.
Built for code you care about.
Decisions about your software are sensitive. CruxDeck treats them that way from the first line of the design.
- Every organization isolated. A person’s access to the app is checked against their current membership, not a stale token. Links to attachments grant short-lived access.
- Every change audited. Who did what, when, as a person or as an agent, kept for good.
- Private by default. Screenshots and files sit in private storage, reachable only through short-lived signed links.
- Untrusted content kept apart. Image previews are re-encoded and served from a separate domain, away from your session. Original files are downloads, never run.
- Decision history kept on every plan. Free hides older resolved decisions until you upgrade. No decision or audit record is ever deleted to meet a plan limit.
- Run it yourself. A self-hosted edition, with updates, that your team operates, using your own WorkOS, Cloudflare R2 and Resend accounts.
Frequently asked questions
- What is CruxDeck?
- CruxDeck is the human decision layer for AI software development. When a coding agent reaches a judgment call it should not make alone, it files a structured Decision Request: the question, options with pros and cons, its recommendation, and any screenshots. The right person decides, and the agent reads the outcome back and continues.
- Which coding agents does CruxDeck work with?
- Claude Code and Codex, through the CruxDeck MCP server. Agents file decisions, attach files and read outcomes with MCP tools.
- Can an agent approve its own decision?
- No. Only a person can resolve a Decision Request. Agents connect with their own scoped, hashed and revocable credentials, never with a person’s login.
- Does CruxDeck replace Jira, GitHub or Slack?
- No. CruxDeck is not a tracker or a chat tool. Decisions link to GitHub and Jira, and reviewers can decide from Slack or Microsoft Teams. CruxDeck holds the judgment calls those tools were never built to hold.
- How is CruxDeck priced?
- Hosted plans are priced per person, never per decision, and agents never count as seats. The current plan is a Free tier for up to two users and a Team plan at $9 per user per month. The self-hosted edition is priced by agreement. Pricing may change before launch.
- Can I run CruxDeck myself?
- Yes. A self-hosted edition, with updates, is planned alongside the hosted service. Your team operates it, using your own WorkOS, Cloudflare R2 and Resend accounts, under separate licensing and support terms.
- Is CruxDeck available now?
- Not yet. CruxDeck is in development. Email admin@cruxdeck.com to hear when it launches.
Bring your judgment calls to one place.
CruxDeck isn’t available yet. We’d like to hear how your team handles agent decisions today.