Supported Session Management
Supported Session Management
Operator supports multiple session management backends for running AI coding agents in persistent, manageable terminal sessions.
Available Options
| Option | Status | Notes |
|---|---|---|
| VS Code Extension | Recommended (Preferred) | Integrated terminals in VS Code, works on all platforms |
| tmux | Supported | Terminal multiplexer, ideal for headless/server environments |
| cmux | Supported | macOS terminal multiplexer, manages workspaces within cmux |
| Zellij | Supported | Terminal workspace manager, tab-per-agent model (macOS/Linux) |
How It Works
Session managers provide:
- Persistent terminals: Agent sessions survive disconnects
- Session switching: Move between multiple agents
- Activity tracking: Monitor idle/running states
- Integration: Two-way communication with Operator TUI/API
Choosing a Session Manager
VS Code Extension is the recommended choice for most users. It provides an integrated experience with ticket management, color-coded terminals, and works seamlessly on macOS, Linux, and Windows without additional setup.
tmux remains an excellent choice for headless/server environments, SSH sessions, and users who prefer terminal-based workflows. It’s particularly useful for remote servers where VS Code may not be available.
cmux is a macOS-native option for users already working within cmux. It launches agents as cmux windows or workspaces. Requires macOS and that Operator is running inside a cmux session.
Zellij is a Rust-native terminal workspace manager that works on macOS and Linux. Operator creates a dedicated tab per agent within your existing Zellij session. A good choice for users already working in Zellij who want native tab-based agent management.
Feature Parity: Core Operations
All session management tools support the following Core Operations:
| Operation | TUI | VS Code Extension | REST API |
|---|---|---|---|
| Sync Kanban Collections | S |
Operator: Sync Kanban Collections |
POST /api/v1/queue/sync |
| Pause Queue Processing | P |
Operator: Pause Queue Processing |
POST /api/v1/queue/pause |
| Resume Queue Processing | R |
Operator: Resume Queue Processing |
POST /api/v1/queue/resume |
| Approve Review | Y |
Operator: Approve Review |
POST /api/v1/agents/{id}/approve |
| Reject Review | X |
Operator: Reject Review |
POST /api/v1/agents/{id}/reject |
Core Operations Explained
-
Sync Kanban Collections - Fetch issues from external kanban providers (Jira, Linear) and create local tickets in the queue
-
Pause Queue Processing - Temporarily stop automatic agent launches while maintaining queue state
-
Resume Queue Processing - Continue automatic agent launches after pausing
-
Approve Review - Approve an agent’s pending plan or visual review to continue workflow
-
Reject Review - Reject a review with feedback, triggering the agent to re-do the work