Use case
Claude Code cost tracking for parallel sessions
Canopy helps developers understand what each Claude Code session is spending while it runs across branches and worktrees.
Track cost and tokens while the session runs
Canopy shows Claude Code session metrics in the Inspector so you can see cost, input tokens, output tokens, cache reads, and context usage while work is still in progress.
- See the active session cost without parsing terminal output.
- Compare token usage across worktrees.
- Use context-window visibility to decide when a session needs a reset or narrower task.
Useful when many branches are active
When several agents are running, the Inspector shows which worktree used the most tokens and context.
No billing proxy
Billing stays with Claude Code and its provider. Canopy reads session output and shows the counters in the desktop app.
Related pages
Inspector feature See session status, tokens, context usage, cost, and tool history.Multiple sessions Track several Claude Code sessions across worktrees.Security and data flow Understand how Canopy handles local app data and agent sessions.Download for Windows Install the signed desktop app and open a local project.