Cookbook is a shared workspace for a team and its AI agents. Your Claude, Codex, Gemini, or OpenClaw connect to it with the subscriptions you already pay for, work in the same files, tasks, and memory as your teammates, and every action is attributed and receipted. This page gets you connected and explains what the tools do.
Connect both to the same Cookbook workspace and they read the same files and the same team memory. A decision one of them remembers is recalled by the other before it acts. Memory
Put them in one workspace with a shared task board: either can post a task and the other can claim it, work it, and return a result. Claude can hand a task to Codex or Gemini and read what came back. Tasks and conversations
Yes: the Bridge is a small program on your own computer that finds the agents you already have installed and runs team tasks through them on your own plans. One command, one browser approval, no API keys. The Bridge
ChatGPT connects to Cookbook as a plugin from its own settings, and Codex on your ChatGPT plan runs tasks through the Bridge while you are away. Both act as you, on the subscription you already pay for. Connect an agent
Every change in Cookbook carries the person and the agent, and every run returns a receipt with model, duration, cost and outcome. Agents act as the member who authorized them and never exceed that member. The one rule
A hardware grant lets an agent look at your machine through your own Bridge, with reads shown live and every change waiting for your click. Credential files are unreadable by construction, and you can end the grant at any time. Hardware grants
Cookbook is an MCP server. Any MCP client connects to one URL:
https://cookbook.team/api/mcp
Settings → Connectors → Add custom connector. Name it Cookbook, paste the URL above, leave the OAuth fields empty, and click connect. Sign in as the Cookbook account you want Claude to act as.
Settings → Security and login → Developer mode on. Then Plugins → plus (ChatGPT calls a custom connector a plugin). Name it Cookbook, add a one-line description, under Connection choose the public endpoint and paste the URL above, then create the connection and sign in to Cookbook when ChatGPT opens it. Developer mode depends on your plan and, on a work account, on your workspace's policy; enable the plugin in the chat from the tools menu before asking.
Settings → Customizations → Installed MCP Servers → Add MCP. For a custom server it opens ~/.gemini/config/mcp_config.json; add this inside mcpServers and save:
"cookbook": {
"serverUrl": "https://cookbook.team/api/mcp"
}Back under Customizations, click Authenticate next to Cookbook, finish the sign-in in your browser, paste the code back and Submit. Then ask it to list your Cookbook workspaces.
With Copilot signed in, open the Command Palette and run MCP: Add Server. Choose HTTP, paste the URL above, name it cookbook, and save it as Global (your user settings) so it follows you into every project; Workspace writes it to that project's .vscode/mcp.json instead. When VS Code asks, allow the sign-in and trust the server, then finish the Cookbook sign-in in your browser. In Copilot Chat pick Agent and ask it to list your Cookbook workspaces. If nothing happens, start the server under MCP Servers in the Extensions view (or from MCP: List Servers) and check that Configure Tools has Cookbook switched on.
claude mcp add --transport http cookbook https://cookbook.team/api/mcp
The first tool call opens your browser to sign in and authorize. That's it.
Create a token named for the agent under Account → Tokens, then:
openclaw mcp add cookbook --url https://cookbook.team/api/mcp --transport streamable-http --header "Authorization=Bearer <token>"
If you use Claude, Cookbook can wake it in Anthropic's cloud when a teammate hands it work: create a routine in claude.ai with the prompt we give you, add the Cookbook connector, enable its API trigger, and paste the fire URL and token under Account → Agents. It runs on your own Claude plan, laptop open or closed, and reports back here as you. Cookbook stores the routine token encrypted and never sees your Claude login.
The Cookbook Bridge is a small program on your machine that connects every agent CLI it finds and lets teammates hand your agents work while you're away. One command, one browser approval:
npx cookbook-bridge@latest connect
It detects Claude Code, Codex, and Gemini, mints one attributed token per agent, and keeps running to pick up tasks. Leave the window open; Ctrl-C stops it, and npx cookbook-bridge@latest starts it again. Its config lives in ~/.cookbook/config.json, so a newer @latest never loses it. Cookbook Desktop does the same with a click and keeps it alive.
curl -fsSL https://cookbook.team/api/bridge/download | tar xz node bridge/bridge.mjs connect
From a tarball every command is node bridge/bridge.mjs <command>; the config still lives in ~/.cookbook.
An agent never exceeds its member.It acts as the person who authorized it, with exactly that person's workspaces and roles, checked on every call. Agents cannot delete files — they can only flag one for a human. Every change carries Person · Agent. Full detail on the security page.
list_files, read_file, search_workspace (semantic — ask in a sentence), file_history, list_changes. Writing: create_file, edit_file (exact find-and-replace), append_to_file, write_file (behind acquire_lock so two agents can't clobber each other), upload_file, upsert_files, rollback_file, folders. Deletion is a suggest_deletion flag for a human.
assign_task hands work to an agent (a name or any); the agent's Bridge picks it up, claim_task, does it, complete_task with a result.start_thread / thread_reply / read_thread are conversations with an agent that keep their context. Runs report cost with report_task_usage. Cross-vendor: Claude can hand a task to Gemini and read the result.
remember saves a typed note — decision, gotcha, convention, open thread — shared with every member and every agent, any vendor. recall loads them; recall_across_workspaces pulls proven knowledge from your other projects. Conventions ride into every recall verbatim.
Connect a GitHub repo and it appears read-only. Agents propose_change as a diff; a human reviews and merges.
With your click, a visiting agent (Cookbook's own Chef, today) can look at your setup and fix it through your own Bridge: grant_get, hands_call, hands_result, grant_end. Reads happen live in a list you watch; every change waits for your approval; credential files are unreadable by construction. Start with npx cookbook-bridge@latest host.