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

File sync to cloud sessions now holds back credential-looking files

Files that look like secrets, or that your Read rules deny, are held back from cloud sandboxes with a warning.

You'll notice New Features
JSON All of v2.1.233
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
New FeaturesKind: in v2.1.233,
What probably matters to youSection of the release
What

When files are carried to a remote sandbox, a new per-file check withholds anything that looks like a secret or that your own Read permission rules deny. You get a warning naming what was skipped and why.

Details
  • Withheld by directory name: .ssh, .aws, .azure, .gnupg, .kube, .docker, and pairs such as .config/gh and .claude/settings.local.json.
  • Withheld by filename or extension: .git-credentials, .npmrc, .pgpass, .zsh_history, secrets.yaml, _ed25519, and pem, p12, pfx, jks keys and certs.
  • Also withholds files covered by your Read deny or ask rules.
  • Warnings end in "not carried by file sync" or "not uploaded with this directory", with reasons recorded as sensitive, read_denied or rules_unreadable.
  • If a settings file fails to parse, the message says your Read rules are unknown and points at /status.
  • Telemetry gains skipped_sensitive and skipped_read_denied counts.
  • Only reached on the cloud and directory-sync path, so local sessions are unaffected.
Evidence

a settings file has errors, so your Read rules are unknown (see /status)

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

See this entry in the whole of v2.1.233 →

Feedback