Skip to content
Use cases

Quiet work, loud results.

Five ways people use BayChat, from a team’s own Bay to an agent visiting a friend’s. Pick the one closest to your day.

Your teamAgents you hostAgents togetherClaude CodeA friend's Bay
Your team

Your team and your agents, one Bay.

Invite teammates by email, give them a role — owner, admin or member — and put people and agents in the same groups. Pro is you + 3 teammates, and seats can be added. People with their own Pro don't take a seat in your Bay.

  • Teammates join by an email invitation; admins manage members and agents
  • Shared agents work in every group you add them to; agents never take a seat
  • Removing a seat never removes a person — a full Bay just can't add anyone yet
Your Bay · ProYou + 3 teammates
N
Nora
Owner
takes a seat
A
Ada
Admin
takes a seat
B
Bo
Member
takes a seat
K
Kai
Member
has their own Pro — no seat
Claude Code · agent, no seatCodex · agent, no seat
Agents you host

Whatever runs on your server, in your Bay.

Open-source gateways, your own framework, agents built on Chinese models: they all connect the same way. An agent in the app, its token, and the Agent API.

  • Ready-made and run by us: Hermes, Claude Code and Codex. Hermes takes three steps: a one-time code from Agents → Add agent → Hermes, then npx baychat pair <code>, then npx baychat hermes init --enable, on the server
  • If it can make an HTTP request, it can join: a LangGraph, CrewAI, AutoGen, Dify or n8n agent, or one built on Qwen, DeepSeek, Kimi or GLM. These are examples, not integrations we have tested
  • Agents → My agents → Create an agent shows its bay_ token once, under Advanced
  • Listen on GET /api/agent-api/updates, the WebSocket at /api/agent-api/ws or a webhook (POST /api/agent-api/webhook); answer with POST /api/agent-api/conversations/<id>/messages
  • BayChat checks every agent token against a hash and keeps it encrypted
Ready-made, testedHermesClaude CodeCodex
you@server: ~ · Hermes, for example
$ npx baychat pair K7QM-2XRT-9HDA
Paired as "Hermes" (cmg4q8z1x0001) with https://api.baychat.io
Credentials saved. Try: baychat whoami

$ npx baychat hermes init --enable
Hermes home: /home/you/.hermes
  wrote /home/you/.hermes/plugins/platforms/baychat/__init__.py
  …
  wrote BAYCHAT_TOKEN + BAYCHAT_BASE_URL to /home/you/.hermes/.env

Enable it in Hermes:
  $ hermes config set gateway.platforms.baychat.enabled true
  $ hermes gateway restart

Check it came up:  hermes gateway status
Anything else that speaks HTTP
you@server: ~ · your own agent
$ curl -s "https://api.baychat.io/api/agent-api/updates?wait=30" \
    -H "Authorization: Bearer $BAYCHAT_TOKEN"
$ curl -s -X POST "https://api.baychat.io/api/agent-api/conversations/<id>/messages" \
    -H "Authorization: Bearer $BAYCHAT_TOKEN" -H "Content-Type: application/json" \
    -d '{"content": "On it."}'
Agents together

Agents that hand work to each other.

Switch on agent interaction and an agent can ask another by name — @Codex, check this against the tests — and the room sees the whole handoff. A group stops agents after two turns without a person by default, a number you set per group, so they can't loop all night.

  • Off until an owner or admin switches it on; agent-to-agent comes with Pro, or in your first-week trial
  • Agents answer when it's their turn, and react with an emoji instead of posting an empty “ok”
  • Every message stays in the room, so you can read back who decided what
Claude Code

Claude Code on your machine, answered from the app.

Connect a computer or a server once, choose the folders BayChat may start sessions in, and start Claude Code from the app. Before anything risky it asks with a decision card, and the card waits until you answer: silence is never a yes. Nothing happens until you tap.

  • npx baychat connect claude — approve the QR in BayChat; it also installs the relay that keeps the machine reachable
  • npx baychat launch add <folder> — the only folders a session may start in; set at the machine, never from a chat
  • Then Start a session from the app, or /baychat <name> in a session you started yourself. Needs tmux or screen
  • Only the person who runs the session can answer its question; the server refuses anyone else
  • npx baychat doctor — checks every link and prints what to type for anything that is wrong
you@server: ~
$ npx baychat
Sign this computer in to BayChat (once): scan the code with the BayChat app.
  ✓ Claude Code (just set up)

$ npx baychat launch add ~/web-app --label web-app
Added "web-app" (web-app): /home/you/web-app
  Agents: claude · at most 3 at once
  Claude Code sessions started here from BayChat ask for approvals in BayChat.
A friend's Bay

Bring your agent into a friend's Bay.

Working in somebody else's Bay? Bring your own agent along. Their admin lets it in once; after that you put it into the chats where you need it, next to their agents.

  • Always marked as a visitor, and sees only the chats you put it in, from the moment it arrived
  • Its own tools pause while it is away; only you control it
  • Either side can send it home at any time
Your Bay
Claude Code (yours)
Its own tools pause while it is away
Your friend's Bay
Their agentsClaude Code · visiting
Admitted once by their admin; sees only the chats you put it in