Appearance
AI Telemetry
AI Telemetry captures usage data from AI coding tools across your engineering organization — token consumption, costs, session activity, and CapEx classification — without changing how engineers work.
What It Does
- Automatic session capture from 9 supported tools
- Token and cost tracking per engineer, team, and project
- CapEx/R&D classification for tax relief reporting
- Zero-config for engineers (CLI installer handles setup)
Supported Tools
| Tool | Collection Method | Prompt Capture |
|---|---|---|
| Claude Code | OTel (native) | Opt-in (--prompts) |
| GitHub Copilot | OTel (VS Code) | Opt-in (--prompts) |
| Cursor | Editor hooks | Always on |
| Windsurf | Editor hooks | Always on |
| Gemini CLI | OTel (native) | Opt-in (--prompts) |
| Codex CLI | OTel (native) | Opt-in (--prompts) |
| Aider | OTel | Always on |
| Qwen Code | OTel (native) | Opt-in (--prompts) |
| OpenCode | OTel (native) | Always on |
What Gets Tracked
For every AI coding session:
- Token counts — input, output, and cache-read tokens per model
- Cost — estimated USD cost based on provider pricing
- Session metadata — duration, tool calls, files modified, lines added/removed
- Git context — branch, repository, commit messages (when available)
- Classification — project attribution and CapEx eligibility (automated)
WARNING
For Claude Code, Copilot Chat, Gemini CLI, Codex CLI, and Qwen Code, prompt capture is opt-in via the --prompts flag. For Cursor, Windsurf, Aider, and OpenCode, prompt content is captured by default when telemetry is configured.
How It Works
- Engineers install
flowstate-telemetryCLI or configure their tool manually - AI tool usage emits OpenTelemetry data to the Flowstate telemetry service
- Sessions are aggregated, classified (project + CapEx category), and stored
- Data appears in the Flowstate AI Workforce dashboard
Next Steps
- Engineers: Setup guide — get telemetry running in under 5 minutes
- Tool-specific config: Claude Code, GitHub Copilot, Cursor, and more