during the update this shows up.. when when i continue its gets stuck not find the gateway .. ?

[Interstellar-code]

sreeharsha@interstellarconsulting.com added a feedback(#7843967) from http://localhost:3000/chat/new
> during the update this shows up.. when when i continue its gets stuck not find the gateway .. ?

Session details:
- Feedback ID: #7843967
- Browser: Firefox 151.0 (unknown)
- Rating: N/A
- Window Size: 1536 x 748
- Resolution: 768 x 432
- DPI: 2.5
- Colour Depth: 24-bit
- Category: N/A

Session Replay:
https://app.userback.io/viewer/3431/143039/7843967H5p5mFCgrP74q2x4VjWR4HXXm4hW9q876HWRJp/?sr=1

Console logs:
<br>%cReact Grab v0.1.44%c<br>https://react-grab.com background: #330039; color: #ffffff; border: 1px solid #d75fcb; padding: 4px 4px 4px 24px; border-radius: 4px; background-image: url("data:image/svg+xml;b...<br>[tap-debug:chat-main] toggle via overlay or window.toggleChatTapDebug() <br>[tap-debug:chat-main] toggle via overlay or window.toggleChatTapDebug() <br>


---
View feedback details in Userback:
https://app.userback.io/viewer/3431/143039/7843967H5p5mFCgrP74q2x4VjWR4HXXm4hW9q876HWRJp/

[Interstellar-code]

Same root cause as #200 — fixed in v2.3.30 (commit 74bb80fc).

The post-update "stuck, can't find the gateway" state was the binary-name mismatch: the updater installs the gateway as hermes, but the old code only looked for a claude binary, so the agent never started and the onboarding flow could not advance. v2.3.30 makes resolveClaudeBinary() find hermes (and resolves a custom gateway port/URL instead of assuming 8642), so the gateway starts and the connection succeeds.

One follow-up noted for transparency: startClaudeAgent() still returns ok:true with a "starting" message even if the health probe never passes — a separate hardening item, tracked for a later patch. With the binary now found, the gateway does come up and the stuck state clears.

Please update to v2.3.30+ and reopen if it persists.