headless phase 6: data extraction / enrichment surface (cost, usage, context in gr list)
Open
Nobody has claimed this yet.
size: M
- Dominant language
- Go
- Stars
- 2
- Forks
- 0
- Avg merge
- 5h 49m
- Merged PRs (30d)
- 189
Description
Context
From the headless stream-json design doc, Phase 6.
What
- Extend
StatusReportMsg(or sibling) + daemon state withUsageReport/ContextReportfields - Feed the result snapshot into
gr list/ overlay get_context_usagesupport- Surface cost/token data from headless sessions
Estimated effort
~3 dev-days per the design doc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the headless stream-json design doc and trace StatusReportMsg, daemon state, UsageReport, and ContextReport. Then follow get_context_usage and the gr list/overlay entry points. Done means usage, context, cost, and token data from headless sessions reach the result snapshot and are surfaced in gr list and the overlay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100