---
id: agent-delivery/generalise-it-deliver-a-turn-to-a-named
title: "Generalise it: deliver a turn to a named session, from anywhere in the backend"
theme: agent-delivery
status: open
created: 2026-08-21
date_source: stated
order: 1
---

**Generalise it: deliver a turn to a named session, from anywhere in the backend.** Wanted
2026-08-21 — "ideal" is the owner's word for it. Today the only server-side caller is the nudger,
and delivery is welded to its schedule: a row in `nudges`, one per (user, session), a fixed
message, a tick. What the dispatcher, the file watchers and Command HQ all want instead is a plain
verb — *here is some text, deliver it to session X* — with the schedule, if any, belonging to the
caller.

Two things already established and worth not re-deriving. The nudger's `checkSafe` holds three
refusals — not live, live but generating, another live session in the same directory — and the
comments above it carry why each one is there. And "not live" is the case that differs by caller:
the nudger refuses (nudging a dead session would CREATE an agent, which is not what nudge means),
while a dispatcher handing over five todos does want it created.