Supported Agents
Tempest supports multiple AI coding agents out of the box. This guide covers the exact CLI commands, configuration options, and integration details for each agent.Agent Configuration System
Each agent in Tempest is defined by anAgentConfig object with the following properties:
The
{UUID} placeholder is replaced by Tempest with the actual session or conversation UUID.
Claude Code
Display Name: Claude CodeCLI Command:
claudeResumable: Yes (by conversation ID)
Launch Command
First spawn:Configuration
Claude Code reads configuration from:~/.claudedirectory (user home)- Environment variables (e.g.,
ANTHROPIC_API_KEY) - MCP configuration from
.mcp.jsonin the project root (if Token Intelligence is enabled)
API Key Setup
Set your Claude API key via the Claude CLI:~/.claude/config.json so Tempest can access them.
Model Selection
Claude Code uses the model configured in your Claude CLI settings. To change the model:Tempest Integration
- Session ID: Persisted as
conversationIdin localStorage - Work-Done Detection:
- Primary: OSC 9 notification signal at turn completion
- Secondary: Title-based detection (title starts with
✳for idle, Unicode spinners for busy) - Fallback: Quiet timer (5 seconds no output)
- MCP Support: Enabled by default if Token Intelligence is configured
- Tab Badge: Shows ”✳ Claude Code” title when idle
- Auto-approve flag:
--dangerously-skip-permissions— appended by default; disables all tool-call confirmation prompts
Troubleshooting
If Claude Code doesn’t launch:- Ensure
claudeis installed:which claude(macOS/Linux) orgcm claude(Windows) - Run
claude configureto set up your API key - Test in a terminal:
claude --helpshould print the help menu - Check that the API key is valid by running
claudein the terminal
Gemini CLI
Display Name: Gemini CLICLI Command:
geminiResumable: Yes (by conversation ID)
Launch Command
First spawn:Configuration
Gemini CLI reads configuration from:~/.geminidirectory (user home)- Environment variables (e.g.,
GOOGLE_API_KEY,GOOGLE_PALM_KEY) - MCP configuration from
.gemini/settings.jsonin the project root (if Token Intelligence is enabled)
API Key Setup
Set your Google API key via the Gemini CLI:Model Selection
Gemini CLI uses the model configured in your settings. To change the model:Tempest Integration
- Session ID: Persisted as
conversationIdin localStorage - Work-Done Detection:
- Primary: OSC 9 notification signal at turn completion
- Secondary: Title-based detection (title starts with
◇for idle,✦or✋for busy) - Fallback: Quiet timer (5 seconds no output)
- MCP Support: Enabled if Token Intelligence is configured (writes to
.gemini/settings.json) - Tab Badge: Shows title with busy/idle indicators
- Auto-approve flag:
--yolo— appended by default; puts Gemini CLI into full auto-approval mode
Troubleshooting
If Gemini CLI doesn’t launch:- Ensure
geminiis installed:which gemini(macOS/Linux) orgcm gemini(Windows) - Run
gemini configureto set up your API key - Test in a terminal:
gemini --helpshould print the help menu - Check that the API key is valid by running
geminiin the terminal
Opencode
Display Name: OpencodeCLI Command:
opencodeResumable: Yes (session ID captured from output)
Launch Command
First spawn:Session ID Capture
Unlike Claude Code or Gemini CLI, Opencode does not accept a--session-id flag on first spawn. Instead, it prints a session ID to stdout when it starts. Tempest captures this ID using a regex pattern:
Configuration
Opencode reads configuration from:opencode.jsonoropencode.jsoncin the project root- Environment variables
- MCP configuration under
mcp.atlasin the config file (if Token Intelligence is enabled)
MCP Configuration (Atlas)
If Token Intelligence is enabled, Tempest writes:Tempest Integration
- Session ID: Captured from output on first spawn, then persisted as
conversationId - Work-Done Detection: Uses standard heuristics (quiet timer, signal-based detection)
- MCP Support: Writes to
opencode.jsoncoropencode.json - Resume Behavior: Uses
-s <captured-id>flag on reopening
Troubleshooting
If the session ID is not captured:- Check that Opencode prints a UUID to stdout on startup
- Run Opencode in a terminal and look for UUID output:
opencode - If Opencode prints a different ID format, the regex pattern in
NewSessionMenu.tsxmay need tuning - Check the Tempest logs (DevTools console) for capture errors
Copilot CLI
Display Name: Copilot CLICLI Command:
gh copilotResumable: No (stateless)
Launch Command
Configuration
Copilot CLI reads configuration from:- GitHub CLI config (
~/.config/gh/config.ymlon macOS/Linux) - GitHub authentication token (use
gh auth loginto set up)
Authentication
Authenticate with GitHub:Tempest Integration
- Session ID: Not persisted (stateless sessions)
- Resumption: Not supported; each spawn creates a fresh session
- Work-Done Detection: Uses heuristics and signal detection
- Limitations: Copilot CLI is designed for one-off suggestions, not persistent conversations
Use Cases
- Quick code suggestions
- Testing command generation
- One-off questions without conversation context
Cline
Display Name: ClineCLI Command:
clineResumable: No (stateless)
Launch Command
Configuration
Cline reads configuration from:~/.clinedirectory (user home)- Environment variables (model selection, API keys)
- Project-level configuration files
API Key Setup
Set your Anthropic API key:Tempest Integration
- Session ID: Not persisted
- Resumption: Not supported; each spawn creates a fresh session
- Work-Done Detection: Uses signal detection and heuristics
- Model Support: Typically runs Claude models; configuration via environment
Troubleshooting
If Cline doesn’t launch:- Ensure
clineis installed:which cline(macOS/Linux) orgcm cline(Windows) - Set your API key:
export ANTHROPIC_API_KEY="your-key" - Test in a terminal:
cline --helporclineto start a session
Cursor Agent
Display Name: Cursor AgentCLI Command:
cursorResumable: No (stateless)
Launch Command
Configuration
Cursor Agent reads configuration from:- Cursor IDE settings (if the user also has Cursor installed)
- Environment variables
.cursor/mcp.jsonfor MCP configuration (if Token Intelligence is enabled)
MCP Configuration
If Token Intelligence is enabled, Tempest writes:Tempest Integration
- Session ID: Not persisted
- Resumption: Not supported; each spawn creates a fresh session
- Work-Done Detection: Uses signal detection
- MCP Support: Writes to
.cursor/mcp.jsonif Token Intelligence is configured
Troubleshooting
If Cursor doesn’t launch:- Ensure the Cursor CLI is installed:
which cursororgcm cursor - Cursor may require the Cursor IDE to be installed or configured
- Check Cursor’s documentation for CLI setup
Goose
Display Name: GooseCLI Command:
gooseResumable: No (stateless)
Launch Command
Configuration
Goose reads configuration from:~/.goosedirectory (user home)- Environment variables
- Project-level configuration files
API Key Setup
Set your API key (if required):Tempest Integration
- Session ID: Not persisted
- Resumption: Not supported; each spawn creates a fresh session
- Work-Done Detection: Uses signal detection and heuristics
- Limitations: Designed for autonomous task execution without persistent conversation
Use Cases
- Autonomous task execution
- One-shot agents that solve specific problems
- Testing and automation workflows
Troubleshooting
If Goose doesn’t launch:- Ensure
gooseis installed:which goose(macOS/Linux) orgcm goose(Windows) - Check that any required environment variables are set
- Test in a terminal:
goose --helporgooseto start
Antigravity
Display Name: Antigravity CLI Command:agy
Resumable: No (stateless — resumes last session via --continue)
Launch Command
First spawn:Tempest Integration
- Session ID: Not persisted (no externally addressable session ID)
- Resumption:
--continueresumes the most recent session in the current directory - Work-Done Detection: Uses signal detection and heuristics
- Auto-approve flag:
--dangerously-skip-permissions— appended by default
Troubleshooting
If Antigravity doesn’t launch:- Ensure
agyis installed and on your PATH - Test in a terminal:
agy --help
Codex CLI
Display Name: Codex CLI CLI Command:codex
Resumable: Yes (resumes last session in CWD via subcommand)
Launch Command
First spawn:Tempest Integration
- Session ID: Not persisted (no externally addressable session ID; resume is CWD-based)
- Resumption:
codex resume --lastpicks up the most recent Codex session in the working directory - Work-Done Detection: Uses signal detection and heuristics
- Auto-approve flag:
--dangerously-bypass-approvals-and-sandbox— appended by default
Troubleshooting
If Codex CLI doesn’t launch:- Ensure
codexis installed:which codex(macOS/Linux) orgcm codex(Windows) - Test in a terminal:
codex --help
Comparison Table
Adding a New Agent
To add support for a new agent to Tempest:-
Define the agent config in
src/components/NewSessionMenu.tsx: -
Provide an icon as an SVG file in
src/assets/agent-icons/ -
Implement work-done detection (if needed):
- Add title-based classification to
sessionManager.tsclassifyTitle()method if your agent sets a title - Test that the agent’s terminal output triggers the work-done state correctly
- Add title-based classification to
-
Test the agent in Tempest:
- Launch a new session with your agent
- Verify the command is constructed correctly
- Confirm work-done detection fires at the right time
- Test resumption if your agent supports it