You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
File SyncArea: what it touches
ImprovementsKind: in v2.1.282,
ImprovementsSection of the release
What
File sync keeps a private git folder (git is a version-tracking tool) for each working folder, stored under Claude Code's configuration home. When that folder cannot be created because of the configuration home, the error now says that Claude Code's configuration home (~/.claude, or CLAUDE_CONFIG_DIR) could not hold it, and asks you to check that it is a writable directory of yours. The system's own wording goes to the debug log. Before, the raw system message was shown instead.
This failure is now counted as the config home being unreadable, rather than as a general git error.
Why
If your ~/.claude folder is missing, broken or read-only, the message now points you at what to fix.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on Hosting the Agent SDK touched a line naming CLAUDE_CONFIG_DIR after this was published.* Point `CLAUDE_CONFIG_DIR` at a per-tenant directory so tenants do not share the `~/.claude.json` global config. When each config directory serves one working directory and you don't pass a [`SessionStore`](/docs/en/agent-sdk/session-stor…agent-sdk/hostingsee the edit
Confirmed sinceAnthropic's documentation has since written up CLAUDE_CONFIG_DIR, on Error reference.Windows reported an error (EBADF) when Claude Code read this session's transcript file, although the file had opened normally. This can happen when other software intercepts file reads — security, encryption or endpoint-management tools, f…errorssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up CLAUDE_CONFIG_DIR, on Error reference.
