Skip to main content
What a business rule is, what a team intended, whether a scenario could really happen: no check settles these. Consult brings them to a person and keeps the work going while the question is open.

​
In your session: answer_task

A long tool returns a task. When the work behind it needs you (the forge in run_repo_to_tasks asks for discovery, review, a repository question or guidance), the task’s status turns input_required and its inputRequests carry the questions.
A client that speaks MCP Tasks puts the questions to you directly and answers with tasks/update. Any client can call answer_task. The session waits up to ten minutes for an answer, then withdraws the question and goes on without it. The session’s debrief comes back in its result, not as a question.