You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Query APIs and CLI commands that leverage the sidecar tables (tool usage, file operations, commands, git operations, errors, costs) for analytics, filtering, and intelligent recall.
Why
The sidecar tables from Phase 1 store rich structured data but there's no way to query them yet. Developers should be able to ask "what files did I edit today?", "show me all failed commands in project X", or "which sessions cost the most tokens".
Tasks
File activity queries: "what files were touched in session X" / "most-edited files this week"
Tool usage analytics: tool frequency, success rates, average duration per tool
Error analysis: error type distribution, most common errors, sessions with highest error rate
Git activity: commits per session, PR creation timeline, branch activity
Cost tracking: token usage per session/project/day, cost trends, cache hit rates
What
Query APIs and CLI commands that leverage the sidecar tables (tool usage, file operations, commands, git operations, errors, costs) for analytics, filtering, and intelligent recall.
Why
The sidecar tables from Phase 1 store rich structured data but there's no way to query them yet. Developers should be able to ask "what files did I edit today?", "show me all failed commands in project X", or "which sessions cost the most tokens".
Tasks
Files
Acceptance Criteria
Testing