{"version":"2.1.282","anchor":"file-sync-clearer-error-when-claude-cannot-hold-its-priv","canonical_anchor":"file-sync-clearer-error-when-claude-cannot-hold-its-priv","heading":"Clearer file sync error when the Claude Code config folder is not writable","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/file-sync-clearer-error-when-claude-cannot-hold-its-priv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Clearer file sync error when the Claude Code config folder is not writable\n\nWhen file sync cannot set up its private folder because of your config home, it now says so and tells you to check it is writable\n\n**What**\n\nFile 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.\n\nThis failure is now counted as the config home being unreadable, rather than as a general git error.\n\n**Why**\n\nIf your `~\/.claude` folder is missing, broken or read-only, the message now points you at what to fix.\n\n- Area: File Sync\n- Names: `CLAUDE_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}