{"version":"2.1.248","anchor":"remote-startup-waits-for-its-credentials-file-instead-of-fai","canonical_anchor":"remote-startup-waits-for-its-credentials-file-instead-of-fai","heading":"Remote startup waits for its credentials file instead of failing fast","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-startup-waits-for-its-credentials-file-instead-of-fai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote startup waits for its credentials file instead of failing fast\n\nRemote sessions now wait and retry for their credentials file instead of failing immediately.\n\n**What**\n\nA remote session that has to read its access token from a file now retries on a fixed backoff (250, 500, 500, 750, 1000 ms) and then waits a grace period for OAuth or API credentials to appear, rather than giving up immediately. It logs \"[spare-claim] session ingress token file not readable yet\" while waiting and reports attempts, whether it recovered, and total wait time.\n\n**Details**\n\n- Only runs for remote invocations started with `--sdk-url` that have no inline session token: `CLAUDE_CODE_REMOTE` set, `CLAUDE_CODE_SESSION_ACCESS_TOKEN` and `CLAUDE_CODE_WEBSOCKET_AUTH_FILE_DESCRIPTOR` unset.\n- The file location can be overridden with `CLAUDE_SESSION_INGRESS_TOKEN_FILE`.\n- A separate re-read path logs \"Session ingress token re-read from well-known file\".\n\n**Evidence**\n\n`cli_worker_lifecycle_claim_token_wait`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}