Never lose a follow-up: durable queues + interrupts for Claude Code, Codex, and OpenCode sessions

The most common way I accidentally derail a session is not by sending the wrong instruction.

It’s by sending the right instruction at the wrong time.

A session is busy (or offline / resuming), I fire off a follow-up from my phone, and then one of three things happens:

the message disappears into the void
it lands later than I expected (after the session already made a bunch of decisions)
I don’t trust it, so I write a second “shadow plan” in Notes… and now I’ve created a coordination problem with myself

What I want is boring:

I want to queue follow-ups safely, edit them if I change my mind, and send-now only when I truly mean “interrupt.”

TL;DR

Decide what you need:
- Queue until ready (ordered, editable follow-ups), or
- Interrupt & send now (stop the current turn)
If you don’t have a durable queue, your safest fallback is: write the follow-up somewhere else and send it only when you’re sure the session is ready.
Happier is one option that solves this directly with a pending queue (queue/edit/reorder/remove/send-now) that’s stored with the session.

The problem (in plain language)

When you’re not at your laptop, follow-ups are how you keep work moving.

But most tools treat “send a message” as if the receiver is always ready.

In real life the receiver is often:

mid-turn
disconnected
switching between local and remote control
resuming after being inactive

So you need a workflow that is explicit about time.

What I tried first (and where I bounced off)

Just send it and hope: surprisingly fragile.
Write it in Notes/Slack and remember to send later: works, but now I’m managing a second queue.
SSH into the machine and intervene directly: powerful, but it turns into real work on a phone.

If you want the industrial version of this problem, people solve it with durable workflow engines (Temporal) or agent orchestration frameworks with persistent threads and interrupts (LangGraph).

Happier is the “practical UX” version I use day-to-day.

If you’re new to Happier (what it is, and where to get it)

If you haven’t seen Happier before: it’s an open-source companion app (mobile/web/desktop) for sessions like Claude Code, Codex, and OpenCode.

The workflow is: sessions run on a machine you trust, and Happier is where you send follow-ups from your phone — with a real queue when the session isn’t ready.

Get set up: