An unnamed feature switch is split, with Cowork local-agent…

An unnamed feature switch is split, with Cowork local-agent sessions defaulting on

One feature switch now reads a different remote setting, and a second check defaults on only for Cowork sessions running as a local agent

Under the hood Internal Changes

JSON All of v2.1.319

Under the hoodTier: how much it should matter to you

1Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

CoworkArea: what it touches

Internal ChangesKind: in v2.1.319, 06 Nov 26

Internal ChangesSection of the release

Unclear It is not clear what feature either switch controls.

What

Claude Code checks some features against switches set on Anthropic's servers before turning them on. One such check has been split in two:

The existing check now reads tengu_graceful_hoare instead of tengu_bright_kettle, and still counts as off when the server sends nothing.
A new check reads tengu_bright_kettle. When the server sends nothing, it counts as on only if CLAUDE_CODE_ENTRYPOINT is set to local-agent and CLAUDE_CODE_IS_COWORK is set. Everywhere else it counts as off.

When this site last checked, tengu_graceful_hoare read on for both this site's account and an account with no special settings, having switched on since the previous check. tengu_bright_kettle read off for both.

Why

In practice, Cowork sessions running as a local agent get the second feature on by default, while other sessions depend on the server.

Read from

Feature flag

tengu_bright_kettle 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.319: 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.

tengu_graceful_hoare Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

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

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.319. 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 doubtIt is not clear what feature either switch controls.

The name it cites is new in this buildNew in this build: tengu_graceful_hoare

See this entry in the whole of v2.1.319 →

The build it came inv2.1.319

6 Nov 2026 · 480 entries, this one is #462.

Use it now39
You'll notice291
Nothing to try yet13
Under the hood137

Either side of it

v2.1.318Older

Open the release →

Names in this entry

flagtengu_graceful_hoare
One feature switch now reads a different remote setting, and a second check defaults on only for Cowork sessions running as a local agent
flagtengu_bright_kettle
A feature that followed one remote switch now follows a different one, and both count as off when the server sends nothing
envCLAUDE_CODE_ENTRYPOINT
Waiting for MCP servers before a headless run is tidied up and logs more detail.
envCLAUDE_CODE_IS_COWORK
Account-synced skills no longer have file attachments pulled out, except on remote or Cowork runs.

Is this right?