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.232 Home All releases olderv2.1.231 v2.1.233newer
Claude Code v2.1.232

Fork refusal builds its flag list from one place

Under the hood
Useful1 Signal0
Elsewhere

The can't-fork message builds its flag list from one shared constant; the text is unchanged.

What

The "Can't fork" message no longer hardcodes the list of launch flags that block forking; it interpolates a shared constant, so the enumerated flags are defined once. The visible text about safe or bare mode is unchanged.

Evidence

Can't fork: this session was started with launch flags (safe or bare mode,

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.232 →