From a1fe5356cf4e08639c7eb376cbe470f36b0cfa50 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Mar 2026 10:41:49 +0000 Subject: [PATCH] story-kit: create 301_story_dedicated_token_usage_page_in_web_ui --- ...ry_dedicated_token_usage_page_in_web_ui.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .story_kit/work/1_backlog/301_story_dedicated_token_usage_page_in_web_ui.md diff --git a/.story_kit/work/1_backlog/301_story_dedicated_token_usage_page_in_web_ui.md b/.story_kit/work/1_backlog/301_story_dedicated_token_usage_page_in_web_ui.md new file mode 100644 index 0000000..cd9743a --- /dev/null +++ b/.story_kit/work/1_backlog/301_story_dedicated_token_usage_page_in_web_ui.md @@ -0,0 +1,21 @@ +--- +name: "Dedicated token usage page in web UI" +--- + +# Story 301: Dedicated token usage page in web UI + +## User Story + +As a project owner, I want a dedicated token usage page in the web UI that shows per-story and per-agent cost breakdowns with totals, so that I can analyse where tokens are being spent and identify optimisation opportunities. + +## Acceptance Criteria + +- [ ] New page/panel accessible from the main navigation +- [ ] Shows a table of all recorded agent sessions with story, agent name, model, token counts, and cost +- [ ] Sortable by cost, story, agent, or date +- [ ] Shows summary totals: total cost, cost by agent type (coder vs QA vs mergemaster), cost by model (opus vs sonnet) +- [ ] Data loads from the token_usage.jsonl log via API endpoint + +## Out of Scope + +- TBD