diff --git a/docs/public/workflows/human-in-the-loop.mdx b/docs/public/workflows/human-in-the-loop.mdx index f1cb0bfa7..934e50b77 100644 --- a/docs/public/workflows/human-in-the-loop.mdx +++ b/docs/public/workflows/human-in-the-loop.mdx @@ -19,6 +19,14 @@ approve -> skip [label="[S] Skip"] When execution reaches the gate, the user sees the previous stage's output followed by the node's label ("Approve Plan") and the available options. In the CLI, this appears as an interactive menu. In the web UI, blocked runs show an interview dock on the run page where the user can answer the pending question. + +`fabro approve` and `fabro deny` grant or deny permission to **start a run** waiting +for execution approval. To answer a human gate during execution, use the +interactive CLI prompt or the run page's interview dock. API clients can list +pending questions with `GET /api/v1/runs/{id}/questions` and answer a specific +question with `POST /api/v1/runs/{id}/questions/{qid}/answer`. + + ### Keyboard accelerators The prefixes `[A]`, `[R]`, `[S]` in edge labels serve as keyboard accelerators. Fabro supports three formats: