Context Bridge is local-first. It does not enable telemetry or a network service, and it does not modify vendor-owned session records. Its canonical log, configuration, and generated handoffs live on the operator's machine.

Observable work can still be sensitive. A bridge session can include messages, tool activity, commands, test results, file activity, Git state, and checkpoints. The resulting handoff is derived data; the append-only canonical log remains the source of truth.

Strict redaction is the default boundary. Secret-classified events never enter a target prompt, and known credential paths are excluded from file context. Keep the policy strict unless you have reviewed the consequences.

12cb config set security.redaction strict
cb config show

Do not add .env files, secret directories, SSH material, access tokens, or raw session exports to a repository just to make a handoff easier to reproduce. A reproducible handoff should describe work without publishing credentials.

Use a redacted export as the sharing boundary. Save it to a local path, inspect it, and remove or further redact content before attaching it to a ticket or sending it to another person.

1cb export <bridge-session-id> --format markdown --redacted > reviewed-handoff.md

The --redacted flag is not a legal or organizational data-classification system. It is a technical safeguard for common secret patterns and excluded paths; the operator remains responsible for reviewing content before it leaves the device.

Return to Import and continue for the reviewed handoff workflow, or to Getting started for local configuration commands.