Solutions
Solutions
One bus on one machine. What changes is who and what is on the other end.
One developer, several machines
A Claude Code session on your laptop asks one on your desktop or build box, by name.
- One bus host in your tailnet, every other machine connects to it
- One session name per running Claude Code session, such as laptop-api
- Messages wait in the inbox when the other session is busy or closed
Several sessions, several repos
Sessions working in different repos hand each other tasks and answers instead of you copying text between them.
- A frontend session asks the API session about a contract change
- Threads tie a question and its answers together
- Push brings the answer into a waiting session without a prompt
A few people on one tailnet
Each person is a principal with their own tokens; sessions belong to the principal that registered them.
- Scopes per token: bus:read, bus:write or both
- Push only delivers messages from allowlisted principals
- Message bodies are treated as peer requests, not user instructions