Fix/tui aggregated token cost #751

riturajFi · 2025-11-08T12:32:02Z

Multi-session token tracking in runtime + sidebar

Overview

fixes #504

Expands runtime token-usage events to include session IDs and both self vs. inclusive snapshots, allowing downstream consumers to correlate root and child sessions.

The runtime now:

Aggregates self/child token totals.
Emits refreshed snapshots after compaction and task transfers.

The sidebar is modernized to:

Present “Total usage” with comma separators.
Add a sortable session breakdown.
Highlight the active agent’s self-spend.

Implementation Highlights

pkg/runtime/event.go, pkg/session/session.go
Introduce richer TokenUsageEvent payloads and per-session self fields, distinguishing the emitting agent’s contribution from inherited child totals.
pkg/runtime/runtime.go
Calculates self vs. inclusive snapshots, merges child session usage, logs each provider chunk to token_usage_chunks.log, and re-emits TokenUsage events whenever compaction or transfers change totals.
pkg/tui/components/sidebar/sidebar.go
Replaces the single Usage pointer with a usageState map keyed by session ID. Formats totals using humanize.Comma, and renders a “SESSION BREAKDOWN” section showing root-exclusive usage plus every child session (sorted, with the active session highlighted).
pkg/tui/page/chat/chat.go
Passes the full TokenUsageEvent to the sidebar.
pkg/runtime/runtime_test.go
Adds snapshot helpers so expectations include the richer event payloads.

Testing

task test

Screenshots / Recordings

riturajFi · 2025-11-09T15:39:10Z

@krissetto — kindly take a look at this PR when you have a moment. I’d really appreciate your feedback!

I closed the previous PR since the approach there turned out to be overly complex and didn’t rebase cleanly with the updated main branch.

In this version, I’ve simplified the implementation by introducing dedicated fields for each session to track separate self and child token counts, which are then aggregated for display.

I’ve tested it with:

A root agent having multiple subagents.

Subagents that themselves have nested subagents.

There’s also a temporary logging system included to help with verification — I’ll remove it once the changes are approved for merge.

rumpl · 2025-11-09T16:29:18Z

For logging you can simply use slog.Debug, this will write the logs to ~/.cagent/cagent.debug.log`

rumpl · 2025-11-09T16:30:00Z

pkg/tui/page/chat/chat.go

 		return p, cmd
 	case *runtime.TokenUsageEvent:
-		p.sidebar.SetTokenUsage(msg.Usage)
+		p.sidebar.SetTokenUsage(msg) // forward full event so sidebar can track per-session usage


Please remove this log

riturajFi · 2025-11-10T06:44:32Z

For logging you can simply use slog.Debug, this will write the logs to ~/.cagent/cagent.debug.log`

Hi @rumpl @krissetto , removed the logging. Can you please verify the solution and if some changes need to be done?

krissetto

Thanks for working on this @riturajFi! I left a bunch of little comments, mostly nitpicks though.

One thing, i think we could streamline the sidebar UI when no subagents are configured in a team.

Also, have a look here for best practices when it comes to documenting go code, for the most part we follow those recommendations when leaving comments etc

krissetto · 2025-11-10T14:52:00Z

pkg/tui/components/sidebar/sidebar.go

+	}
+	builder.WriteString(fmt.Sprintf("\n  Tokens: %s | Cost: $%.2f\n", formatTokenCount(totalTokens), totals.Cost)) // display totals line
+	builder.WriteString("--------------------------------\n")                                                      // visual separator
+	builder.WriteString(styles.SubtleStyle.Render("SESSION BREAKDOWN"))                                            // heading for per-session details


nit: Let's use Agent breakdown (not all caps is a bit nicer imho) instead as its more representative. each time an agent delegates to a subagent, a new session is created. This can happen more than once

krissetto · 2025-11-10T15:07:38Z

pkg/tui/components/sidebar/sidebar.go

+	// var usagePercent float64
+	// if totals.ContextLimit > 0 {
+	// 	usagePercent = (float64(totals.ContextLength) / float64(totals.ContextLimit)) * 100
+	// }
+	// percentageText := styles.MutedStyle.Render(fmt.Sprintf("%.0f%%", usagePercent))


nit: this commented out code can be removed when dealing with multiple agents, but if there's only one it might be good to keep the percentage displayed

on it @krissetto

pkg/tui/components/sidebar/sidebar.go

riturajFi · 2025-11-10T19:00:40Z

@krissetto I fixed the issues raised by you. Kindly review

riturajFi · 2025-11-13T20:26:47Z

Hi @rumpl @krissetto @dgageot Would love your review of this PR! Exited to move to the next issue in the core codebase

krissetto · 2025-11-14T12:59:02Z

Hey @riturajFi i'm testing this out again. Could you please fix the linter errors so the CI is green? There is some unused code and some formatting issues. Also needs a rebase, sorry for that.

