Docs
Connect your agents once. Then share a session from the chat or the terminal, and pull somebody else’s into your own repository.
1. Install & Connect Your Agents (Once)
Tell your agent
Install and set up Flatbread using https://flatbread.io/install.mdOr run it yourself
npm install -g flatbread-cli && flatbread setupIt needs Node.js 20 or newer. Setup registers the Flatbread MCP server with Claude Code, Codex, Cursor, Google Antigravity, OpenCode, Gemini CLI, GitHub Copilot CLI and Cline, and writes the skill that tells an agent when to use it — each only where that agent is installed. You run it once: an update, or an agent you install later, is taken care of the next time Flatbread runs.
3. Pull a Run & CLI Reference
Tell your agent
pull flatbread <id>Or paste a run’s link. The agent reads its execution brief and applies the pattern and its guardrails to this repository.
Or in a terminal
flatbread pull <id>Prints the run’s execution brief.
Every command flatbread setup Connect the agents on this computer, once flatbread share Share your newest session, from whichever tool wrote it flatbread share <tool> Share one tool's newest instead: claude, codex, gemini... flatbread pull <run> Print a run's execution brief, for your agent to read (its ID or link) flatbread search <words> Find shared runs: public ones, and your own when signed in flatbread login Sign in. Share asks you to when it needs to flatbread whoami Show who is signed in on this computer flatbread logout Sign this computer out flatbread doctor Something not working? Checks this computer and says what to do flatbread tools The tools Flatbread reads, and what each one records flatbread setup --uninstall Undo setup flatbread mcp What setup connects your agents to. They start it, not you 4. What Leaves Your Machine
Nothing, until you press Confirm. Then the session goes up as the review page showed it, with every secret already replaced on your machine.
Replaced first, with no network call and no model
A secret assigned to a name
API_TOKEN=hunter2-prod-7731→API_TOKEN=«REDACTED:secret»A login in a connection URL, and a private address
postgres://app:hunter2@10.0.0.4:5432/shop→postgres://«REDACTED:db_credentials»@«REDACTED:private_ip»:5432/shopA key with no known prefix, by how random it is
key Xk9mQ2vR7tLp4Wz8Nc3Bf6Hj1Ds5Ga0Ye→key «REDACTED:high_entropy»Your username, in a path
/Users/maya/Desktop/app→/Users/«REDACTED:user»/Desktop/appA word you add: --redact acme-internal
the acme-internal cluster→the «REDACTED:custom» clusterAll 24 kinds it looks for
- AWS access key id
- PEM private key block
- GitHub token
- GitLab personal access token
- Google API key
- Google OAuth access token
- Stripe live or webhook secret
- npm access token
- Supabase secret key or access token
- Vercel token
- Anthropic API key
- OpenAI-style API key
- Slack token
- JWT
- Login inside a connection URL
- Secret in a URL query
- Bearer header value
- Home directory username
- Private network address
- Internal hostname
- Secret assigned on one line
- Random-looking string (a key with no known prefix)
- Email address
- Value of a credential-named field
The original is not uploaded. The run keeps only what kind of thing was there, where, and how long it was.
Then you decide, on the review page
- Read the whole session as it will be sent, each replacement marked.
- Keep one that is not a secret, or hide a word it missed.
- Hide every diff and file’s contents with one switch.
- Choose private, unlisted or public. Private unless you change it.
Sent when you press Confirm
Your prompts, the agent’s messages, the commands it ran and what they printed, the diffs it made, the model, timings and token counts, and the folder, git branch and commit it ran on.
Afterwards, Manage run on the run can hide another word or phrase, change who can open it, or delete it. A redaction can be added, never undone. Privacy