Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Bridge-mode redaction now also requires a transport that persists output

You'll notice
Useful2 Signal3
Artifacts not in their notes

Bridge-mode redaction now only kicks in when your transport actually persists sent output.

CLAUDE_CODE_ENVIRONMENT_KIND
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.
Evidence

CLAUDE_CODE_ENVIRONMENT_KIND === "bridge"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →