answer-agent
Provide answers to pending agent questions and resume paused execution. Supports single or multi-question responses.
Instructions
Submit an answer to a pending question from an agent. When an agent pauses because it asked a question, use this to respond and resume execution.
When to call: Read task:///all — tasks with status waiting_answer have a "Pending Questions" section showing the question, choices, and an example answer-agent call.
Single-question flows (Copilot / Claude): Use the answer field.
Choice by number:
"1","2","3"— selects the corresponding optionChoice by text: Exact text of a choice option
Custom answer:
"OTHER: your custom text"— for freeform responses when choices don't fit
Multi-question flows (Codex): Use the answers field with a map of question IDs to answers.
Read task:///{id} → pending_question.structured_questions to get question IDs.
Examples:
answer-agent { "task_id": "abc123", "answer": "2" }
answer-agent { "task_id": "abc123", "answer": "OTHER: Use TypeScript instead" }
answer-agent { "task_id": "abc123", "answers": { "q_build_system": "1", "q_language": "TypeScript" } }Find pending questions: Read task:///all — look for the "Pending Questions" section.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| answer | No | Single answer for single-question flows (Copilot/Claude): choice number (1, 2, 3...), exact choice text, or "OTHER: your answer". Mutually exclusive with answers. | |
| answers | No | Multi-question answer map for Codex flows: { "<questionId>": "<answer>" }. Read task:///{id} → pending_question.structured_questions[].id to get question IDs. Mutually exclusive with answer. | |
| task_id | Yes | Task ID with pending question. Find via task:///all — look for waiting_answer status. |