Search BrigadeStack

Search BrigadeStack pages and docs.

BrigadeStack
Menu
Docs menu

Docs / Shared memory

Cloud agents

How ChatGPT dots and Claude Duet connect to shared memory, and the generic connection in the 0.32.0 beta.

Cloud agents run in another company’s app, so they cannot read your repo. They reach shared memory through the backend instead. Every connection below needs the backend running, a public host for the connector, and an access check in front of it. None of them works on a local-only setup.

ChatGPT dots

A ChatGPT dot connects a ChatGPT agent to your memory, the backend inbox and task dispatch. It shipped in 0.28.0. It exposes 33 tools.

You need:

  • pip install brigade-cli[grokbot], plus uvicorn in the same Python environment. In 0.31.0 grokbot is the name of the extra that installs the MCP SDK and PyJWT[crypto]. 0.32.0 beta: the extra is named connector, and grokbot stays as an alias for one release.
  • A runtime JSON file with mode 0600 inside a directory with mode 0700. python -m brigade.dot runtime-template --pack dot prints a template.
  • A backend credential enrolled for the dot, and a private state directory.
  • A dedicated public host that routes /mcp through a Cloudflare Access application to the listener on 127.0.0.1:8779. The listener refuses to run on Windows, and the service unit is a systemd unit.

In 0.31.0 the only setup route is the connector pack command, whose name predates the removal of Grok Bot: brigadestack run cloud grokbot pack setup --id dot ..., which previews and then applies with --apply, followed by pack doctor, pack canary and pack install-service. The other grokbot subcommands are the queue, which you do not need for a dot.

0.32.0 beta: the run cloud grokbot commands are removed. Use brigadestack hub connector setup --id dot --runtime-path <file> ... --apply, then hub connector doctor, canary and install-service with the same --id. The dot and duet ids are unchanged.

Claude Duet

Claude Duet ships in 0.31.0.

Duet lets Claude in claude.ai read your memory, skills, inbox and fleet views. It registers 22 tools by default. Dispatch is off by default. With the optional dispatch keys it registers 29, including tools that submit work, follow up on it and interrupt it.

It needs the same SDK install as a dot, plus:

  • Its own Cloudflare Access application, separate from the one a dot uses.
  • A backend credential enrolled for agent:duet, in its own token file.
  • A private state directory that no other connector uses, and a runtime JSON file.
  • A public route to 127.0.0.1:8780.

Setup is the same flow as a dot (the 0.31.0 pack commands, or hub connector in the 0.32.0 beta), with --id duet and --allow-origin https://claude.ai. In claude.ai you then add a custom connector that uses OAuth with automatic client registration against the Duet Access application.

Any cloud agent

0.32.0 beta. The generic connection is a third connector profile, cloud-agent, for any cloud agent that speaks MCP. It is not in 0.31.0, where a cloud agent needs one of the two connectors above.

It exposes memory_search, memory_card and handoff_write. When you set messaging_enabled to true it adds inbox_list, inbox_ack, inbox_reply and message_send, with the same recipient grants and hourly send limit as Duet. It has no dispatch, fleet, event or skill tools.

It runs on its own hub identity, agent:cloud-agent, with its own state directory and credential, and listens on 127.0.0.1:8783. Authentication is a listener token by default: a file holding a 43 to 512 character URL-safe secret that differs from every hub and connector credential, sent as a bearer token. Setup generates the token file for you when it is missing. Access-signed identity is the alternative mode. Both modes need a loopback bind, so you put a TLS tunnel or reverse proxy in front of it. Failed authentications are rate limited.

Set it up with brigadestack hub connector setup --id cloud-agent --runtime-path <file>, add --apply to write it, then run hub connector doctor, canary and install-service, and serve for the unit’s command. Those commands do not start the service.

What every connection can read

Both connectors read memory under their own identity, and each needs read access on the fleet scope. A connector gets the top matching cards inside responses it already requests, so the agent does not need a separate memory tool. Cards that contain private details such as hostnames, addresses or paths are never sent to a connector. A card published with brigadestack memory hub push is stored as unreviewed, and a connector is sent only reviewed cards and its own.

See How shared memory works for what the backend stores and Run the backend for setup.