What
When starting a cloud or remote (teleport) session and the container begins empty, Claude Code can now start the session right away instead of waiting. A background process races to "arm" (seed with git data) the container:
- Success or a fixed time ceiling (90 seconds) determines when the session is finally reported as created, via a new
containerOrigin.kind === 'created_empty'path. - Reporting the session as created (and the related directory-sync telemetry) is deferred until the arming decision resolves or the ceiling is hit.
- If arming ultimately fails or times out, the first pending upload to the container is discarded rather than sent to a container that never got properly seeded.
Why
This lets cloud sessions feel faster to start, since the user doesn't have to wait for the container to be fully seeded before beginning work, while still avoiding data loss if the seeding process fails or takes too long.