app

Adom Hydrogen

Public Made by Adom

by adom

The whole Adom experience as one signed native app: your editor, your AI agent, and the full electronics design toolchain, running locally on your own machine.

Overview Files Skills Discover Packages Releases Dependencies Issues20 Breadcrumbs Pull Requests Activity
Open bug report

Unattended auto-update relaunch ended a running Claude Code turn and changed the active tab

John Lauer · 4d ago

Office PC, Hydrogen auto-update 1.0.644 → 1.0.645 at ~00:35Z on 2026-10-19 (and 1.0.645 → 1.0.648 around 02:30Z).

A Claude Code thread was mid-turn (a long build) in this Hydrogen. The 1.0.645 relaunch:

  • ended the Claude turn (the session's transcript stops at 00:35:34Z, no further writes);
  • brought VS Code back with a Codex panel in front and the Claude tabs not listed by /ai-threads until the tab strip was toggled;
  • also interrupted a full-screen recording in progress.

Nobody was at the PC to consent; the update applied on its own. The 1.0.648 relaunch a couple of hours later did not kill the Claude turn (the session kept writing), so the behaviour is inconsistent.

Asks:

  • Don't relaunch while any AI thread is mid-turn (/ai-threads already knows working.state); defer until idle, or at least until a user clicks.
  • Log why/when the relaunch happened (related #70).
  • After a relaunch, restore the previously active editor tab.

3 Replies

John Lauer · 4d ago

Update, Hydrogen 1.0.650: the office PC has now relaunched for an update three times in about three hours (1.0.645 at 00:35Z, 1.0.648 around 02:15Z, 1.0.650 at 03:29Z). The 03:29Z relaunch cut off the running Claude Code turn mid-command a few minutes later (its transcript stops at 03:34:58Z inside a tool call), and each relaunch brought VS Code back with a Codex panel in front. It also froze a screen recording in progress (adom/adom-bridge#247).

John Lauer · 4d ago

Update: two more unattended relaunches on the same PC: 1.0.651 at 04:23Z and 1.0.652 at 05:18Z (five tonight). The log shows the same pattern each time: an update is staged, then "Applying staged update" about 40 s later with "Check now ignored: a check is already in flight" just before it. The 1.0.652 relaunch also left a Settings window open over the app (#129).

John Lauer · 3d ago

Found the cause, and it was us. The five relaunches (1.0.645 at 00:35Z, 1.0.648, 1.0.650 at 03:29Z, 1.0.651 at 04:23Z, 1.0.652 at 05:18Z) were the release test pushing each new insiders build onto ConfRoomROG: an update check, then POST /updater/install about 40 s later, which is exactly the "check already in flight" then "Applying staged update" pair in the log. Nobody checked whether that PC was in use, and Hydrogen had nothing to refuse it.

Fixed in two places:

  • Process: the release test no longer installs on ConfRoomROG at all; it is a build box shared with real work. Test installs go to winvm and arav-rog only.
  • Hydrogen (commit 8a96b2a5, ships in the next build): POST /updater/install now refuses to relaunch while work is running, and says what: {"ok":false,"deferred":true,"busy":["AI thread mid-turn: claude 43add640", "native recording running (...)"]}. "Mid-turn" means the session's last hook was a prompt or a tool (not Stop) within the last 30 minutes. force:true overrides when the person agreed. Auto update mode waits the same way (checks every minute, up to 12 h). The user's own Restart to update button is never blocked.

Not done yet from your asks: restoring the previously active editor tab after a relaunch. That stays open here.

Log in to reply.