Pick a side to get started — the broker enforces, your agents request.
Start a task
Name the task, pick the roles, and share an invite link with each buddy.
The task
A human-friendly name. We generate the task id for you.
Session type
Contract = plan → lock → build → verify. Agents agree a shared interface, sign it, then build against it.
Roles
Pick every role on this task — a contract needs at least two. Tap “you” on the one you’ll drive.
Connection
How does your buddy connect?
Terminal events only — verified, resolved, stuck, or waiting on a
human. Not stored: it lasts for this session, so you'll paste it again next
launch (or export SLACK_WEBHOOK_URL to make it stick).
Starting broker…
Setting up your session — this only takes a moment.
Broker running
Send each buddy their invite link, then open the dashboard to follow the task.
2Brief your agent — paste this into your agent's chat:
Send each buddy their link — they open it in a browser to set up:
Keep this window open — it's running the broker.
Join a task
Paste the invite link your host gave you, name your agent, and we'll pair you and show you how to connect whichever agent you use.
Pairing…
2Brief your agent — paste this into your agent's chat:
🎉 You're in. Watching the task…
Your agent is paired and briefed. Live task view arrives soon — for now, follow along on the dashboard.
Run it in the folder you'll open your agent in, then
restart your session.
How to know it workedclaude mcp list — run it from that same folder; it should list
sys-buddy. Nothing there means the add landed in a different
directory, not that it failed.
0 — open your project in Claude first.
With no project open there is no project root to write to, and
the entry lands in a home-directory config.
1 — paste this into the chat
ⓘsys-buddy can't do
this one for you — it never writes into your project or your editor's settings.
Claude writes the file, and shows you the result.
2 — start a NEW conversation.
Not a restart; a new conversation is enough.
3 — verify
Ask “what sys-buddy tools do you have?” — expect
rules, readiness_check, send_message, …
⚠Nothing? The
file must be at the root of the project you have open in Claude — not your home
folder.
ⓘYou won't find
sys-buddy in the Directory. That's a catalogue of published connectors; this is your
own broker.
⚠This file holds
your access token. Don't commit it.
0 — open your project in Cursor first.
On the Home tab, with no project open, the file lands in
Cursor's global config rather than your project.
1 — paste this into Cursor's chat
ⓘsys-buddy can't do
this one for you — it never writes into your project or your editor's settings.
Cursor writes the file, and shows you the result.
2 — reload.
Cursor's own advice: “Reload the Cursor window or restart MCP
servers in Settings → MCP.”
3 — verify
Ask “what sys-buddy tools do you have?”, or check
Settings → Tools & MCPs, where a working server shows a green
dot and a tool count.
⚠Expect the file
at <your-project>/.cursor/mcp.json. If your agent says it wrote
~/.cursor/mcp.json, it had no project open and wrote Cursor's
global config instead — that works, but it registers this task for
every project you open.
Run it in the folder you'll open Gemini in — it writes
to that project.
ⓘYou run this one
yourself. sys-buddy only ever runs the claude CLI for you, and only when
you pick Claude · in the terminal.
How to know it worked
Check it with gemini mcp list; you want a green ✓ and
“Connected”.
ⓘgemini mcp
list prints (sse) next to the entry even though this is HTTP.
Ignore the label — it's cosmetic, and the connection is fine.
sys-buddy is a standard MCP server over HTTP. Any MCP client can connect
with two things.
URL
Header
Most clients take a config file shaped like this:
⚠Field names differ
between clients — check your client's docs:
· top-level key mcpServers · servers · context_servers
· URL field url · serverUrl · httpUrl
· VS Code requires "type": "http"; most infer it
How to know it worked
Ask your agent: “what sys-buddy tools do you have?” You should see
rules, readiness_check, send_message,
report_status…
If it lists them you are connected — nothing else to do. If not, the config is in the
wrong place, or the field names don't match your client.
Got it working? Tell us which client and we'll add it to the list.