# Ask a person a question mid-task and carry on with the answer

> Ask a person a question mid-task and carry on with the answer: 2 companies fully do it, 7 with a limit, 11 carry the tag. Every listing in Human approval & handoff with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/human-in-the-loop.ask-question/
- Markdown: https://www.anchorterminal.com/niches/human-in-the-loop.ask-question/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/human-in-the-loop.ask-question/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/human-in-the-loop.ask-question/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 7 | 11 | 11 | 4 |

## What counts as done

The question reaches the right person, the answer comes back typed (an option or text) with who answered, and the agent uses it in its next step; with no answer it does not proceed on its own guess unless told to.

How agents ask for it: which customer did you mean; ask finance whether to refund; check with me if anything's unclear

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **gotoHuman (gotoHuman UG (haftungsbeschränkt))**: Review types take dropdown, checkbox, button and text input fields; the webhook returns the filled data with respondingUser and respondedAt. assignTo routes to named reviewers (Team plan and above).
- **Orkes Conductor Human tasks (Orkes, Inc.)**: User forms collect typed fields, validated on submit, and the form response is the task output; assignment targets a user or group, and the trigger context carries assignee and claimant.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Big Arrow (Franz Enzenhofer (individual, Vienna))**: --ask (typed reply) and --choice (2 to 6 options) return JSON answers by row id, and exit 1 when the card is closed unanswered. The answerer is whoever sits at that Mac; no identity is returned.
- **Hatchet (Hatchet Technologies, Inc.)**: The event payload can carry any typed answer and who gave it, but Hatchet neither asks the person nor records the answerer; both are the builder's code.
- **Inngest (Inngest Inc)**: The resuming event or signal can carry any typed answer and the answerer, but Inngest neither asks the person nor records who answered; both are builder code.
- **Pushary (RalphNex OÜ)**: ask_user takes confirm, select (2 to 6 options) or input and returns value and note with a status; expired is documented as not approval. Teams record the answerer by name, but the tool result is not shown to carry who answered.
- **Restate (Restate GmbH)**: The resolution carries any JSON answer, so options or text work, but Restate neither asks a person nor records who resolved it; both are builder code.
- **Temporal (Temporal Technologies Inc.)**: A Signal or Update can carry any typed answer and the approver's identity, but Temporal neither asks the person nor verifies who answered; the page tells builders to validate approver permissions themselves.
- **Trigger.dev (API Hero Ltd)**: Token output is any typed JSON, so options or text work, but the person is reached by builder code and nothing records who completed the token.

- not this job: Permit MCP Gateway (Permit Inc.): Approve or reject only, with a rejection reason; there is no question, option or free-text answer type.
- not this job: withHuman (Metoro Inc): Approve or deny only, with an optional note; issue 144 asking for a question tool is still open.

## What stops agents finishing

- approval-only product with no question type
- question routed to the operator when someone else holds the answer
- short wait cap returns before the person can answer

## Around it

Before: agent-harnesses.run-agent. After: human-in-the-loop.approve-action.

## Where this comes from

Weight 11 of 100 in Human approval & handoff: 4 of 26 accounts (Call a Human MCP, TTal mid-job blockers, Claude Code AskUserQuestion, withHuman ask_human request)

As data: https://www.anchorterminal.com/api/v1/use-cases/human-in-the-loop.ask-question.json, or the MCP tool get_use_case with id human-in-the-loop.ask-question. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
