You'll notice
Useful4 Signal4
Files that look like secrets, or that your Read rules deny, are held back from cloud sandboxes with a warning.
What's wrong with this entry?
Anonymous. No account, no email.
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/ghand.claude/settings.local.json. - Withheld by filename or extension:
.git-credentials,.npmrc,.pgpass,.zsh_history,secrets.yaml,_ed25519, andpem,p12,pfx,jkskeys 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_sensitiveandskipped_read_deniedcounts. - 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.