See what every dev on your team
is doing in Claude Code.
Your 5-25 developer team runs Claude Code all day. You have zero visibility. Who’s burning tokens? Who’s got a stuck agent? Which repos are generating vs debugging? Septim Muster reads every dev’s local session files (with their consent) and gives you one dashboard.
Launch list open. $0 now. Founding price locks the moment we ship (June 2026).
Team-wide Claude Code usage is a black box.
Your dev team has adopted Claude Code. Some use it daily. Some barely. One engineer had an overnight incident and burned $800 — you didn’t know until the month-end bill. Another ships twice as fast as everyone else and no one on the team knows what skills they’re using. Senior engineers spend 20 minutes asking in Slack who knows "the thing for refactoring" — the answer is their own teammate three desks over.
Every other platform your team uses has admin visibility: Slack admin, GitHub admin, JIRA admin. Claude Code runs on each dev’s local machine with zero team-level view. Muster is the opt-in, team-consented read-layer on top of everyone’s local JSONL session files.
One dashboard. Every developer.
Live working-on
Who’s in Claude Code right now. What product / repo / task. How long they’ve been at it.
Token + cost per dev
Daily / weekly / monthly spend per seat. Spike alerts. Anomaly detection at the agent level.
Runaway agent alert
If any dev’s session crosses a budget cap, Muster pings the admin inside 60 seconds with a one-click “revoke session” action. Admin stays in the loop — no silent kill. Automatic halt is on the v2 roadmap.
Skill usage heatmap
Which Claude Code skills does your team actually run. Which are unused. Which one dev uses that nobody else knows about.
Repo × dev heatmap
Which projects each dev is working on. Where concentration is highest. Where there’s a bus factor of one.
Privacy + consent
Each dev opts in per seat. They see what you see. The entire log lives on your own machine or a LAN server you control.