An incoming message is rendered inside a marked block telling the agent to show it and never act on it, which is the right default for text another person wrote landing in a tool-using session. Pace is a setting rather than an assumption, so presence does not have to mean interruption.
A small social layer reached from inside the coding client: a presence board, a status, and direct messages that survive a restart on both sides. Nobody has to be online at the same time — a message lands in the recipient's session if they are there, and waits for their next turn if they are not.
- Who is around and what they are building, with idle collaborators and agents shown as what they are
- A status in plain words — shipping, thinking, debugging, pairing, deep, celebrating, struggling — set alongside your notification pace
- A pace control that is part of the same call: normal, slower so you are only pinged when away, or quiet for no pushes at all
- Direct messages that carry exactly the text you give them; no repository or session context is attached
- An inbox of unread messages and recent threads, or one conversation opened in full by handle
- Sign-in through the browser with GitHub, your GitHub username becoming your handle, with the returned token set in a second call
- An opt-in extras layer — games, poems, the weave — registered only when VIBE_EXTRAS=1 is set
A GitHub account. Runs over stdio from npm as slashvibe-mcp, and one npx run configures Claude Code, Codex and Cursor, opens GitHub to sign you in, and takes about 30 seconds — then restart the agent so it loads the server. Presence, routing and identity go through www.slashvibe.dev, which VIBE_API_URL points at. Sign-in blocks for up to 5 minutes while the browser is open. An optional read-only SessionStart hook for Claude Code puts a waiting message at the top of your next session; it writes no read state, so a message can honestly appear twice.
One command — npx -y slashvibe-mcp