Decisions
When an agent needs your yes, it asks you in the chat you are already in, and you answer there. Your answer is kept in your words, and it reaches the agent that asked, even if that chat has closed.
Answer a question
- The agent asks one question in plain words and says what it recommends and why.
- You answer in the chat. Where your app shows a decision card, tap Yes, No or Change it, or just type your answer.
- The agent records your answer. It quotes your words and names the chat you said them in.
You never need to open Mainmind to answer. A question an agent asks you in your own chat stays in that chat: it is not added to the app as something waiting, and the 7-day default never takes your silence there as a yes. If you leave it unanswered, it stays on that agent's own list of questions, which the agent reads when it checks its questions or starts its next session, so it can ask you again then.
The Your call page in the app lists everything else still waiting on you, such as a teammate's change that only you can approve. It has the same Yes, No and, for the owner, Change it. On each plain question you can also choose Leave waiting, Yes, No or Overtaken, then record those choices once. Overtaken needs a reason, and that reason stays hidden until you choose it. Nothing is decided, and the agent that asked hears that reason the next time it starts. When the list is longer than one page, Show the next brings the following page. After you answer, it says which agent hears it. A Page that shows an open decision uses those same controls for the owner or a co-owner who may already answer it. A question asked in your own chat still stays off Your call. If a Page links that question, you can answer it there too. Choosing among several options, or a decision made of several parts, still happens on the decision page.
What to answer first
Your call and the decision list put the most urgent question first.
- Answer first, Answer soon, and Can wait say how soon. A question with none of these waits behind the ones that have them.
- A due time comes before one that is not due yet. One that is already late comes first among questions with the same rank.
- When those are the same, the older question comes first.
An agent can set the due time and the rank when it asks. The owner, a co-owner, or the chief of staff can change the rank later. A link on the card is there so you can read the evidence. A yes does not save that link.
The owner and a co-owner see every question they may answer, across agents, in one list. A page table can fill from that same list when the page is open; the rows are not stored in the page. A question that needs you to sign in and do it says so on the card. The owner, a co-owner, or the chief of staff can retire a question events have overtaken, with a reason. That is not an answer. The agent that asked is told the next time it starts.
What happens after you answer
| You said | What happens |
|---|
| Yes, to a change in your knowledge | The change is saved on its own. |
| Yes, to anything else | The agent is told to carry it out and to tell you when it is done. |
| No | Nothing changes, and the agent is told not to do it. |
| Change it, with a note | The agent is told to make your changes and ask again. The old version is never saved. |
The answer goes to whichever app is working as that agent next. An agent hears it the next time it syncs, in any app. If no app is working as that agent right now, the answer waits for it.
What is serving and what is not yet. All of the above works today, including an answer given on a Page. Mainmind does not start an agent by itself: the agent's app decides when it runs, so an answer is acted on when that agent next works. A notice that reaches the agent the moment you answer is not serving yet.
Going ahead without asking
Two switches let a change to your knowledge go ahead without a fresh answer. Both are off until you turn them on, and both apply only to a change that can be undone:
- Always, when its switch is on, is offered after you say yes to two asks of exactly the same kind. Later asks of that kind go ahead with your yes.
- The 7-day default lets a change go ahead when the agent recommended yes and it has waited 7 days on Your call. A question asked in your own chat waits for your answer instead.
Mainmind records the answer, not the agent, and lists it under Done for you, where you can undo it. A plain question that is not a change to your knowledge always waits for you. So does anything about money, pay or tax, anything that mentions customers or reaches people outside the business, and any change to who may do what or to the instructions your agents follow.
A standing rule you already ruled is the one exception weighing can cover. Pass one item. When the rule covers it, go names the rule, the outcome and a confidence. It does not approve a payment or a change in a connected account. Pay, a write-off, or money leaving still waits unless that rule names the reason. A filed month and FY26 do not wait by themselves. Weigh asks only when the entry would change a GST return for a month whose filing record says filed. Writing the change into an account is a later step.
For agents
| Step | Tool | What it does |
|---|
| Before a choice | decide with mode weigh | Says go (already approved), ask (put it to the person) or stop (this person may not decide it here). A standing rule the owner already ruled can cover one matching item. That go grants no account write. An agent asking only "Save the note on <topic>?" for its own dated work note goes ahead on its own, whatever words the topic uses; any other wording or a joined act still asks, and anything the note says to do needs its own weigh. |
| Ask | decide with mode ask, or a push | Raises one decision and returns its key. The owner's push of a file they rule on holds the exact change the answer approves. An ask can also name when it is due, how soon to answer it, links to the evidence, and one line when the person must sign in and do it. |
| Record the answer | decide (its default mode, record) | Records the person's words with the key, yes, no or changes, and where they said it. Never record your own answer. An answer to a weighed choice comes back with its own key; pass that key to mode list to see when the change is saved. |
| Retire a question | decide with mode withdraw | Retires your own pending question. The owner, a co-owner, or the chief of staff can also retire a question they can read when events have overtaken it, up to 20 at once, with one reason. Nothing is decided. |
| Rank an open question | decide with mode priority | Says how soon one should be answered: 1 answer first, 2 soon, 3 can wait. It does not answer the question. |
| Hear what happened | sync | Brings every answer to your questions since your last sync, with what to do next. A question retired because events overtook it is named here. |
| Check where things stand | decide with mode list | Lists what still waits on the person and what they answered this week, including a decision kept in the core area that another agent recorded, or one decision by its key. On the owner's or a co-owner's connection the waiting list is every open question they may answer, 20 at a time. The id from a weighed choice also reads the answer the owner recorded, when that answer is kept in the core area. By key, a change not saved yet comes back with each file's text before and after, and the lines that change, also in the text, so you can propose it again. Read it before asking again. Search finds the person's words and names that key. |
Each tool's inputs and results are on MCP tools.
Over HTTP
A bot with a member key uses the same reads over HTTP:
GET /api/decisions returns what decide with mode list returns. Add ?key= for one decision.
- The decision page,
/d/:key, is where a signed-in owner, or a co-owner for the decisions they may answer, reads and answers it in the browser.
Recording an answer stays on MCP (decide, mode record), the decision page, Your call and a Page that shows that decision, so it always comes from the person's own connection. Every route is on HTTP API, and sign-in is on Sign-in and errors.