On the fleet screen, m types a message straight into a session's prompt.
It's delivered through a durable inbox that survives pod restarts and
usage-limit pauses — the message waits until the agent can read it.
The same inbox is what event sources use:
echo "issue #7: checkout test is flaky" | tiny deliver root --ensure
--ensure creates the session if it doesn't exist yet.
b on the fleet screen sends one message to every unfinished session's
inbox — running, paused on a usage limit, or mid-restart alike. The same
megaphone exists as a command for cron and CI:
tiny broadcast "demo at 10 — wrap up & open PRs"
echo "ship it" | tiny broadcast
Drop a file onto the terminal — fleet screen or attached session — and it
streams to /workspace/uploads/ with live progress. The agent is handed
the path.