aq-commslisted

# aq comms — Messaging and asking humans The daemon's message bus carries three kinds of frames: agent → user ("I need X"), user → agent (chat + directives), and agent → agent (coordination). All flow through `aq message`. ## Read ```bash aq message inbox # your session's pending messages aq message inbox --json # structured (--json is # global: any position works) aq message list --project <pid> # everything sent in a project aq message list --thread-id dashboard:<pid> # filter to a chat thread ``` Every session that starts with a bearer token gets an automatic inbox. Nothing renders it at every prompt boundary: the `UserPromptSubmit` hook that ran `aq inbox --inject` was removed on 2026-08-27. Pending messages reach you when `aq prime` runs (start, resume, post-compact) and through the cascade's nudge, which types them into the session once it goes idle. `aq inbox --inject` is still a supported command, so run it yourself when you want the queue rendered inline mid-task; `aq message inbox` is the same queue as data. ## Send Supervisors should use the native live-worker command for operational guidance. It resolves a task, agent, or session to its current live worker, queues the message durably, mirrors it in the task comments, and reports its delivery status: ```bash aq agent message <task-id|agent-id|session-id> "Stop the full suite; run the focused file.