Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

A new remote switch with no visible use yet

Claude Code defines a new remote switch, tengu_starry_crescent, but this release does not show what it controls

Nothing to try yet In Development
JSON All of v2.1.318
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InternalsArea: what it touches
In DevelopmentKind: in v2.1.318,
In DevelopmentSection of the release

Unclear What tengu_starry_crescent controls, and what it falls back to when the server sends nothing, is not known.

What

Claude Code defines a new remote switch named tengu_starry_crescent. A remote switch is a setting the server can turn on or off for an account. It sits next to an existing switch, tengu_buzzing_pike, near a size limit of 524288 and a list of markers for creating a thread. No part of Claude Code is shown reading the new switch.

Why

Nothing you can see changes for now. The switch is defined, but what it turns on is not known.

Read from
Feature flag
tengu_buzzing_pike 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.318: not a boolean we can read

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

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

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat `tengu_starry_crescent` controls, and what it falls back to when the server sends nothing, is not known.

See this entry in the whole of v2.1.318 →

Feedback