Four divergent concepts for a native, low-friction backlog shared by a developer and their coding agents, followed by the recommended direction. Each sheet is an annotated set of product-fidelity frames: desktop, mobile, capture, retrieval, execution, and lifecycle states.
CONCEPT A Task inbox — a global, email-like triage surface: sweep, snooze, done. CONCEPT B Project ledger — a dense, stable per-project list with a detail panel. CONCEPT C Conversation-first — tasks live as chips in threads; browsing is an overlay, not a place. CONCEPT D Agent workbench — intent above execution: backlog → task → attempts, mission-control style. RECOMMENDED The Project Ledger # — B's chassis, C's capture, A's attention model, plus the end-to-end #245 sequence.