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

Settings sync holds back credential-looking content and says so

Remote settings sync now keeps credential-looking files and rules on this machine, reports them, and logs dropped credential rules as warnings

Group of 2 You'll notice Improvements
JSON All of v2.1.293
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Settings SyncArea: what it touches
ImprovementsKind: in v2.1.293,
ImprovementsSection of the release

Unclear Whether this screening is always on is not known, so it is unclear whether every user's sync holds these files back.

What

When settings are synced to a remote session, Claude Code now holds back content that looks like it contains a credential, such as a password or access key, and reports what it held back.

  • The sync status line can now say that some files were kept on this machine because they look like they hold a credential.
  • Settings summaries add credentialTextsWithheld, settingsKeysWithheld and droppedRules counts.
  • If any credential-restriction rules were dropped, the summary is logged at level warning instead of debug. Before, a warning was used only for dropped rules or for settings that could not be read, were rejected or were too large.
  • The sync payload now includes refiltered_credentials and refiltered_credential_restrictions next to refiltered_keys.
  • The managed-settings summary in usage reporting gains credential_texts_withheld, rules_dropped_credential, restrictions_dropped_credential, withheld_credential and claude_md_withheld_credential.

Why

If something you expected in a remote session is missing, the status line and the logs now tell you it was held back because it looked like a credential, rather than leaving it unexplained.

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 doubtWhether this screening is always on is not known, so it is unclear whether every user's sync holds these files back.

See this entry in the whole of v2.1.293 →

Feedback