You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer returning to a project I want the board to show what actually ran, not only what was declared So that I recover the thread without opening folders or paying an agent to summarise state that is already written down
Acceptance
A feature shows its steps in the order they ran, with the duration of each.
A step that ran several times appears several times, not merged.
The originating ticket is shown, resolved through the identity file's upward link.
Work with no task attachment is reachable, not hidden.
The board keeps working on a project that has no run journal at all, degrading to what it shows today.
No token or cost figure appears: they are not on disk, and the board reads only the repository.
The board still writes nothing and launches nothing.
What it reads, and what it must not
It reads the run journal and the task identity file, next to the frontmatter it already reads. It must not read telemetry: the board is offline, unauthenticated, and local by design. Cost belongs to the skill that can reach the sink, and to the dashboard.
Its own product brief already names these two as missing — "journal des exécutions" and "tokens par phase" — and answers the second: the board is not where tokens belong.
The current kanban package is deliberately unwired: the architecture rejects an embedded board. aidd telemetry report --axis backlog now covers attribution in a separate, cost-oriented CLI surface, but it is not this feature: it aggregates records, does not provide a chronological activity view, and reads telemetry.
Keep the need, but use this issue as a spike to choose an active UI owner and define the data boundary: local journal only, including missing-journal behavior, or telemetry-backed reporting. No implementation should start until that boundary is explicit.
Activity
blafourcade commentedon Sep 12, 2026
This is not ready to be scheduled as a feature.
The current
kanbanpackage is deliberately unwired: the architecture rejects an embedded board.aidd telemetry report --axis backlognow covers attribution in a separate, cost-oriented CLI surface, but it is not this feature: it aggregates records, does not provide a chronological activity view, and reads telemetry.Keep the need, but use this issue as a spike to choose an active UI owner and define the data boundary: local journal only, including missing-journal behavior, or telemetry-backed reporting. No implementation should start until that boundary is explicit.
blafourcade commentedon Oct 15, 2026
Superseded by #993: what ran is read from Claude Code's own session files, through
aidd telemetry report.