human-tasks

Workflow blockers requiring human action are handled by creating explicitly labeled [HUMAN] tasks. The agent blocks its current task, notifies the orchestrator, and resumes immediately once the human completes the manual step.

Human-in-the-loop task routing separates genuine capability blockers from missing permissions. You need it when a workflow stalls on decisions, credential entry, or physical actions that only a human can complete.

Create a task titled starting with [HUMAN], assign it to a human, place it in the human-tasks project, and write actionable step-by-step instructions specific enough to complete without follow-up questions.

Yes, notification triggers surface the [HUMAN] task in the dashboard and notify the orchestrator. The agent pipeline resumes immediately upon receiving the task completion notification.

A permission issue is a missing access right, while a human capability blocker is a genuine dependency requiring manual decisions, payments, or physical actions. This routing frames the latter as a [HUMAN] task.

Agent workflows stall when the next step is impossible without human input. Unblock it by routing the dependency as a [HUMAN] task with correct assignee and project flags, blocking the agent until completion.