adom-vscode

@@ -1,6 +1,6 @@ --- name: adom-vscode-description: "Control VS Code Server (code-server) from inside the Docker container. THIS is the wrapper for the VS Code FILE EXPLORER sidebar, editor tabs, markdown preview, etc., when the user says 'reveal in file explorer' or 'open in vscode' they mean this CLI, NOT adom-desktop (which controls Chrome browser windows). START-HERE skill of the adom-vscode pack: file ops, workspace scoping, port discovery, and the map to the sub-skills covering live settings (adom-vscode-settings), container exec (adom-vscode-exec), the frontend event queue (adom-vscode-queue), container identity + api key (adom-vscode-container), extension management (adom-vscode-extensions), and modes/layout (adom-vscode-modes). Trigger words: adom-vscode, open in vscode, reveal in explorer, file explorer, sidebar reveal, preview markdown, vscode command, vscode api, port 8821, code-server control, drive vscode, vscode verbs."+description: "Control VS Code Server (code-server) from inside the Docker container. THIS is the wrapper for the VS Code FILE EXPLORER sidebar, editor tabs, markdown preview, etc., when the user says 'reveal in file explorer' or 'open in vscode' they mean this CLI, NOT the bridge CLI (`adom-bridge-cli`, which controls Chrome browser windows). START-HERE skill of the adom-vscode pack: file ops, workspace scoping, port discovery, and the map to the sub-skills covering live settings (adom-vscode-settings), container exec (adom-vscode-exec), the frontend event queue (adom-vscode-queue), container identity + api key (adom-vscode-container), extension management (adom-vscode-extensions), and modes/layout (adom-vscode-modes). Trigger words: adom-vscode, open in vscode, reveal in explorer, file explorer, sidebar reveal, preview markdown, vscode command, vscode api, port 8821, code-server control, drive vscode, vscode verbs." ---  # adom-vscode, VS Code Control (start here)@@ -12,7 +12,7 @@ description: "Control VS Code Server (code-server) from inside the Docker contai > Docker container's running VS Code instance). That's THIS > CLI: `adom-vscode reveal <path>`. >-> **Do NOT** reach for `adom-desktop` for that, `adom-desktop`+> **Do NOT** reach for the bridge CLI (`adom-bridge-cli`) for that — it > controls puppeteer / Chrome browser windows, not VS Code. > > **Do NOT** use the desktop `code` CLI either, it is not on@@ -22,7 +22,7 @@ description: "Control VS Code Server (code-server) from inside the Docker contai > > If the user mentions "vscode", "explorer", or wants to see a > file in the editor, default to `adom-vscode`. Save-> `adom-desktop` for cases where the trigger is clearly Chrome /+> the bridge CLI for cases where the trigger is clearly Chrome / > browser / pup / shotlog tab.  ## The mental model

@@ -1,6 +1,6 @@ {   "slug": "adom-vscode",-  "version": "1.1.21",+  "version": "1.1.22",   "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.21",+  "version": "1.1.22",   "license": "PROPRIETARY",   "visibility": "public",   "hero": {

@@ -20,7 +20,7 @@ Parent skill: **adom-vscode**  Commands run as the workspace user (`adom`) via `bash -lc` inside the container, spawned by the extension host itself. LOGIN shell matters: tools like-adom-desktop need the workspace env from `/etc/profile.d/`, and a bare `-c`+the bridge CLI need the workspace env from `/etc/profile.d/`, and a bare `-c` shell runs them env-less (they fail with nothing on stdout).  ## CLI