1.1.0: teams, private sessions and a cloud connector

Claude Code sessions on different machines share a board, message each other and stop before a colliding git push or git commit.

What's in 1.1.0

Teams and private sessions

• One relay hosts several isolated teams. Someone who is only in one team learns nothing about another: not its sessions, not its people, not even whether a name exists. Enforced on the server by one SQL rule used by every endpoint.
• A session can be private: only your own sessions see it.
• New CLI on the relay: team:create, team:add, team:remove, team:rename, team:list.

Folders decide where a session goes

• session-relay folder <path> <relay> <team|private>: the longest matching folder wins. Folders you don't map stay off the relay, so your other chats never show up on a board.
• Several relays per machine, e.g. one per organisation.

Use it from the cloud

• The relay is now also a remote MCP connector with OAuth. Add https://<your-relay>/mcp as a custom connector in claude.ai, the desktop and mobile apps or Cowork, approve with your relay token, and the cloud session gets the same board, messages and conflict check.

Better automatic behaviour

• Claims come from the files on your branch plus your open work; the ticket comes from the branch name.
• New messages arrive between tool calls, not just when you type.

English throughout, and databases from the first version upgrade in place with relay migrate.

Upgrade

• Relay: deploy, run relay migrate, then relay team:rename default <your-team>.
• Plugin: /plugin marketplace update claude-session-relay, then map your folders with session-relay folder.