You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.248,
In DevelopmentSection of the release
What
Redaction in "bridge" environments used to hinge only on the environment kind. It now requires both CLAUDE_CODE_ENVIRONMENT_KIND === "bridge" and an active transport that persists outbound frames, so a locally attached transport turns the redaction off.
Details
A new per-host object tracks the active transport and reports whether it persists, whether it was pinned local, and whether the remote bridge is live.
Startup registers the transport as active only when --sdk-url or stream-json output is in play; otherwise it pins the transport local, which makes the predicate false.
Around forty call sites in the control-protocol layer use it: MCP server lists are cut down to name and status, the memory-file list is emptied, absolute paths are substituted, and crash text changes.
Invisible unless the process is launched with the bridge environment kind and a persisting transport.
