You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TeleportArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
When Claude Code uploads your repository to a cloud (teleport) session, it now checks whether your home directory is itself a git checkout that contains the project. This is common when dotfiles, your personal configuration files, are kept in git. In that case the upload is forced onto the hardened path or refused. The error explains that a Claude Code session started there could write the checkout's git files, or the user-level git configuration the upload would run under.
New refusal reasons include:
home_checkout
settings_unreadable
config_in_checkout
partial_clone_home_checkout
partial_clone_config_in_checkout
The upload is also refused when git configuration lives inside a directory your settings open to sessions. The messages point at permissions.additionalDirectories, sandbox.filesystem.allowWrite, an Edit rule or --add-dir, and suggest keeping a dotfiles repository bare with --git-dir. Failed write-tree or read-tree steps on partial clones now stop the upload early, the older git-not-on-PATH message also lists directories below such a home, and telemetry gains below_home_checkout.
Why
If your home directory is a dotfiles repository, cloud-session uploads from projects inside it may now be refused. The fix the messages suggest is keeping the dotfiles repository bare with --git-dir, or narrowing which directories sessions can write to.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed sandbox excludedCommands entries not matching git rev-parse --git-dir, programs named like shell builtins, and commit messages…
