Daintree Decisions
How Daintree Decisions carries an agent's question through a relay in your own Cloudflare account to your phone and your desktop inbox, and types your answer back into the terminal that asked.
Some questions an agent shouldn't answer for itself. Which of two designs to ship, whether a migration can drop a column, whether the screenshots it just took look right. Decisions lets the agent put that question to you and keep going. You answer it from your phone, wherever you are, or from the Decisions inbox when you're at your computer, minutes or days later.
It runs through a relay you deploy into your own Cloudflare account. Daintree runs no server for it, and the questions, answers and screenshots are end-to-end encrypted between your computer and the devices you pair with it. Decisions is off until you turn it on, and then off for each agent on this computer until you switch that agent on.
How a Question Reaches You
- The agent asks. It calls an MCP tool,
ask_human, with a self-contained question, optional context, options and screenshots. It is told straight away that the question is queued (Asked as q-4), so it carries on with anything that doesn't depend on the answer, and ends its turn when it can't go further without it. Nothing blocks while it waits for you. - Daintree sends it. The question is saved on your computer first, then sent encrypted to your relay, which pushes a notification to your paired phones. That notification says only that a question needs you, never the question itself. Your computer raises a desktop notification of its own, and by default, while it sees you there, the relay holds the phone notification back for up to two minutes. If the relay is out of reach, the question goes out when it's back.
- You answer, on your phone or your computer. Pick an option, write a comment, or send a follow-up first if the question isn't clear. On your phone you can also attach a photo. On your computer, the Decisions inbox lists every question waiting on you.
- Daintree types the answer into the run that asked. Same terminal, same launch, same agent session, and only when it's safe to type: at the agent's prompt, or mid-turn for Claude Code and Codex, and never over a draft, an approval selector or an error. If that terminal is gone, Daintree can resume a Claude Code or Codex session to deliver it. Otherwise it holds the answer and tells you, so nothing is typed into the wrong place.
What You Need
- A Cloudflare account. The relay is a Worker, a Durable Object and a private R2 bucket. Cloudflare's free plan is enough for one person, though R2 needs a payment method on file. See Cloudflare Account and Costs.
- A phone or tablet with a browser. On iPhone and iPad, iOS 16.4 or later, with Decisions added to the Home Screen so notifications arrive.
- A supported agent. Claude Code, Codex, Gemini CLI, Qwen Code, OpenCode, GitHub Copilot, Amp or Mistral Vibe, or a plugin agent that accepts an MCP server at launch. See Supported Agents.
- Node.js 22 or later, only if you deploy the relay from Daintree or the command line.
- A local project or scratch window for deploying, updating or removing the relay. A window on a Remote Host can use Decisions but doesn't manage the relay.
Set Up Decisions
Everything lives in Settings → Integrations → Decisions. It's one setting for this computer: there's no per-project switch.
- Turn it on. Switch on Enable Decisions. The first time, Turn on Decisions? lists what Decisions sends and where it goes. Only Turn on Decisions turns it on, and nothing is sent until you connect a relay.
- Deploy or connect a relay. Guided deploy creates one in your Cloudflare account from a terminal in Daintree, or you can enter the address of one you already have. See Guided Deploy.
- Claim it and save a recovery kit. Claiming makes this computer the relay's owner. A guided deploy claims the relay for you; an existing relay is claimed with its secret, or restored from a recovery kit. Then save and verify a kit of your own: it's how you get ownership back on a new computer. See Claim or Restore and Save and Verify a Recovery Kit.
- Pair a phone. Scan a QR code, compare six digits, then turn on notifications in the phone app. On iPhone and iPad, add Decisions to the Home Screen first and pair from there. See Pair a Phone.
- Run the setup check. Check setup sends a test question to your phone and waits for it to come back. See Run the Setup Check.
- Switch on an agent. Under Agents, switch on each agent you want to ask you questions, then launch it. An agent that was already running picks it up at its next launch. See Enable an Agent.
With a relay connected, until a recovery kit is verified and the setup check has passed, the Connection section says Setup isn't finished. Agents can still ask in the meantime; the warning is about whether you could recover the relay and whether a question really reaches you.
Where It Fits
Decisions is for questions an agent hands to you on purpose, rather than stopping to stare at its prompt, and that can wait for you. An agent that simply stops at its prompt shows up in its waiting state, in Pilot and in Canopy, and you answer it in its terminal like anything else. A Decisions question is in the inbox at your desk and on your phone away from it, and answering it in either place closes it in both.
It is also separate from Settings → Hosts → Answer from another device, which lets a phone or laptop you reach through your own tailscale serve or ssh -L see a waiting agent's screen, with secrets redacted, and pick one of its options. That goes through no relay and works on whatever the agent is showing; Decisions is for questions an agent asks on purpose.
And it is a different server from Daintree's own MCP server. Daintree hands an enabled agent a separate daintree-decisions server at launch, whatever your MCP server settings, and writes nothing into the agent's config or your project.
Decisions Guides
- Set Up a Decisions Relay: the guided deploy, an existing relay, custom domains, and updating or removing the relay from Cloudflare.
- Pair Phones and Recover Keys: claiming the relay, the recovery kit, pairing a phone, the setup check, enrolling Remote Hosts, and revoking a device.
- Enable Agents and Receive Answers: which agents are supported, answering on your phone, when Daintree types an answer in, the pane chip, and what to do when an answer needs you.
- Answer From the Decisions Inbox: answering, following up, dismissing and withdrawing questions on this computer, desktop notifications, and your involvement preference.
- Decisions MCP Tools: the five tools an agent gets, their fields, statuses and limits.
- Approval Gates and the Decision Model: requiring your own approval of exact screenshots in a runbook, and letting a model answer some questions in your place.
- Decisions Privacy and Data: who can read what, terminal snapshots, voice dictation, and what each off switch and deletion removes.
The relay, the phone app and the decisions command-line tool are open source in daintreehq/decisions. These pages cover the Daintree side.