Skip to Content

How do I find the sessions on one git branch in Claude Code?

Rius records the git branch on every Claude Code session the plugin traces, so you find the sessions on one branch by filtering the trace list on the branch field. Each session is one trace, so the filtered list shows one row per session. The branch is recorded whether a folder sends structure only or content.

How it works

  • The Rius plugin turns each Claude Code session into one trace. The trace carries the folder path and the git branch, in both /rius:enable-here (structure only) and /rius:enable-content-here modes. Prompts and replies are not needed to find a branch.
  • The trace list lets you filter on any span or resource attribute your agents send. The branch is one of them, so it appears in the filter’s Field menu with a count of how many spans carry it in the current window.
  • Filters combine with AND and are kept in the URL. A copied link opens the same filtered list.
  • Attribute filters match exact values only. Type or pick the full branch name. To cover several branches, use the is any of operator.
  • Only folders you enabled are traced, so sessions from a folder with tracing off do not appear under any branch. The Claude Code plugin page explains the folder rules.

Set it up

  1. Install the plugin, sign in with /rius:login, and run /rius:enable-here in your repo. /rius:status should read Rius tracing: on on its first line. The Coding agents guide covers the setup in full.

    claude plugin marketplace add glassflow/rius-coding-agents && claude plugin install rius@rius-coding-agents

  2. Work on the branch as usual. Each Claude Code session shows in the trace list while it runs, and shows as in progress until you exit Claude Code.

  3. Open Traces in the console and set the time range. The default is 7 days. Choose 30d or a custom range for older branch work.

  4. Click Add filter. Under Field, pick vcs.ref.head.name, the git branch. Sessions from older plugin versions carry it as cc.git_branch, so add a second filter on that key if you need older work. Choose the operator is, then pick the branch name from the suggestions or type it exactly.

  5. If you are not sure which field it is, open any session you ran on that branch and go to its Raw tab. Find the branch attribute and use its menu, Filter traces by this. The filter chip is created for you, with the key spelled correctly. Use Exclude this value to hide a branch instead.

  6. Narrow the list further. Click a cell in the Sent by column to add that developer to the filter, so you see one person’s sessions on that branch. Use Save current search… under Saved to keep the branch filter, shared with Only me or Everyone in this workspace.

  7. Open a row to read the session as a waterfall of turns, model calls, tool calls and subagents. The Session link in the trace header opens the Spans tab filtered to that session, and pasting a session ID into the Spans search box does the same.

What you get

  • One row per Claude Code session on the branch, with status, agent, span count, error count, token total, computed cost and latency.
  • A summary strip above the list for the sessions that match your filters: count, error rate, latency percentiles, tokens and cost. That gives you the usage of a branch at a glance. Costs are list-price estimates in US dollars, not billed amounts.
  • A way to go from a branch to the exact step: failed sessions carry an error status, and a failed tool call is marked in the waterfall.
  • A link you can send. Share on the trace list creates a read-only, frozen view of your filters with summary tiles and trace metadata only, never span content. It expires after 24 hours, 7 days or 30 days.
  • With plugin 0.6.2 or later, each session is also recorded under the email of the developer who signed in. Track Claude Code usage and cost across a team shows how to read branch work per developer.

When something else fits

  • To compare cost across developers rather than branches, use the Users page, described in the team usage guide, and sort by Cost.
  • To follow branch names that share a prefix, add them to one is any of filter, because attribute filters have no partial match.
  • To see everything inside one session, skip the branch filter and open that session’s waterfall or the Spans tab.

Still stuck? Get help

Last updated on
Quickstart