{"version":"2.1.290","anchor":"gh-path-probe-now-has-a-timeout-and-failure-path","canonical_anchor":"gh-path-probe-now-has-a-timeout-and-failure-path","heading":"GitHub CLI setup no longer stalls when looking for gh fails","tier":"notice","area":"GitHub","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/gh-path-probe-now-has-a-timeout-and-failure-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### GitHub CLI setup no longer stalls when looking for `gh` fails\n\nIf finding the gh command times out or fails during setup, Claude Code skips its gh stand-in and carries on, except in hosted runs\n\n**What**\n\nIn some setups Claude Code places a small stand-in, called a shim, in front of `gh`, the GitHub command-line tool. To do that it first looks up where `gh` lives on your system. That lookup used to be a single timed attempt. It now reports whether it timed out or failed outright.\n\n- If the lookup times out or fails, Claude Code skips the stand-in and continues.\n\n- When running hosted, a failure stops with an error instead.\n\n**Why**\n\nStarting the agent proxy, the part that routes this traffic, holds up better when the lookup for `gh` misbehaves.\n\n- Area: GitHub\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}