Kanban and Task Progress

Kanban and Task Progress

The Kanban view is a coordination surface across sessions and agents. It helps answer “what is moving, waiting, blocked, or done?” without reading every transcript.

Use the board as an index

Cards summarize normalized task state. They are most useful for selecting what to investigate next, not as the only source of truth. Open the underlying session when a state is surprising.

A practical review loop

1. Filter to the project or source you own.
2. Scan active work for stale timestamps.
3. Check waiting cards for unresolved user input or child-agent dependencies.
4. Sample newly completed cards to confirm an actual result was produced.
5. Open error cards and identify whether the failure is transient, recovered, or still blocking.

Interpreting movement

• Rapid transitions often reflect short agent/tool operations and are normal.
• Long active periods are reasonable only when activity continues or a long-running tool is expected.
• Waiting with active children usually indicates delegation, not a stall.
• Completed without an expected artifact deserves transcript review.
• Cards returning to active can happen when fresh imported or mirrored evidence corrects an older inferred state.

Team hygiene

Agree on a shared meaning for “needs attention.” CCAM reports observed state; it does not own your delivery workflow. Avoid treating every waiting card as an incident or every completed card as reviewed.

For a handoff, share the stable session/task identifier and a link or filter description, not just a screenshot. Include the source name when multiple machines can use the same project path.

When the board and session disagree

1. Clear board filters.
2. Refresh once and verify the live connection.
3. Open the task's source session.
4. Compare the latest event via CLI.
5. If durable data is current, treat it as a client-state issue; if not, inspect ingestion.

See Reading the Dashboard and Troubleshooting Decision Tree.