Skip to content

feat(cli): the board reads what actually ran #651

Closed as not planned
Closed as not planned

Description

@blafourcade

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.

Out of scope

  • Any figure requiring the telemetry sink.
  • Aggregation across projects.

Relations

Field Value
depends_on #620

Activity

  1. added this to the milestone on Aug 14, 2026
  2. removed this from the milestone on Sep 3, 2026
  3. blafourcade commented on Sep 12, 2026

    @blafourcade
    ContributorAuthor

    This is not ready to be scheduled as a feature.

    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.

  4. changed the issue type fromtoon Sep 12, 2026
  5. moved this from Ideation to Todo in AIDD Roadmapon Sep 15, 2026
  6. blafourcade commented on Oct 15, 2026

    @blafourcade
    ContributorAuthor

    Superseded by #993: what ran is read from Claude Code's own session files, through aidd telemetry report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Priority

    Low

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions