> ## Documentation Index
> Fetch the complete documentation index at: https://docs.erdo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Questions

> List the questions an agent is waiting on and answer them over MCP, REST, or the CLI

# Questions

When an agent needs a decision or a missing detail, it stops and asks. In the app
the question appears as a card in the conversation, with its options. Questions
give you the same cards, with the same text and options, from the CLI, REST and
MCP. They are separate from [approvals](https://docs.erdo.ai/approvals.md), which gate an action; a
question is the agent asking you something.

A question has an `id`, the thread it is in, and a `status`: `pending` while the
agent is waiting, `answered` once you have replied in the thread. A card holds one
or more questions. Each has a `label`, a `type` (`choice` or `text`), its
`options`, whether it takes several answers (`multi_select`), and whether it is
`required`.

## CLI

```bash theme={null}
erdo questions list                      # open questions across your recent threads
erdo questions list --thread <thread>    # one thread
erdo questions list --thread <thread> --all   # include earlier, answered questions

erdo questions answer <id> --option "Warm"        # pick an offered option
erdo questions answer <id> "Use the 2024 price"   # free text, or another answer to a choice
erdo questions answer <id> --answer tone=Warm --answer channels=email,sms --answer price=2m
erdo questions answer <id> --option "Warm" --no-wait
```

`answer` sends the same reply the app's card sends, so the agent resumes exactly
as if you had clicked it, then waits for the agent's next reply. `--no-wait`
prints the thread, message and invocation ids and returns; follow it with
`erdo agent wait <thread> --invocation <id>`. Without `--thread`, the thread is
found from your open questions. Listing without `--thread` checks your most
recent threads (add `--org` for the whole organization) and says when older
threads were not checked.

An answer must match the card: an option has to be one the card offers (use text
for anything else), a single-select question takes one answer, and every required
question needs one. An already answered question is refused, naming the open one.

## REST

| Method | Path | Purpose |
| - | - | - |
| `GET` | `/v1/questions` | List questions; `thread_id`, `include_answered` and `scope` (`own` or `org`) narrow it |
| `POST` | `/v1/threads/{threadID}/questions/{questionID}/answer` | Answer one: `options` and `text` for a one-question card, `answers` (`question_id`, `options`, `text`) for several; `async` returns the invocation id |

The answer response carries `reply_sent`, the exact message that was sent, with
the send acknowledgement (`thread_id`, `message_id`, `invocation_id`, `status`).

## MCP

`erdo_list_questions` and `erdo_answer_question` take the same inputs as the REST
endpoints.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.