What leaves your machine

Only the session you run the command in, and only after you confirm.
The session file without screenshots, the agent's thinking and Claude Code's bookkeeping lines. Tool output is cut to its first 60 lines, what the agent passed to a tool to its first 40. What the agent read and ran during the session is part of the session, so check it on the draft.
If the session ran in a git repository: its GitHub address, the branch, and the titles, hashes and size of the commits the session made, not the commits themselves. Our server asks GitHub whether the repository is public before the address is linked; a private one is never linked. Its name shows only to the draft's own audience, you or your team, and is removed when the Build is published. The Build header shows the repository, the commit count and change size, and each commit by title as a link to it on GitHub; commit titles also help the model draft the outcome.
The files that changed, as diffs, up to 300 lines a file. In Claude Code the plugin takes a git snapshot of the working tree at each prompt and answer (in a temporary index and a ref of its own, refs/coders-talk/: your branch, index and files are not touched), so it sees what the agent changed through Bash too, what you changed by hand between its answers, and the commits made in each turn with their hashes. Without git, or in Codex, the diffs come from the agent’s own edits in the session. Env, key and credential files go by name only, lock and build files too. Readers see the code under each moment only if you tick it on the draft. A team decides whether its code may be shown outside the team.
Nothing secret. Keys, tokens, connection strings, email addresses, public IP addresses and internal hostnames are replaced with [REDACTED:TYPE] on your computer, before anything is sent, in commit titles and the branch name too; a home folder in a path becomes ~. The preview lists each finding by number and kind, never its value, and --keep=<numbers> sends one as it is. Words to hide in every session, like client names, go in ~/.coders-talk/privacy.json. Our server checks again with the same rules and redacts anything it finds for good: the value is kept nowhere.
What readers see is yours to choose when you publish: the summary only (the moments as you wrote them, the result, stack, time and interventions: no words from the conversation, no code), selected excerpts (the moments you pick, with the prompt as typed, what the agent ran and, if you show it, the code), or the full session. The summary is the default. A draft you never publish loses its session text after 90 days without changes; the draft stays.
Where it goes: your private Builds, or your team's space when the repository belongs to a team you are in. The plugin asks the site for your teams to say which; --private and --team decide it yourself.
How many tokens the session spent, per model: counted on your machine from the session file, and only the numbers are sent.
In auto mode, the same for every session that ends, without asking; only if you turned it on for this computer.
A connected plugin can only start imports: it cannot publish, comment or change your profile. Disconnect it in Settings at any time.

Other agents

Upload the session file on the import page; the format guide says where each agent keeps its sessions.