Find the sessions worth investigating
The desktop app captures analytics from Claude Code and Codex CLI, plus Cursor on macOS. Sessions are parsed locally, with redacted excerpts for investigation. Full conversation archiving is in development.
Track estimated spending, growing context, and tool failures across coding sessions. Capture analytics with the desktop app, or connect your SDK to track model-call costs and performance. Compare the data over time in your dashboard.
Already invited to the private alpha?
Open your dashboardCompare model costs and response times. See which coding sessions accumulate context or run into tool failures. Use the dashboard and analytics tools to investigate what changed.
The desktop app captures analytics from Claude Code and Codex CLI, plus Cursor on macOS. Sessions are parsed locally, with redacted excerpts for investigation. Full conversation archiving is in development.
Capture estimated costs, token usage, latency, and errors as model responses stream. Compare usage over time and inspect captured requests when something goes wrong.
Connect supported tools once, then collect data as you use them. Open Trace Flow when you want to understand the cost or investigate a problem.
Install the desktop app for coding-agent analytics, or point your existing SDK at Trace Flow for model API capture.
Model responses keep streaming. The desktop app syncs coding-session analytics in the background so you can keep working.
Filter by provider, model, source, or repository. Compare costs and performance across the work you have captured.
Capture coding-session analytics without changing your workflow. The desktop app runs in your menu bar or system tray.
Connect the Trace Flow desktop app to your account. Available for macOS and Windows.
Review the detected sources, then choose Start syncing. Capture analytics from Claude Code and Codex CLI, plus Cursor on macOS.
The app syncs in the background as you work. Open your dashboard to investigate costs and performance, or pause syncing from the tray.
The proxy path starts with a base URL and one Trace Flow header.
import OpenAI from 'openai';
const client = new OpenAI({
apiKey: process.env.OPENAI_API_KEY,
});import OpenAI from 'openai';
const client = new OpenAI({
apiKey: process.env.OPENAI_API_KEY,
baseURL: 'https://gateway.trace-flow.dev/openai/v1',
defaultHeaders: {
'X-Trace-Flow-Api-Key': process.env.TRACE_FLOW_API_KEY,
},
});Trace Flow keeps analytics from coding sessions and model calls so you can investigate costs and performance over time.
Keep cost and usage trends you can revisit as your tools and habits change. Monthly model usage totals are retained for five years; coding-agent analytics for one year. Individual model traces have shorter, plan-based access windows.
Filter analytics in the dashboard or query them through MCP. Coding-session capture includes redacted excerpts for investigation; it does not upload full transcripts.
Read the retention policy