adom-vscode

@@ -274,6 +274,8 @@ v1.1.20: /command returns errorCode command_not_found (HTTP 400) with did-you-me  v1.1.21: event-driven tab census + Claude session identity (John 2026-09-03: never poll the iframes again). GET /tabs and the SSE stream GET /tabs/events publish the extension host's own tabGroups census on every change; POST /claude/session-start ingests the Claude SessionStart hook (id + transcript path, before the jsonl is flushed) and GET /claude/sessions lists it; POST /claude/open-session opens an existing conversation by id and confirms the bind (retagging sdk-cli transcripts, which the Claude extension otherwise declines). Capability markers in /health: tabs.list, tabs.events, claude.open-session, claude.session-start, claude.sessions. +v1.1.49: the Codex Sessions side bar carries a muted one-line note at the bottom saying it is an Adom feature (Codex conversations as first-class VS Code tabs); hover or click for the why.+ v1.1.48: the title-bar AI menu paints from the last answer and refreshes behind itself (no wait on the extension host), is capped to the window height, folds the icon checklist and vendor-button toggles behind Customize, shows a Terminal (TUI) row and icon only when that AI's CLI is on PATH (`tui_available`, `cli_path` on /ai/providers), and offers Install rows for the AIs that are not here (`POST /ai/install`). Published to the wiki by `scripts/release-wiki.sh`, which refuses a mis-stamped package.  v1.1.26: AI thread icons in the window title bar (John 2026-09-06), the layout-controls row at the top right. VS Code has no contribution point there, so `browser/ai-titlebar.js` rides workbench.html (written by `adom-vscode install`, back on every reload) and calls this extension over `/proxy/<port>/ai/*`: one icon per INSTALLED AI in the vendor's own colour (Claude Code, Codex, and Kimi or Antigravity when their extension is present), a sparkle menu listing every installed AI plus its TUI (the CLI in a terminal tab), and a VS Code-style checklist of which icons to show (saved as `adom-vscode.aiIcons`; TUIs off by default). A click opens the thread in THIS window's active group (each Hydrogen VS Code tab is its own window and extension host; the script matches its visible tabs against every candidate port's census, so the thread never lands in another window) and moves it back if the AI extension split the editor. GET /ai/providers, POST /ai/new {type, tui?, group?} (a TUI goes through the /terminal/tui registry with the AI Threads panel's icon and colour), POST /ai/icons {icons}, POST /tabs/close {label|kind}. The icons are drawn as a real monaco-toolbar (VS Code's own action-item markup, hover and active styling) with monaco-hover tooltips; the menu glyph is a plus with a dropdown chevron. Also: `extensions install --vsix` and `adom-vscode install` used the remote-cli wrapper, which only works inside a VS Code terminal and reported success while installing nothing; both now use the code-server binary and require its own "successfully installed" line.

@@ -1 +1 @@-1.1.48+1.1.49

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {   "slug": "adom-vscode",-  "version": "1.1.48",+  "version": "1.1.49",   "type": "app",   "description": "CLI + VS Code extension that lets AI assistants and the Hydrogen Desktop frontend drive VS Code from inside an Adom container: open files, live get/set of any setting/theme/font (no reload), native streamed exec, a frontend event queue, container identity (hd/hw), api-key status/inject, extension query/update, modes, paste screenshots, and any VS Code command via a local HTTP API on port 8821 (with port-file fallback discovery).",   "license": "PROPRIETARY",

@@ -4,7 +4,7 @@   "slug": "adom-vscode",   "title": "adom-vscode",   "brief": "Let Claude, Codex and Kimi drive VS Code inside your Adom container",-  "version": "1.1.48",+  "version": "1.1.49",   "license": "PROPRIETARY",   "visibility": "public",   "hero": {@@ -141,4 +141,4 @@     "adom-vscode-extensions",     "adom-vscode-modes"   ]-}\ No newline at end of file+}