June 8, 2026 · 4 min read
Why Cue: one quiet place for everything that needs you
A normal working day asks for your attention from a dozen directions at once. Email has a signup. Stripe has a payment. Vercel finished a deploy and Sentry caught an error while it did. A teammate pinged you in Slack. And somewhere in another window, an AI agent you set running an hour ago has quietly stopped — it hit a decision it is not allowed to make alone, and it is waiting for you to notice.
None of these tools is wrong to tell you. The problem is that they all tell you the same way, with the same weight, in the same insistent tone. A failed payment and a successful deploy arrive looking identical. The one thing that genuinely needs a human — the agent that stopped — looks no more urgent than the forty things that do not. So you end up watching everything, which is the same as watching nothing.
Attention is a budget, not a default
Cue starts from a simple stance: your attention is the scarce resource, and a good tool should spend it carefully. Most of what happens in your stack is worth recording but not worth interrupting you for. A few things genuinely need a decision right now. The job is to tell those two apart and to look honestly different doing it.
That is why Cue is dark and nearly monochrome — the Quiet Console. Notifications land as calm rows you can clear or snooze whenever you get to them. There is exactly one accent color, amber, and it is reserved for a single meaning: this needs your decision. Nothing decorative is ever amber. Nothing you have already cleared is amber. If something is glowing, it is waiting on you and nothing else. We call that the amber law, and we hold to it everywhere.
Two jobs, one surface
Cue does two things that turn out to be the same thing. It is a notification hub: point a connector — GitHub, Stripe, Vercel, Sentry, Linear, a plain webhook — at a stream, and it gathers what matters into one inbox. And it is a human-in-the-loop surface for AI agents: connect an agent over MCP, and when it needs a human it raises a request and blocks until you answer.
Two words we keep deliberately distinct. A stream is an inbox lane you own. A connector is the thing that feeds cues into it. One collects, one delivers; blurring them is how inboxes turn back into noise.
The agent that waits
The part we are most proud of is the quietest. When an agent reaches a decision it should not make alone — deleting branches, sending an invoice, touching production — it does not guess and it does not silently stall in a terminal you forgot to watch. It raises an agent request in Cue and blocks. You see it as the one amber card in an otherwise calm inbox, with the context and exactly what would be affected. You approve or decline once, and the agent picks up where it left off.
No more keeping a dozen sessions open to catch the one that stopped. The agents wait in a place built for waiting, and you decide on your own schedule.
Where we are
The build is live as of today. If any of this sounds like your day, the fastest way to understand Cue is to see it. We will keep these notes short and infrequent — fitting, for a tool whose whole point is to leave you alone until it shouldn't.
Read what shipped on the changelog.