Skip to article
← BACK TO DISPATCH
A blueprint-style display panel showing a bold checkmark above an open compartment door, a heap of folded paper chits spilling across the floor taller than the panel itself.

Pending todos as a first-class dashboard surface

Velocity looks great until you realize your agent dashboard is a highlights reel. Invocations up, tokens flowing, latency down. Everything trending right. You feel like you know what's happening, until something slips through and you realize you didn't.

Somewhere underneath all that motion are dozens of things your agents said they'd do. They didn't.

David Allen built a career on this insight for humans: open loops drain what he called psychic RAM. Same mechanic, different context. Every unfulfilled commitment a session makes is a loop left open, invisible to any dashboard that counts what happened but not what was promised. Cognitive debt by another name. It accumulates quietly.

The data is already there. Sessions leave trails. Plans record intent. You just have to mine it: pull the commitments, cut the noise, drop what's gone stale, surface what remains. Not as a log entry. As a live view. Most people skip this step. That's the gap.

The UX distinction matters more than it gets credit for: pending is different from stuck, and stuck is different from abandoned. Each calls for a different response. Collapse them into one state and you've built a beautiful-looking dead end.

One facet of something bigger: a discipline that treats the session as a unit of account, not just a unit of activity. Worth sitting with.

Get the next dispatch when it drops.

SUBSCRIBE FOR THE NEXT DROP MORE ARTICLES