yaaclisted

# Talking to the user's other sessions The tools carry their own instructions: each one says what it does and what calling it costs. This skill is the part they cannot carry — when reaching for the radio is the right move, and what to do with what comes back. ## When it is worth using The occasions all look like *one session knows something another one needs*: - **Parallel worktrees.** A rename, a migration, a moved config — anything the other session is about to build on a stale version of. Tell them before they do, not after. - **A question this session cannot answer.** Another session has the file open, ran the test, or made the decision an hour ago. Asking costs one message; rediscovering it costs a rebuild of context. - **Long jobs.** A session watching a slow suite can report when it goes green. - **The user is the one relaying.** If they are copying text between two terminals, that is the radio's job. And when it is not: YAAC moves *text*, never files or history. For handing over a whole conversation, resuming a session is the right tool. For work this session should simply do itself, do it. ## Why nothing arrives on its own The tools say to call `check_inbox`; the reason is worth having. MCP has no way for a server to push into a session that is sitting idle, so an unread message is not a notification waiting to be dismissed — it is a message nobody knows you have not read. Reading takes the messages rather than showing them, so collect them when you are in