/session:status

Display a formatted table of all registered sessions, showing which are currently active.

Quick Start

Copy/agileflow:session:status

Example Output

┌─────┬──────────────────────────────┬────────────┬─────────┬────────────┐
│ ID  │ Path                         │ Branch     │ Status  │ Nickname   │
├─────┼──────────────────────────────┼────────────┼─────────┼────────────┤
│ 1   │ /home/user/myproject         │ main       │ active  │ (main)     │
│ 2   │ /home/user/myproject-auth    │ session-2  │ active  │ auth       │
│ 3   │ /home/user/myproject-3       │ session-3  │ stale   │ -          │
└─────┴──────────────────────────────┴────────────┴─────────┴────────────┘

Active: 2    Stale: 1

Current session: 1

To switch sessions, run /agileflow:session:resume
To create new session, run /agileflow:session:new

Status Values

Session Detection

Sessions are detected using PID-based locking:

1. Each session creates a lock file with its process ID
2. Status check verifies if each PID is still running
3. Stale locks are automatically cleaned on next startup

Use Cases

Before Starting Work

Check if other sessions are already working on something:

Copy/agileflow:session:status
# See what's active, decide if you need a new session

After Returning to Work

Find out which sessions exist and their state:

Copy/agileflow:session:status
# Review sessions, then:
/agileflow:session:resume  # to switch to one

Debugging Conflicts

If you suspect session conflicts:

Copy/agileflow:session:status
# Check for multiple "active" sessions
# Stale sessions may need cleanup

Related Commands

• /session:new - Create a new parallel session
• /session:resume - Switch to another session
• /session:end - End current session
• /session:init - Initialize session system