Sessions
A session is one run of a coding agent, captured by the hook. Open Sessions in a dev-mode workspace to see them live — new sessions and their cost stream in over SSE as agents work.
What a session records
Section titled “What a session records”| Field | Source |
|---|---|
| Developer | your MNEMA_DEVELOPER_ID (defaults to user@host) |
| Agent | the client — currently claude_code |
| Status | active → completed (or failed when a blocker is logged) |
| Model | read from the session transcript at the end |
| Tokens & cost | input / output / cache tokens summed from the transcript, priced per model |
| Duration | start to end, stamped server-side |
| Git | branch and HEAD commit at start and end |
| Files touched | count of files the session edited |
| Tool calls | each tool the agent ran, with the file path for file tools |
Token cost is 0 until a session ends, because usage is summed from the transcript at
SessionEnd. A session that is still active shows its tool activity but not its final cost yet.
Attribution
Section titled “Attribution”- To a developer — every session carries the developer id from the machine that ran it, so the Team leaderboard can total spend per person.
- To a task — when an agent claims a board task (via the
claim_taskMCP tool), the session is linked to it, and a merged PR on the same branch is attributed back to that task.
Where the data comes from
Section titled “Where the data comes from”Sessions are pushed by the local hook, never polled. If you see $0 cost or empty git fields,
the hook is not installed or not sending — reinstall it from
Connect your coding agent. Nothing is captured for an agent you have not
connected a hook for.