Supported Coding Agents
The gateway watches the local session files of four coding agents. No agent configuration is required — if an agent below is installed and you use it, the gateway picks up its activity automatically.
| Agent | What is read | Platforms |
|---|---|---|
| Claude Code | Session transcripts written under ~/.claude/projects/ | macOS, Linux, Windows |
| Cursor | Chat and composer history from Cursor’s local workspace storage | macOS, Linux, Windows |
| Codex | Session rollout files and local session state | macOS, Linux, Windows |
| Claude Desktop | Agent-session audit logs written by Claude Desktop’s agent (Cowork) mode | macOS |
Use proxai-gateway status to see live per-agent capture counts, or filter
the record ledger by agent:
proxai-gateway logs --source claude-codeThe --source filter accepts claude-code, cursor, codex, and
claude-desktop.
What is captured
From each session the gateway captures the conversation itself and the context needed to make it useful in the dashboard:
- User prompts and assistant responses
- The working directory and git branch the session ran in
- Tool calls made by the agent
- Session and message identifiers, timestamps, and the agent version
What is not captured
- Secrets — API keys, tokens, credentials, and connection strings are redacted on your machine before anything is stored or uploaded. See Data & Privacy.
- Non-dialogue noise — each agent has a dedicated filter that keeps only genuine dialogue content and trims oversized or non-dialogue fields before redaction.
- Network traffic — the gateway never proxies or inspects requests; it only reads the files listed above.
New agents
Support for additional agents ships through regular gateway releases. Because the gateway keeps itself up to date, new sources become available without re-installation.
Last updated on