Skip to main content
The status command provides a comprehensive overview of all agent sessions, including PR state, CI status, code review status, and activity monitoring.

Syntax

Options

string
Filter by project ID
flag
Output as JSON for scripting

Basic Usage

Output Format

The status table shows:

Example Output

Status Indicators

CI Status Icons

icon
All CI checks passed
icon
CI checks failed
icon
CI checks pending/running
icon
No CI status (no PR or checks not configured)

Review Decision Icons

icon
Approved
icon
Changes requested
icon
No review yet or no PR

Activity States

state
Agent is currently processing (prompt visible, spinner showing)
state
Agent is waiting for user input (prompt hidden)
state
Agent is executing tools or commands
Activity state is detected by analyzing the terminal output using agent-specific patterns.

Age Format

Time since last activity in human-readable format:
  • 2m - 2 minutes ago
  • 15m - 15 minutes ago
  • 1h - 1 hour ago
  • 3h - 3 hours ago
  • 2d - 2 days ago

JSON Output

Use --json for scripting:

JSON Schema

Field Descriptions

string
Session ID
string | null
Current git branch
string | null
Session status (working, idle, done, killed)
string | null
User-provided or tracker-derived summary
string | null
Agent-generated summary via introspection
string | null
Pull request URL
number | null
Pull request number
string | null
Issue identifier
string
Human-readable time since last activity
string
Project ID
'success' | 'failure' | 'pending' | null
CI pipeline status
'approved' | 'changes_requested' | null
Code review decision
number | null
Number of unresolved review threads
'active' | 'idle' | 'working' | null
Current agent activity state

Filtering

By Project

Combining with Shell Tools

Activity Detection

The CLI detects agent activity by:
  1. Terminal Capture - Reads last 5 lines from tmux pane
  2. Pattern Matching - Uses agent-specific patterns to detect state
  3. Timestamp Tracking - Records tmux activity timestamp

Claude Code Patterns

For claude-code agent:
  • Active: Prompt visible (e.g., claude>, spinner)
  • Idle: No prompt, waiting for input
  • Working: Tool execution, command output
Activity detection works best when the agent is in interactive mode. Background tasks may not update activity state.

Session Summary

The status command shows two types of summaries:
  1. User Summary - From session metadata or issue description
  2. Agent Summary - Extracted from agent’s conversation history
Agent summaries are fetched via agent introspection:
Agent summaries are more accurate for long-running sessions because they reflect actual work done, not just the issue description.

Fallback Mode

If no config is found, status falls back to discovering sessions from tmux:
Fallback mode has limited information. Create a config with ao init for full status reporting.

Common Issues

No Config Found

Solution: Create a configuration:

Unknown Project

Solution: Use a valid project ID:

No Sessions

Solution: Spawn some sessions:

Examples

Monitor All Projects

Check Specific Project

Watch Status (Poll)

Find Failing Sessions

List Stale Sessions

Export Status

Exit Codes

  • 0 - Success
  • 1 - Error (invalid project ID)

Next Steps

Session Management

List, kill, and cleanup sessions

Send Messages

Interact with active sessions

Dashboard

View status in the web interface