Answer From the Decisions Inbox
The Decisions inbox on your computer: opening it from the toolbar, palette or pane chip, what it lists across this computer and its Remote Hosts, answering and following up, dismissing or withdrawing, clearing Needs you, desktop notifications, holding phone notifications, and the involvement preference.
You don't need your phone to answer an agent when you're at your desk. The Decisions inbox lists every question your agents asked through Decisions, on this computer and on the Remote Hosts it enrolled. There you can read a question in full, answer it, send a follow-up, dismiss it or withdraw it. Once a question has reached your relay, your phone and the inbox show the same question, and the first answer the relay accepts, from either, is the answer.
An answer you give here is your own, not a proxy's. This computer, the relay's owner, signs it with its own key, Daintree types it into the terminal that asked under the same rules as a phone answer, and your phones show it as answered on this computer.
Open the Inbox
- The toolbar. The Decisions button opens the inbox, and its badge counts the questions in Needs you that you haven't seen or cleared. It's there only while Decisions is on. Move or hide it in Settings → Toolbar.
- The command palette (Shift-Command-P Control-Shift-P Control-Shift-P ). Open Decisions inbox opens the inbox. Open next Decisions question opens the oldest question in Needs you you haven't seen yet (or the oldest one there, if you've seen them all), and you can step from it through the others. Neither has a default key; assign one in Settings → Keyboard.
- A pane's Decisions chip. Open inbox, at the foot of the chip's popover, opens the inbox at that pane's question.
- Settings. Settings → Integrations → Decisions → Questions → Inbox → Open inbox closes Settings and opens the inbox.
- A desktop notification. Clicking one for a new question, or for a follow-up that wants a reply, opens that question. See Desktop Notifications.
The inbox lists this computer's questions, so the toolbar button, the palette actions and the chip's Open inbox aren't offered in a window attached to a Remote Host. Open it from one of this computer's own windows, where the questions agents on that host asked are listed too.
What It Lists
Questions are grouped by what they need from you. Empty groups don't show.
| Group | What's in it |
|---|---|
| Needs you | Questions waiting for an answer, including ones still queued on this computer, and answered questions where the agent sent a follow-up asking for your reply. Oldest first, except that a question due within a day moves to the top with a Due in… chip. |
| Being delivered | Answers and follow-ups waiting to be typed into the terminal that asked. |
| Needs attention | Answers, and follow-ups you sent, whose delivery stopped or that may or may not have been delivered, even on a question still waiting for its answer. A question here isn't also listed under Needs you or Being delivered. |
| Cleared | Questions you cleared from Needs you. You can still answer them, or reply to the agent's follow-up. |
| History | Questions that are done: answered, canceled (shown as Cancelled), expired unanswered, declined, or never sent. Most recently closed first. |
Each row shows the question, how long ago it was asked, the agent, project and worktree, and its alias, such as q-4. A question asked on a Remote Host is listed beside this computer's, oldest first across both. This computer keeps each host's list while it has a connection to that host. When it doesn't, the host's questions stay listed as they were last heard, and reading one waits until the host is back.
The list is one stop for the keyboard: ↑ and ↓, Home and End move through it, Enter or Space opens a row, and Tab moves on, to Clear Needs you when it's there and then to the question.
When this computer isn't connected to the relay, a notice above the list says why. While the connection is only being retried, the questions it already holds stay readable, new questions, answers and dismissals wait until it reconnects, and Sends once reconnected appears beside the send button. Other problems, such as keys or a database that can't be read, or a relay that revoked this computer, need you to act in Settings → Integrations → Decisions, as the notice says.
Read a Question
The selected question shows the agent that asked, the question as its heading, when it was asked and when it's due, then its notes, its options and their descriptions, and any screenshots. Below that is the thread: your answers and follow-ups on one side, the agent's on the other, each saying where it came from, such as Answer from your phone, Answer from your computer or Follow-up from the agent, asking for a reply.
- Screenshots open filling the window. Arrow keys, Home and End step through them, and Esc goes back to the question. When the question has a before and an after image, Compare before and after shows them side by side. Each image is checked against the digest the question carries before it's shown, and it's held in memory only.
- Go to terminal appears while the terminal that asked is still open on this computer, and takes you to it, switching projects if it has to.
- Next question appears when the question you're reading isn't in Needs you and another one is, and moves to it.
- A question in Needs attention shows Delivery stopped or Delivery uncertain, with Resolve delivery, which opens Answers needing attention for that terminal. A Remote Host keeps its own list of those, so a host's question doesn't offer it.
Questions are read on demand and kept in memory only while the inbox is open. Question text is shown as plain formatting: links show as their words and images as their alt text, so nothing in a question can fetch, navigate or open a file.
From the Pane Chip
A pane's Decisions chip lists that pane's questions by their opening lines. Choosing one opens it in a question view with the same reading, answering, follow-up and dismiss controls as the inbox. ← and → (outside text fields and code blocks), or the arrows in its header, step through the pane's other questions without closing it, and Esc closes it. The question view works in a window attached to a Remote Host too.
Answer a Question
While a question takes an answer, Your answer sits under it, shaped by what the agent asked:
| The question is | You answer with |
|---|---|
| An approval | Its options (Approve and Reject unless the agent gave others), and a note if the question takes words. Then Send decision. |
| A choice | One of its options, and a note if the question takes words. Then Send answer. |
| Text | A text field. Then Send answer. |
| Mixed | An option, Or answer in your own words, or both. Then Send answer. |
Command-Enter Control-Enter Control-Enter sends from the form once it's ready. Until then, a hint beside the button says what's missing, such as Choose an option. An answer can be up to 16 KiB of text.
An approval that carries screenshots can't be decided until you've opened every one of them at full size: until you have, the hint reads Open the remaining image to decide, or how many remain. Your answer then records exactly which images you opened, the same way a phone answer does, which is what an approval gate checks.
Before signing anything, Daintree reads the question again. If it was answered elsewhere, canceled or expired meanwhile, or the agent changed it since you read it, nothing is sent and the view says why. A changed question asks you to review the update first. If the reply to a send is lost, Daintree checks whether it arrived before it sends again, so one answer never becomes two.
After you send, the form follows the answer through: sent, then waiting to be typed into the terminal, then Answer sent and typed into the terminal. On your phones it leaves Needs you and shows as answered on your computer. The agent's get_decision reports answered_on: computer, with provenance: human like any answer of yours.
Send a Follow-Up
Follow up, below the thread, adds a message to the question's thread, before or after you answer. When the agent's latest message asks for a reply, the heading reads Reply to the agent and the button Send reply. Your follow-up is typed into the agent's terminal as a FOLLOW-UP block marked sent_from: computer, under the same rules as an answer. It never changes your answer or approves anything. On a question you've already answered, a reply to a follow-up that asked for one takes it out of Needs you on every phone.
A question still queued on this computer doesn't take follow-ups yet, and neither does one that was withdrawn or expired.
Dismiss or Withdraw a Question
There are two ways to close a question without answering it, and they mean different things to the agent.
- Dismiss question declines it for you, as Dismiss on your phone does. After Dismiss question q-4? names the question and its opening line, the question closes, its reminders stop, and it leaves Needs you. If the agent that asked is still running in the terminal that asked, Daintree types it a notice that you chose not to answer, and that nothing was decided or approved.
get_decisionreports the questioncancelledwithclosed_reason: declined. Your phones show it declined on this computer. The pane chip's list offers the same thing as Dismiss… on each waiting question. - Withdraw question calls the question off, as an agent's own
cancel_questiondoes. Daintree types nothing into the terminal. Your phones show it withdrawn, or never see it if it hadn't been sent yet, and the agent sees it canceled only when it checks. It's offered in place of Dismiss question when a dismissal can't be taken, and asks again with Withdraw question q-4? before it does anything.
Withdrawing is offered when your relay, or Daintree on the computer that asked, needs an update before it takes a dismissal from this computer, when the relay doesn't hold the question yet because a Remote Host hasn't sent it, and on a computer that doesn't sign for you. The view says which. Other failures offer Retry or say why instead. A dismissal sent while the relay is out of reach is queued and goes once it's back. While it's under way the pane chip reads q-4 dismissing, and a withdrawal waiting for the relay reads q-4 cancelling.
A Remote Host's question can be dismissed while that host isn't connected, as long as this computer read it while it was open on the relay: the confirmation says when it last read it, and the dismissal holds only if the question hasn't changed since. Once the host is back, an agent still listening is told. A dismissal like this is never turned into a withdrawal, which needs the host.
Clear From Needs You
Sometimes you've dealt with a question another way, such as telling the agent directly, and only want it out of the count. That's what clearing is for. It changes nothing for the agent or your phones, and nothing is answered, declined or withdrawn.
- Clear from Needs you, on the question you're reading, moves it to Cleared. Restore to Needs you moves it back.
- Clear Needs you, under the list, clears every question in Needs you at once.
Opening a waiting question in a focused window also marks it seen, once what it asks is on screen. Seen and cleared questions stay answerable for as long as the agent waits, but they stop counting toward the toolbar badge, the macOS Dock badge and the window title. A question counts again as soon as its agent asks something new in its thread. These marks are kept on this computer only.
Desktop Notifications
With Decisions connected, this computer raises a desktop notification of its own for each of these, at most once each, even across restarts. The titles below are examples; they name what Daintree knows.
| When | The notification | Clicking it |
|---|---|---|
| An agent asks a question | Question from <Agent> in <Project>, with the question's opening line | Opens the question |
| An agent's follow-up on an answered question asks for a reply | <Agent> in <Project> wants a reply, with the question's opening line | Opens the question at that follow-up |
| An answer or follow-up can't be typed in | Such as Answer to <Agent> in <Project> needs attention, or Follow-up to … may or may not have been delivered, with the reason | Opens Answers needing attention at that terminal |
A question answered or withdrawn before its notification would show raises none, and a notification already shown goes once its question stops waiting. They play the waiting sound when sound is on. Because an agent is asking you directly, only turning notifications off altogether silences them: per-event switches, quiet hours and a muted session don't. A turn that ended by asking a question doesn't also raise the usual Agent finished notification. See Notifications and Sound.
Questions waiting on you also count in the window title on every platform, and in the Dock badge on macOS, beside agents seen waiting. They count by pane: a pane with several questions, or with a question and a waiting agent, counts once. Unlike an agent's count, focusing the window doesn't clear them; answering, seeing or clearing them does.
Hold Phone Notifications While You're Here
Without this, at your desk you'd hear about every question twice. Hold phone notifications while I'm at this computer, under Settings → Integrations → Decisions → Questions, is on by default. While it's on, desktop notifications are on, and your relay supports it, this computer tells your relay whether it sees you here. While you are, the relay waits up to two minutes before notifying your phone of a new question, and doesn't notify it at all if it hears the question was answered, declined or canceled first.
- Three minutes without input, a locked screen, sleep, and an idle state Daintree can't read count as away.
- The hold covers every new question, a Remote Host's included. A notification already on its way to your phone can't be taken back.
- The relay learns only yes or no, never anything about your questions or your screen. Remote Hosts never send it. See Decisions Privacy and Data.
- With desktop notifications off, phone notifications go straight away, as if this were off.
How Involved You Want to Be
The foot of the inbox shows how involved you've asked agents to be, the same preference you can set on your phone:
- Ask while exploring. Agents are asked to come to you while they explore the options.
- Bring a recommendation. Agents are asked to consult a number of other agents first, from 1 to 8, then bring you their recommendation or their disagreement.
It also shows a temporary mode and when it ends, where it was set (this computer, or a phone or tablet), and when this computer last confirmed it with the relay. Change, or Set preference when none is set, opens a form with your usual mode, how many agents to consult, and an optional mode until a time you choose, at most 30 days ahead.
Agents read the preference with the get_involvement tool before they prepare a question, so a change reaches agents that are already running. It never changes what an agent may do or what needs your approval: agents agreeing is a recommendation, not an answer. If a phone changed the preference since you opened the form, your change isn't saved, and the inbox gives this computer a few seconds to read the newer one first. A relay older than 0.7.0 doesn't hold the preference at all, a 0.7 relay takes changes only from a phone, and 0.8.0 or later takes them from this computer too. A computer enrolled as a Remote Host can't change it.
cancel_question and post its own follow-ups with send_followup, as itself.What Signs for You
Only the computer that owns the relay signs answers, dismissals, follow-ups and preference changes for you, with the key the relay already trusts for approving your phones. Daintree running on a machine enrolled as a Remote Host never does: there, the view says this computer doesn't sign for you, and you answer from the owner computer or your phone. Signing a question a Remote Host asked is fine, since the owner computer signs it.
Taking answers, dismissals and follow-ups from a computer needs a recent relay, and a recent Daintree on the computer that asked. When one of them is too old, the view says which, nothing is sent, and your phone can still answer. Update the relay to fix the first.