Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.240 ·

"Switch your default effort to medium?" prompt, complete but with no text to show

A one-time prompt offering to switch your default effort to medium exists but has no text.

Nothing to try yet Notable In Development
JSON All of v2.1.240
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Effort LevelsArea: what it touches
In DevelopmentKind: in v2.1.240,
What probably matters to youSection of the release

The effort-medium dialog is fully wired into the prompt sequence but its required wording comes from a remote config key that ships empty.

What

A one-time dialog offering to change your saved default effort from high to medium, confirming with Effort set to medium and saved as your default or a warning if the write fails. It is fully reachable in the prompt sequence, ahead of the LSP and plugin hints, and marks itself seen so it appears at most once. But its wording comes entirely from the remote config key tengu_radiant_island, whose in-binary value is an empty object and whose body text is required, so with no server value the dialog never appears.

Details
  • Only the body text is required; title, confirm label and cancel label have in-code defaults.
  • You are only eligible if you have no effort pinned anywhere, or have pinned high in your user settings. Any other configuration disqualifies.
  • The parent picks it as effort-medium-nudge in the same chain as the fullscreen upsell and remote callouts.
Evidence

Switch your default effort to medium?

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

Read from
Feature flag
tengu_radiant_island Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.240: not a boolean we can read

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

What has happened since
Flag reading moved The flag server now returns [] for tengu_radiant_island, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_radiant_island, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_radiant_island

See this entry in the whole of v2.1.240 →

Feedback