Milestones
List view
Issues surfaced by the 0.5.0 fresh-install first-run review (#238–#251): backfill fidelity, subscription-framing polish, the Traces experience, onboarding, and standalone UI fixes. None are release-blockers.
No due date•15/15 issues closedThe open (MIT) runtime proxy substrate in SUGGEST mode — the rails for live cost-optimization on API/usage-billed traffic. Includes the pricing-mode gate (subscription traffic is observe-only pass-through, honoring provider terms), a data-driven policy engine, an audit log + savings meter, a kill switch, and budget_cap as the first policy (no validation dependency). Suggest-mode first (logs what it would do); enforce is gated. Policy validation/certification is tracked separately.
No due date•5/5 issues closedUpgrade Lens from one chart + tiles + tables to a richer cost-visualization surface. Headliner: an analytics pivot explorer (group spend/tokens/sessions by any dimension); differentiator: a recoverable-waste overlay powered by the optimize analyzers. Build path under consideration: explorer-first vs incremental standalone charts.
No due date•12/12 issues closedAgents re-plan the same work constantly. The Plan stage is where most of the LLM spend goes, and across a real workload the plans repeat: same task shape, same tool sequence, different filenames and dates. Reuse is TokenJam's fifth analyzer. It read existing telemetry and quantifies how much of the user's spend is repeated planning, then exports the recurring plan skeletons as reviewable templates
No due date•2/2 issues closedThe local UI today is six tables. It works, but a developer can't look at it and immediately see "where is my money going, and how much could I recover." Lens makes that the front door — and gives the project a brand-able surface to put on the marketing site next to the analyzers.
No due date•14/14 issues closed