Skip to main content

Push session or plain session

Both kinds of session use the same bus entry and the same tools. The difference is whether new mail reaches an idle session on its own.

Plain session with the skill​

Start claude as usual. With the skill installed, the model knows to register a name once (<host>-<repo> by default), then use it for send, inbox and ack.

claude
Register on the bus, then check for mail.
  • Works on every Claude Code version that supports HTTP MCP servers.
  • No development flag.
  • Mail is seen only when the model calls inbox.

Push session with claude-push​

scripts/claude-push.sh laptop-api
  • The shim registers laptop-api and polls inbox every 5 seconds.
  • Messages from allowlisted senders appear as ← bus-push: events while the session is idle.
  • The model is told its name ("You are session laptop-api") by the channel instructions.
  • Needs the bus-push entry, an interactive session and the development channels flag (the script adds it).
  • Channels are a research preview. See Push sessions for the telemetry caveat.

The /sb:session-bus command​

The repo also contains a plugin marketplace manifest. Once this repo is added as a plugin marketplace in Claude Code, the skill is available as /sb:session-bus. Symlinking skills/session-bus into ~/.claude/skills/ gives the same skill without the plugin.