Auto AI CLI Detection
See which registered AI CLI a terminal tab is running.
Availability
Implemented in the stable source; configuration and compatibility limits are described below.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Several shell tabs can look alike even when different supported AI CLIs are running.
- New command names and launch wrappers can fall outside a built-in detector.
What ships with it
- Registry of supported command names and output signatures for named AI tools.
- Selected JavaScript package-runner command forms map to registered commands.
- A match supplies an AI display name to the tab session; other telemetry depends on separate integrations.
Questions this answers
- Can my terminal detect AI coding agents?
- How do I know which AI CLI tool is running in my terminal?
- Is there a terminal that tracks Claude Code and Copilot sessions?
- How to monitor AI agents running in terminal tabs?
How it works
The stable v0.5.1 app keeps supported tools in a registry that supplies command names and recognizable output patterns. The registry includes Claude, Codex, Gemini, ChatGPT, GitHub Copilot, Aider, Cursor, Windsurf, Cline, Cody, Amazon Q, Devin, Continue, Goose, Mentat, Amp, and OpenCode.
Detection checks the submitted command and selected output signatures. It also understands defined JavaScript launch forms such as npx, bunx, and selected npm, pnpm, yarn, or bun exec/dlx forms when they resolve to a registered command. This is bounded matching, not coverage of every shell wrapper or every AI CLI.
A match supplies an AI display name to the tab session. Other features can use that name where their own integrations support it; detection alone does not guarantee provider usage, cost, or event telemetry.
Why it matters
When several shells and agents are open, knowing which registered CLI a tab belongs to makes it easier to choose the right session. Chau7 derives a display identity from known commands and output signatures. New or renamed tools may need a registry update, and downstream metrics depend on their separate data sources.
In the Rust/GPUI candidate
Candidate-only detail: commit 350d851b457e maps the package name opencode-ai in selected JavaScript package-manager launch forms. Stable v0.5.1 already detects direct opencode and selected generic package-runner forms, but does not contain that package alias mapping. This unreleased candidate capability is not part of the stable claim.
Candidate features and migration plan. Download links continue to serve the latest stable release.
Frequently asked questions
Which tools are included?
The stable registry includes Claude, Codex, Gemini, ChatGPT, GitHub Copilot, Aider, Cursor, Windsurf, Cline, Cody, Amazon Q, Devin, Continue, Goose, Mentat, Amp, and OpenCode. Detection depends on the command or output signature recognized by that release.
Does it recognize every wrapper or AI CLI?
No. It handles registered command names and selected JavaScript package-runner forms. Unrecognized commands, wrappers, and output formats may not match.
Does recognizing an agent mean its API usage is measured?
No. Detection labels a terminal session. API analytics require the separate local proxy and a supported client configuration; CLI session events and usage metrics also depend on their data sources.