AI Session Tracking
Every AI session, tracked from first prompt to last. Because 'I think it was Tuesday' is not auditing.
Questions this answers
- How to track AI coding sessions in my terminal?
- How long did my Claude Code session last?
- Session history for AI coding agent interactions
- Track AI agent runs and session duration in terminal
How it works
Chau7 automatically groups AI agent activity into sessions. A session begins when an AI agent is detected in a tab and encompasses all runs, tool calls, and API interactions that occur until the agent exits. Each session is assigned a unique ID and tracks its start time, duration, run count, and associated tab.
Sessions are queryable through the MCP server. You can list all sessions, filter by repository path or active status, and drill into individual sessions to see their constituent runs and tool calls. This gives you a structured history of your AI-assisted development activity.
The session model is designed for multi-agent workflows. Each tab maintains its own session independently, so running Claude Code in three tabs produces three distinct, non-overlapping sessions with their own metrics.
Why it matters
Without session tracking, AI agent usage is ephemeral. You finish a coding session and have no record of how many runs it took, how long each one lasted, or what the cumulative cost was. Chau7 groups related AI interactions into sessions with run counts, duration, and cost attribution so you can answer 'how much did that feature cost to build with AI?'
Frequently asked questions
How do I view past sessions?
Use the MCP server's session_list endpoint to list sessions with optional filters for repository path and active status. Each session includes its run count, start time, and associated tab information.
Can I tag or annotate sessions?
You can tag individual runs within a session using the MCP server's run_tag endpoint. Tags propagate to session-level queries, making it easy to categorize and search your session history.
Are sessions preserved after restarting Chau7?
Yes. Session and run data are persisted to disk and survive application restarts. Your full session history is retained for future queries.