agent-status

Synopsis


aigon agent-status <status> [message]

Description

Sets the current agent’s status in the Aigon state system. This is called by agent workflows and can be used manually to signal status changes.

The status is written to .aigon/state/feature-{id}-{agent}.json in the main repo, where the dashboard reads it to show real-time agent progress.

Valid statuses

Active

Status	Meaning
`implementing`	Agent is actively working on the feature
`reviewing`	Agent is conducting a code review
`revising`	Agent is addressing review feedback
`spec-reviewing`	Agent is reviewing the spec

Completion

Status	Meaning
`implementation-complete`	Agent has finished initial implementation
`revision-complete`	Agent has finished addressing review feedback
`review-complete`	Agent has finished the code review
`spec-review-complete`	Agent has finished the spec review
`research-complete`	Agent has finished research findings

Other

Status	Meaning
`waiting`	Agent needs human input before continuing
`error`	Agent encountered an error
`awaiting-input`	Agent is blocked waiting for a specific prompt response

Deprecated aliases

The CLI still accepts the following legacy signals for backward compatibility, but remaps them to the canonical names above before any state is written.

Alias	Remap rule
`submitted`	Remapped to `implementation-complete` by default, or `revision-complete` if the recorded session `taskType` is `revise`, or `research-complete` if the entity type is `research`.
`feedback-addressed`	No-op alias; agents must call `revision-complete` to advance state.

Usage


# From inside a feature worktree:
aigon agent-status implementation-complete
 
# Signal review completion:
aigon agent-status review-complete
 
# Block with a message explaining what's needed:
aigon agent-status awaiting-input "Pick which features to create"
 
# The command auto-detects the feature ID and agent from the branch name

Notes

Must be run from a feature branch or worktree — the feature ID and agent are parsed from the branch name
Status changes trigger dashboard notifications (if enabled)
Typically called as part of the implementation workflow rather than directly