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. Every question and what came back is kept with the session at agent-sessions/<session id>/. The session’s debrief comes back in its result, not as a question.

Experts on Slack: ask_human

For teams that run an expert channel. Opens one question in a Slack thread and returns its id at once. A reply agent owns the thread to its close and banks each answer where the asking pass reads it.
ask_human with questions: "open" opens one consult from a task’s open yes/no questions (<task>/sme/questions.json), skipping answered ones. list_consults lists yours, or reads one thread whole by consult_id. Only you read your consults.

Parked passes

When the model API turns a pass away, it parks with what it spent. list_parked shows yours; resume_parked respawns them once the API answers. A sweep does the same every fifteen minutes. The Slack tools and parked passes are on kennet:l3.