Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Placing files in a cloud session's home folder is checked more carefully

Copying files into a cloud session's home folder now confirms the source did not change mid-copy and records how long a setting check waited

Under the hood Internal Changes
JSON All of v2.1.290
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
Internal ChangesKind: in v2.1.290,
Internal ChangesSection of the release
What

In cloud sessions, Claude Code can copy files into the session's home folder. Before it does, it checks a server setting, tengu_hazy_nova, which is off unless it is switched on remotely. Claude Code now measures how long it waits for that check and records an analytics event, tengu_stage_file_home_flag_wait, with one of three values:

  • on: the setting was on
  • off: the setting was off
  • not_loaded: the setting had not arrived from the server yet

After copying a file, Claude Code also checks that the source is still the same file on disk it started with. If the source was swapped for a different file during the copy, it reports that and cleans up.

Why

This mostly makes file placement in cloud sessions harder to get wrong and easier to observe. A file that is replaced while it is being copied no longer ends up in the home folder unnoticed.

Read from
Feature flag
tengu_hazy_nova 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.290: 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.290. 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 on for tengu_hazy_nova, 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 off for tengu_hazy_nova, 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 on for tengu_hazy_nova, 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 off for tengu_hazy_nova, 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 on for tengu_hazy_nova, 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 →

See this entry in the whole of v2.1.290 →

Feedback