Approve gates and respond to user_input nodes via CLI

When a dagraph run reaches an approval_gate or user_input node, it pauses and waits for a human decision. The approve and respond commands let you record that decision from the terminal. After either command, re-run the DAG with --run-id to resume execution from where it stopped.

approve
respond

agentgraph approve

Use approve to record a human decision on a paused approval_gate node — either approving it so the run continues, or rejecting it to mark the run as failed.

agentgraph approve <run_id> <node_id> [OPTIONS]

Arguments and flags

string

required

The run ID that contains the pending approval gate. Find it with agentgraph list --status paused.

string

required

The ID of the approval_gate node to act on. The node must be in awaiting_approval status.

string

default:"runs"

Runs directory. Must match the --runs-dir used when the DAG was originally run.

boolean

Reject the gate instead of approving it. The node is marked failed and the run does not continue past this point.

string

Optional reviewer comment stored alongside the decision. Visible in the artifact and in audit logs.

string

Override the approver identity written to the artifact. Defaults to the value of the $USER environment variable.

Examples

agentgraph approve a1b2c3d4e5f6 review_gate

agentgraph approve a1b2c3d4e5f6 review_gate \
  --comment "Looks good — ship it"

agentgraph approve a1b2c3d4e5f6 review_gate \
  --reject \
  --comment "Output quality is too low; regenerate with a stricter prompt"

agentgraph approve a1b2c3d4e5f6 review_gate \
  --approver alice \
  --comment "Approved in weekly review"

Approve/reject flow

Run the DAG

agentgraph run examples/approval_flow.yaml --input feature="dark mode"

The run pauses at the approval_gate node and prints a summary showing which gates are waiting.

Find the paused run

agentgraph list --status paused

Record your decision

# Approve
agentgraph approve a1b2c3d4e5f6 review_gate --comment "Approved"

# Or reject
agentgraph approve a1b2c3d4e5f6 review_gate --reject --comment "Try again"

Resume the run

agentgraph run examples/approval_flow.yaml --run-id a1b2c3d4e5f6

Nodes that already completed are skipped. Execution continues from after the gate (if approved) or stops (if rejected).

agentgraph respond

Use respond to supply a value to a paused user_input node. The node supports three input types: text (free-form string), select (one of a fixed list of options), and confirm (yes/no).

agentgraph respond <run_id> <node_id> <value> [OPTIONS]

Arguments and flags

string

required

The run ID that contains the pending user_input node.

string

required

The ID of the user_input node to respond to. The node must be in awaiting_user_input status.

string

required

The response value. For select nodes, must be one of the declared options. For confirm nodes, must be yes, no, y, n, true, or false.

string

default:"runs"

Runs directory.

string

Path to the DAG YAML file. When provided, agentgraph validates value against the node’s declared input_type and options before writing the response.

Examples

agentgraph respond a1b2c3d4e5f6 audience_input \
  "senior software engineers with distributed systems experience"

agentgraph respond a1b2c3d4e5f6 tone_select "professional" \
  --dag examples/blog_writer.yaml

agentgraph respond a1b2c3d4e5f6 publish_confirm yes \
  --dag examples/publish_flow.yaml

Resume after responding

After recording the response, resume the run with:

agentgraph run examples/my_dag.yaml --run-id a1b2c3d4e5f6

Both approve and respond only update the local run state. They do not trigger execution — you must run the DAG again with --run-id to continue.

​agentgraph approve

​Arguments and flags

​Examples

​Approve/reject flow

​agentgraph respond

​Arguments and flags

​Examples

​Resume after responding

agentgraph approve

Arguments and flags

Examples

Approve/reject flow

agentgraph respond

Arguments and flags

Examples

Resume after responding