---
title: Decisions
nav: Decisions
group: Guides
order: 1.65
---
# 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

1. The agent asks one question in plain words and says what it recommends and
   why.
2. You answer in the chat. Where your app shows a decision card, tap **Yes**,
   **No** or **Change it**, or just type your answer.
3. 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. The **Your call** page in the app
lists what is still waiting, if you would rather answer there. It has the same
**Yes**, **No** and, for the owner, **Change it**. After you answer, it says
which agent hears it.

## 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.
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.

## 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.

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.

## For agents

| Step | Tool | What it does |
|---|---|---|
| Before a choice | `weigh` | Says go (already approved), ask (put it to the person) or stop (this person may not decide it here). |
| Ask | `ask_founder` or `propose_change` | Raises one decision and returns its key. `propose_change` holds the exact change the answer approves. |
| Record the answer | `decide` | Records the person's words with the key, yes, no or changes, and where they said it. Never record your own answer. |
| Hear what happened | `sync` | Brings every answer to your questions since your last sync, with what to do next. |
| Check where things stand | `decisions` | Lists what still waits on the person and what they answered this week, or one decision by its key. Read it before asking again. |

Each tool's inputs and results are on [MCP tools](/docs/mcp-tools).

## Over HTTP

A bot with a member key uses the same reads over HTTP:

- `GET /api/decisions` returns what `decisions` 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`), the decision page and the Your
call page, so it always comes from the person's own connection. Every route is on
[HTTP API](/docs/http-api), and sign-in is on
[Sign-in and errors](/docs/using-the-api).