riturajFi · 2025-11-14T13:00:48Z

Hi @krissetto i shall fix everything in the next 2 hours or so. Currently dont have access to my computer 🙃🙃

krissetto · 2025-11-14T13:04:54Z

@riturajFi not a problem, i'll leave some comments as i test things out in the meantime. Also, could you squash the commits down when you get a chance?

krissetto · 2025-11-14T19:02:07Z

@riturajFi First of all, I love the enthusiasm you have in wanting to contribute to this project ❤️

To try and guide you in the right direction to get this feature merged, i made a quick example of what i was thinking about that you can find here: https://github.com/krissetto/cagent/tree/tui-usage

It would be ideal if we could get this feature in with minimal changes to the actual runtime, focusing instead on the TUI side of things. Smaller changes are easier to review for us and will be faster to merge, then if there are followup issues we can deal with those separately 😄

Please have a look at the ideas in my branch (compare them directly to main), give it a try locally, and feel free to steal the code and bring it in here or open a separate PR if it makes things easier for you

Let me know what you think!

riturajFi · 2025-11-14T19:49:43Z

Oh...i thought you guys wanted to solve it in the backend too as any future consumer would directly have token count access.😅 if just handling things in the frontend is fine then i shall do it right away 🫡

krissetto · 2025-11-19T12:50:04Z

@riturajFi go for it! frontend only is more than enough right now, a consumer can always access the data from the sessions

riturajFi · 2025-11-19T14:41:56Z

Thanks @krissetto for the greenlight. I shall make the changes in some hours. Kindly find time to take a look.

riturajFi · 2025-11-21T19:05:50Z

Hi @krissetto changed the entire logic to the frontend. The changes -

basically went through your solution and implemented it here. Thanks for your help!

riturajFi requested a review from a team as a code owner November 8, 2025 12:32

riturajFi marked this pull request as draft November 8, 2025 12:32

riturajFi force-pushed the fix/tui_aggregated_token_cost branch 2 times, most recently from c3a0214 to a15dc5c Compare November 9, 2025 15:28

riturajFi marked this pull request as ready for review November 9, 2025 15:35

rumpl reviewed Nov 9, 2025

View reviewed changes

riturajFi requested a review from rumpl November 10, 2025 06:43

riturajFi force-pushed the fix/tui_aggregated_token_cost branch from 0378171 to 1d5ad81 Compare November 10, 2025 13:19

krissetto reviewed Nov 10, 2025

View reviewed changes

riturajFi requested a review from krissetto November 10, 2025 18:04

riturajFi force-pushed the fix/tui_aggregated_token_cost branch from d21981f to 68c2716 Compare November 10, 2025 18:59

riturajFi force-pushed the fix/tui_aggregated_token_cost branch 2 times, most recently from acf035f to 759f561 Compare November 21, 2025 18:26

riturajFi added 3 commits November 22, 2025 00:38

frontend fix

5c22f4e

minor fix

bcbdf75

commentd

1645e6c

riturajFi force-pushed the fix/tui_aggregated_token_cost branch from 759f561 to 1645e6c Compare November 21, 2025 19:08

riturajFi added 2 commits November 22, 2025 04:49

minor

4350013

temp

3e7534f

Fix/tui aggregated token cost #751

Are you sure you want to change the base?

Fix/tui aggregated token cost #751

Conversation

riturajFi commented Nov 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

Implementation Highlights

Testing

Screenshots / Recordings

Uh oh!

riturajFi commented Nov 9, 2025

Uh oh!

rumpl commented Nov 9, 2025

Uh oh!

rumpl Nov 9, 2025

Choose a reason for hiding this comment

Uh oh!

riturajFi commented Nov 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

krissetto left a comment

Choose a reason for hiding this comment

Uh oh!

krissetto Nov 10, 2025

Choose a reason for hiding this comment

Uh oh!

krissetto Nov 10, 2025

Choose a reason for hiding this comment

Uh oh!

riturajFi Nov 10, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

riturajFi commented Nov 10, 2025

Uh oh!

riturajFi commented Nov 13, 2025

Uh oh!

krissetto commented Nov 14, 2025

Uh oh!

riturajFi commented Nov 14, 2025

Uh oh!

krissetto commented Nov 14, 2025

Uh oh!

krissetto commented Nov 14, 2025

Uh oh!

riturajFi commented Nov 14, 2025

Uh oh!

krissetto commented Nov 19, 2025

Uh oh!

riturajFi commented Nov 19, 2025

Uh oh!

riturajFi commented Nov 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

riturajFi commented Nov 8, 2025 •

edited

Loading

riturajFi commented Nov 10, 2025 •

edited

Loading

riturajFi commented Nov 21, 2025 •

edited

Loading