Adom Hydrogen (platform base)

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.62",+  "version": "0.5.63",   "description": "Hydrogen's PLATFORM-GENERIC workspace layer on top of adom/core. Installs adom/core for the full Adom ecosystem, then adds everything common to running inside Hydrogen on ANY platform: the runtime-neutral hydrogen-* skills and the generic editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hydrogen-windows-bootstrap (WSL2), adom/hydrogen-mac-bootstrap, adom/hydrogen-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "tags": [

@@ -4,7 +4,7 @@   "type": "bootstrap",   "title": "Adom Hydrogen (platform base)",   "brief": "Layer Hydrogen's workspace onto a standard Adom workstation.",-  "version": "0.5.62",+  "version": "0.5.63",   "description": "Hydrogen's PLATFORM-GENERIC workspace layer on top of adom/core. Installs adom/core for the full Adom ecosystem, then adds everything common to running inside Hydrogen on ANY platform: the runtime-neutral hydrogen-* skills and the generic editor configuration (Claude Code CLI + extension, VS Code settings, trusted domains). Platform-specific layers depend on THIS: adom/hydrogen-windows-bootstrap (WSL2), adom/hydrogen-mac-bootstrap, adom/hydrogen-ubuntu-bootstrap. The reference design other orgs copy to build their own bootstrap on adom/core.",   "org": "adom",   "tags": [

@@ -78,12 +78,20 @@ Each Provider has an `oracle_cmd`, a shell command run in the container whose st   failure). Right after an update relaunch the exec route settles for a few seconds; the   first cut read every AI as absent and raised the first-landing dialog on a signed-in box. -`shared_auth` on the Provider says whether the extension and the CLI read one credential-store (claude, codex, kimi: true; antigravity: false). `ext_separate_signin` marks the AIs-whose extension signs in on its own (antigravity, kimi as a fallback). Hydrogen cannot read-the Antigravity extension's login (it lives in VS Code's browser-side global storage under-`google.google-antigravity`, only `lastLoginUsername`, tokens in secret storage), so the-dialog says "extension: own sign-in" rather than guessing.+`shared_auth` on the Provider says whether one sign-in covers the extension and the CLI.+Claude, Codex and Kimi share a credential store. Antigravity does not, but Hydrogen makes it+shared: the extension's agy server keeps its Google login in+`~/.gemini/jetski-standalone-oauth-token` and the CLI in+`~/.gemini/antigravity-cli/antigravity-oauth-token`, both for the SAME OAuth client+(identical `aud` in the id_token, VERIFIED 2026-09-20) in the same JSON shape. The oracle+reads both and copies whichever exists to the missing side (mode 600), so a panel sign-in+signs the CLI in and a CLI sign-in signs the extension in. One limit, measured: the panel's+webview keeps its Welcome screen until the window reloads (restarting the agy server or+re-opening the side bar does not refresh it), so after a CLI-side sign-in the dialog offers+"Reload VS Code now". `shared_auth_note` carries that explanation into the tooltip.+`ext_separate_signin` still marks Antigravity so the dialog's primary Sign in opens the panel+(extension first). Sign-out removes both token files. Before this, Hydrogen ignored the+extension's file and showed "Sign in" over a signed-in panel (John, 2026-09-20).  ## Sign-in: driving it for the user 

@@ -30,7 +30,7 @@ tell the user to open Hydrogen rather than improvising an install. | `claude` | Claude Code | anthropic.claude-code (baked into the golden image) | `claude`, a wrapper onto the extension's bundled binary | yes, `~/.claude/.credentials.json` | | `codex` | Codex | openai.chatgpt (baked in) | `codex`, a wrapper onto the extension's bundled binary | yes, `~/.codex/auth.json` | | `kimi` | Kimi Code | moonshot-ai.kimi-code (user installs) | `kimi` 2.x, standalone (the extension ships no CLI) | yes, `~/.kimi-code/credentials` |-| `antigravity` | Antigravity | google.google-antigravity (user installs) | `agy`, the copy the extension downloads to `~/.gemini/bin/agy` | NO: the extension signs in inside its own panel, the CLI in a terminal |+| `antigravity` | Antigravity | google.google-antigravity (user installs) | `agy`, the copy the extension downloads to `~/.gemini/bin/agy` | yes, by Hydrogen: it copies the Google token between `~/.gemini/jetski-standalone-oauth-token` (extension) and `~/.gemini/antigravity-cli/antigravity-oauth-token` (CLI) |  `grok` is listed as coming soon and has no install or sign-in yet. @@ -79,9 +79,13 @@ few seconds; the human has minutes, not seconds, to click through Google or Open   in the catalog, then start the sign-in. Say what got installed: the extension and the CLI. - **Sign-in for claude, codex, kimi**: one sign-in covers the extension and the CLI. Give the URL   as a link. For Codex give the device code too.-- **Sign-in for antigravity**: say plainly that the extension and the CLI sign in separately.-  Open the panel for the extension; run `/agents/login` for the CLI. The CLI flow ends on a-  page that shows a code; ask them to paste it and send it with `/agents/login-input`.+- **Sign-in for antigravity**: either side works and Hydrogen syncs the token to the other+  within seconds. Prefer the panel (`/agents/open-panel`): the user clicks Continue with Google+  there and the CLI is signed in right after. The CLI flow (`/agents/login`) ends on a page+  that shows a code; ask them to paste it and send it with `/agents/login-input`. After a+  CLI-side sign-in the VS Code panel keeps its Welcome screen until the window reloads; the+  dialog offers "Reload VS Code now", or call `POST $HD/reload-vscode?confirm=1` (it hard+  reloads the editor; ask first if the user may have unsaved editor state). - **Kimi region**: Kimi's installer defaults to mainland China (kimi.com, WeChat). Hydrogen's   install writes `global` into `~/.kimi-code/region` so sign-in goes to kimi.ai. If a user   lands on a WeChat page, that file is wrong.