Not tracking sub agents (Fedora 44)

[MorsCordis]

It doesn't appear that Codeburn is tracking tool calls performed by subagents with Claude CLI.

It also seems to treat each Gemini session as a single call, not tracking tool calls/usage particularly well. Only coding and exploration are showing.

[vmvarela]

The same gap exists for the OpenCode provider. OpenCode stores sessions in SQLite with a parent–child hierarchy: a root session can have child and grandchild sessions, each with their own Part rows. The current parser only queries direct messages on root sessions, so any token usage or tool calls that happen inside a child session are silently dropped.

The root cause is in how discoverSessions maps session sources and how the message query is structured — it doesn't traverse the session tree. A WITH RECURSIVE CTE on the Session table would capture the full subtree and attribute everything back to the root session correctly.

Planning to look into this for OpenCode specifically — would this be a welcome addition alongside #340

[ozymandiashh]

This is now split across two ready PRs:

• Track agent calls across providers #340 covers the original cross-provider tracking gap for Gemini/Claude/Codex-style agent activity. Gemini now emits one CodeBurn provider call per assistant message with usage instead of one aggregate call per session, Claude discovery includes direct subagents/*.jsonl files, and Codex agent tool normalization is covered by regression tests.
• Track OpenCode child sessions under root sessions #343 covers the OpenCode child-session case mentioned in the thread. It keeps root-only discovery to avoid double counting, then parses the full unarchived child/grandchild session subtree back under the root session.

Both PRs are currently clean/mergeable with GitHub checks passing.

Important limitation: I did not validate either PR against the original Fedora reporter environment or real private local subagent history. The validation uses synthetic fixtures and parser regression tests, so no local project names, prompts, paths, session IDs, usage values, or private product details are included.