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, which gate an action; a question is the agent asking you something. A question has anid, 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
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
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.
