Operator Tasks - GroundForge

When a Gateway rule uses Review, GroundForge creates an Operator Task instead of running the capability immediately. The task shows the available request context, including the Agent, Channel, Gateway, capability, input, Workspace, and linked Trace.

Approve

Approve when the requested capability and input are acceptable. GroundForge records the decision and continues the reviewed request.

Reject

Reject when the action should not run. The capability is not called, and the request ends with a rejection result.

CLI example

gforge operator tasks list --status pending
gforge operator tasks describe <task-id> -o yaml

gforge operator tasks approve <task-id> \
  --comment "Verified the requested ticket and action"

Use reject instead of approve when the action should not run:

gforge operator tasks reject <task-id> \
  --comment "The requested action is outside the approved scope"

Screenshot placeholder
Add /images/governance/operator-task.png showing the Agent, Channel, request preview, Gateway, capability input, comment field, and decision controls.

See Request Review and CLI governance.

Last modified on July 27, 2026

Related topics

Governance Get Operator Task Decide Operator Task List Operator Tasks