{"version":"2.1.246","anchor":"cloud-sessions-wait-for-the-first-file-upload-before-sending","canonical_anchor":"cloud-sessions-wait-for-the-first-file-upload-before-sending","heading":"Cloud sessions wait for the first file upload before sending your message","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-sessions-wait-for-the-first-file-upload-before-sending","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud sessions wait for the first file upload before sending your message\n\nCloud sessions hold your first message until your project files have actually uploaded.\n\n**What**\n\nA cloud session now holds back your first message until the initial upload of your project files has actually landed on the server, instead of sending it against an empty or half-populated workspace. While waiting it prints progress lines, retries the first push on a backoff schedule, and if it never lands it stops with a \"seed_incomplete\" result. Reached on any `claude --cloud` session; no flag guards it.\n\n**Details**\n\n- The wait is implemented as a gate on the send manager, registered with `onRelease: \"withhold\"`, so queued input is held rather than dropped.\n- Retries only apply on the initial \"create\" upload, not on later incremental syncs.\n- New telemetry `tengu_dir_sync_git_first_send_wait` reports `waited_ms` and one of `wedged`, `released`, `withdrawn`, or `landed`.\n\n**Evidence**\n\n`tengu_dir_sync_git_first_send_wait`\n\n- Area: Cloud Sessions\n- Names: `--cloud`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}