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.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

Carrying and reporting your local permission mode in remote sessions is gated off

Not switched on
Useful3 Signal4
Sessions Notable

Remote sessions could inherit your local permission mode and effort level, but no value is compiled in.

Forwarding permissions.defaultMode and effort into claude --remote and reporting the decision both sit behind remote flags with no compiled value.

Feature flag
tengu_violin_strad Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.238: not a boolean we can read

tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.238: on

Read once, for one account on one subscription tier, against v2.1.238. It isn't a statement about your account. What a flag value here can and cannot tell you

--remotepermissions.defaultMode
What

Claude Code can now take the default permission mode and effort level from your local settings, forward them into a session started with claude --remote, and report at startup what it decided. Both halves sit behind remote feature flags that have no value compiled into this build, so with no server configuration a remote session still starts without your local permissions.defaultMode and nothing about the decision is reported.

Details
  • Forwarding requires the remote flag tengu_violin_strad, which is looked up from the server, has no value compiled into the build, and is treated as false if the lookup throws.
  • The forwarding check ANDs an existing precondition with that flag lookup, and its single result is passed to remote-session setup both as the general gate and as the flag deciding whether the settings mode is forwardable.
  • A new helper assembles the startup report: whether a settings default was considered, whether one is present, its value, the active mode and the effort.
  • Every field of that report except the presence bit, settingsDefaultModePresent, is blanked unless both tengu_violin_wood and tengu_violin_strad are on, and both are compiled with a false fallback.
Evidence

tengu_violin_strad, settingsDefaultModePresent

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