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.247 ·

A new protected ~/.claude/seed-admin directory, with nothing yet writing to it

Writes under a new seed-admin folder are hard-denied for everyone, though what fills it is off.

You'll notice Nothing to try yet In Development
JSON All of v2.1.247
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
SandboxArea: what it touches
In DevelopmentKind: in v2.1.247,
What probably matters to youSection of the release

Guard rails for ~/.claude/seed-admin ship live, but the cloud upload that writes there sits behind tengu_teleport_send_to_cloud, compiled off.

What

Claude Code now hard-denies all writes under ~/.claude/seed-admin, both for the model (a safety refusal that cannot be approved away) and in the sandbox, which lists the directory as unwritable alongside jobs and daemon. The only thing that fills it is the cloud-session upload path, reached from "Continue this session in the cloud" in the Teleport menu, which is behind tengu_teleport_send_to_cloud and compiles in as off. The guard rails are live for everyone; the feature they guard is not, absent a server value.

Details
  • The upload stages one private git directory per process there and refuses to run if the directory is not a plain directory owned by you, or if it lies inside the work tree.
  • Denies also cover paths reached through a resolved symlink of the config home.
Evidence

~/.claude/seed-admin holds the private git directories of cloud-session uploads and is managed by Claude Code; it cannot be written directly

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

Read from
Names in the bundle~/.claude/seed-admintengu_teleport_send_to_cloud
Feature flag
tengu_teleport_send_to_cloud 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.247: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.247. 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 off for tengu_teleport_send_to_cloud, 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_teleport_send_to_cloud, 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.247 →

Feedback