Evolve token accounting
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 152
- Forks
- 16
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 536
Description
Goal
Evolve Mecatl token accounting from raw, opaque token totals into configurable cost-aware budgeting and understandable Mecatui usage reporting.
Scope
This parent tracks the coordinated work:
- Configure effective per-run and team token ceilings for embedded mecatui (#686).
- Add fixed-point, configurable weighted-cost accounting with correct cache-read/cache-write partitioning (#687).
- Display effective limits and budget state in Mecatui (#688).
- Add an interactive
/tokensexplanation and delegated-work breakdown with a non-double-counted grand total (#693).
Sequencing
- Define durable raw usage and weighted-cost semantics, including cache-write treatment and configuration (#687).
- Expose the relevant embedded-server configuration (#686).
- Project effective budget and cost information through the server/UI boundary (#688).
- Build the interactive usage panel and footer discoverability on that authoritative projection (#693).
The raw token facets remain valuable observability. Cost-weighted accounting must be a separately named value until any public compatibility/migration decision is made.
Contributor guide
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 sequencing and the referenced issues, especially #687 for raw usage and weighted-cost semantics, then review #686, #688, and #693 in order. Done means the coordinated work defines durable accounting, exposes effective limits, projects authoritative budget data, and presents a non-double-counted usage breakdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100