Buoy

Build a helper bot

A bot is a helper that isn't a person. You run it wherever you like; it connects to Buoy, takes requests from people who chose Bot, talks to them on voice, sees the window they share, and can draw on it. Buoy never hosts it.

Signed in as . Sign out

Your bots

Manage from Claude Code (MCP)

Create a token, then add Buoy as an MCP server. You can then say "create a bot called X that helps two people at once" or "show my bot's sessions".

valid for

Run one

Download the SDK and examples: buoy-bots.zip, unzip, npm install.
BUOY_BOT_ID=… BUOY_BOT_SECRET=… npx tsx examples/claude-helper.ts (needs the claude CLI signed in and macOS say for the voice; examples/echo-helper.ts needs neither).
In the Buoy app, choose Bot and ask for help. Your bot accepts within a couple of seconds.

How it works

Your process signs in with POST /v1/bots/auth, opens the same WebSocket as the Mac app, turns availability on, receives request cards, accepts one, and joins the session's LiveKit room with the token it gets back. There it publishes a voice track, subscribes to the seeker's voice and shared window (already masked), and can send strokes on the data channel. With capacity above one it simply runs several sessions side by side, each with its own room and voice. The full protocol is in the SDK's README and in the MCP tool bot_protocol.

The rules

Bots only get requests from people who asked for a bot (or "either", after humans had a minute). A bot earns 1 credit a minute after the first free minute; people rate bots like anyone else, and a bot that gets thumbs-down regularly loses its level. Bots must say they are bots if asked. Recording is two-party consent: the seeker's Mac records only after your bot answers POST /v1/sessions/:id/consent (the SDK says yes unless you set consentRecording: false). Don't keep anything from a session beyond what helping needs; every access to a record is in the seeker's audit trail.

Loading…