# Cookrew > Cookrew is an open-source desktop workspace for running a team of AI coding agents on one canvas. It runs Claude Code, Codex, OpenCode and Pi side by side, records every agent turn as a checkpoint, and can serve a saved team at a cookrew.dev address where anyone can open a live session from a browser or from the Cookrew app. - Website: https://cookrew.dev - Source: https://github.com/cookrew/cookrew-app (MIT) - Marketplace of served agent teams: https://cookrew.dev/market - Getting started: https://cookrew.dev/start - Features: https://cookrew.dev/features/canvas, https://cookrew.dev/features/harnesses, https://cookrew.dev/features/checkpoints, https://cookrew.dev/features/board, https://cookrew.dev/features/cli, https://cookrew.dev/features/mobile, https://cookrew.dev/features/workspaces, https://cookrew.dev/features/marketplace ## Definitions - Marketplace: The Cookrew marketplace lists served teams: teams of AI agents that stay on their author’s machine. A caller signs in with a cookrew.dev account, buys a seat once if the team is priced, and gets a sandboxed session of their own. The relay carries encrypted bytes it cannot read; money goes directly from caller to author and cookrew.dev takes no cut. - Checkpoint: In Cookrew every agent turn is a checkpoint. You can scrub back through a session, fork a new agent from any past turn, and pin a version when a team is exported or called. Exporting or calling never touches the original session. ## Facts - Harnesses: Claude Code, Codex, OpenCode, Pi, Shell - Platforms: macOS (Apple Silicon), Windows (preview) - Tests green: 4,975 (2026-09-03, vitest, full suite on the dev branch) - Relay cipher: X25519 → HKDF-SHA256 → AES-256-GCM; the relay reads nothing ## FAQ ### What is Cookrew? Cookrew is an open-source desktop workspace for running a team of AI coding agents on one canvas. It runs Claude Code, Codex, OpenCode and Pi side by side, records every agent turn as a checkpoint, and can serve a saved team at a cookrew.dev address where anyone can open a live session from a browser or from the Cookrew app. ### Is Cookrew free and open source? Yes. Cookrew is MIT-licensed and developed in the open at https://github.com/cookrew/cookrew-app. The desktop app is free. Served teams on the marketplace are priced by their authors; many are free and need only a cookrew.dev account. ### Which AI coding agents does Cookrew run? Claude Code, Codex, OpenCode and Pi ship as presets, plus a plain shell. A harness declares its capabilities in Cookrew’s registry, so new ones are added without changing how orchestration works. Any mix of them can work in one team. ### Can I run Claude Code and Codex together? Yes. Place both from the dock, wire them with cookrew connect, and make one of them the orchestrator. Both answer the same CLI, so a Claude Code orchestrator can dispatch to a Codex reviewer and read its reply as a checkpoint. ### Do I need my own API keys? Each harness uses its own login or key on your machine, exactly as it does in a terminal. Cookrew adds none of its own and never sees them. Local models work through harnesses that support them, such as Pi with a local provider. ### What is the Cookrew marketplace? The Cookrew marketplace lists served teams: teams of AI agents that stay on their author’s machine. A caller signs in with a cookrew.dev account, buys a seat once if the team is priced, and gets a sandboxed session of their own. The relay carries encrypted bytes it cannot read; money goes directly from caller to author and cookrew.dev takes no cut. ### What does “serving a team” mean? Serving publishes a saved team at cookrew.dev/@you/team-name. The team keeps running on your machine; each caller gets a sandboxed session workspace minted for them, which you can end at any time. The registry lists the address and marks it live only while your relay connection is up. ### How much does a seat cost, and who gets the money? The author sets the price of a seat, charged once at the door and never per question — the seat follows you to any device you sign in on, and the author can end it. Card payments go through the author’s own Stripe checkout; USDC payments use x402. cookrew.dev holds none of it and takes nothing. ### Is my code sent to cookrew.dev? No. A served session runs on the author’s machine inside a sandbox. Between a caller and a door, every byte is sealed in the caller’s browser or app (X25519 → HKDF-SHA256 → AES-256-GCM) to the door’s key; the relay moves ciphertext it cannot read. Your own local canvas never touches cookrew.dev unless you serve a team. ### Can I use a team from a browser or from my phone? Yes. Every team page on cookrew.dev carries the team’s own terminal, the same PTY a placed card gets, drawn in the browser. The Cookrew phone companion shows your own canvas, cards and Board on a phone over Wi-Fi or Tailscale. ### What is a checkpoint? In Cookrew every agent turn is a checkpoint. You can scrub back through a session, fork a new agent from any past turn, and pin a version when a team is exported or called. Exporting or calling never touches the original session. ### How do I install a team from a link? Click “Open in Cookrew” on a team page, or paste the address into Cookrew → Import a team. The app shows the team’s face first and asks before placing anything; a link on its own never installs.