What
When a cloud or remote-control session is created before its usual git-based directory sync can start, Claude Code now builds and uploads a 'first upload' bundle of the local project directory directly, instead of leaving the session without files. This path:
- Falls back to cloning the project from GitHub if needed
- Reports clear refusal reasons when it can't proceed, including an unborn branch, a shallow or partial local clone, an oversized history, timeouts, or files withheld because they're covered by Read rules, sandbox read-deny settings, or look like credentials
- Archives the session and shows a clear message, such as "File sync was switched off while the session was being created," if the upload can't be completed in time
A new environment variable, CLAUDE_CODE_DIR_SYNC_ENGINE=none, lets a machine disable directory sync entirely.
Why
Previously, a cloud session created before directory sync was ready could end up with no files and no clear explanation. This gives users an actual snapshot of their project in that situation, or, if that's not possible, a specific reason why instead of a silent failure.