Source Intelligence

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.236 Home All releases olderv2.1.235 v2.1.237newer
Claude Code v2.1.236

Live collaborative-document branches are compiled out, not merely flagged off

Not switched on
Useful1 Signal5
Artifacts Notable

Live collaborative-document branches sit in artifact publishing but can never run, even with server config.

Streaming and remote publish branches with durable arming are reached only through a null handle and a false constant nothing assigns.

What

The artifact publish result gained branches choosing between a gate-closed, streaming or remote suffix, plus a note about durable arming. Every one of them is reached through a module handle declared as null and a boolean declared as false that nothing in the build ever assigns, so none of it can run and no server-side config can enable it.

Details
  • Unreachable in this build: the gate-closed result suffix, the live-edit and live-doc stream gates, the durable-arming subscription state and its status line.
  • The same block holds a read-page-data constant that is likewise a compile-time false, which leaves the set of read_page_data schema names empty.
  • These strings appear in the build and look like shipping features; they are excluded at build time rather than switched off by a flag.
Evidence

LIVE_DOC_RESULT_SUFFIX_GATE_CLOSED

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

See this entry in the whole of v2.1.236 →