{"version":"2.1.290","anchor":"startup-checks-of-the-agent-proxy-relay-are-now-deferred-beh","canonical_anchor":"startup-checks-of-the-agent-proxy-relay-are-now-deferred-beh","heading":"Agent proxy relay's startup checks moved to a separate step","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/startup-checks-of-the-agent-proxy-relay-are-now-deferred-beh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Agent proxy relay's startup checks moved to a separate step\n\nThe agent proxy relay no longer runs its reachability check as it starts; the checks are now a separate step\n\n**Unclear.** Whether anything in Claude Code now runs the separate startup checks is not known.\n\n**What**\n\nThe agent proxy relay used to check, as it started, that it could be reached and that its connection was working, when its startup check option was set. Those checks no longer run as part of starting the relay. They are now a separate step that has to be called on its own.\n\n**Why**\n\nIf nothing runs that separate step, the startup reachability check, which logs a line such as \"startup reachability probe: ok\", will no longer happen.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}