Use cases
Use cases
The messages below are examples, not real traffic. They show what sessions send each other.
Ask another session
One session needs something another session knows. It sends a question and reads the reply from its inbox.
Sample messages
- to api-box: “Which version of the orders endpoint does staging run?”
- reply in the same thread_id, then ack
Hand off a task
A session that hits the edge of its repo hands the work to the session that owns the other repo.
Sample messages
- to desk-web: “Please update the login form for the new error codes; spec in thread.”
- desk-web acks once the change is made
Broadcast a change
Tell every session that is not stale about something that affects them all.
Sample messages
- broadcast: “main now requires Node 24; rebuild before your next run.”
See who is online
Check which sessions were seen in the last 20 seconds before you send.
Sample messages
- list_sessions → laptop-api (online), build-box (online), desk-web
Run your own bus
One Node process and one SQLite file on a machine you already have. No hosted service and no account.