feat(staged): replace bundled ACP bridges with app-managed Node runtime and floating npm installs

.github/workflows/staged-release.yml

@@ -79,10 +79,6 @@ jobs:
           STAGED_UPDATER_ENDPOINT: https://github.com/${{ github.repository }}/releases/download/staged-latest/latest.json
         run: pnpm run tauri:release:config
 
-      - name: Stage bundled ACP tools
-        working-directory: apps/staged
-        run: ./scripts/prepare-acp-tools-resource.sh "$TAURI_TARGET"
-
       - name: Build unsigned Tauri app
         working-directory: apps/staged
         env:

.gitignore

@@ -2,9 +2,3 @@ target/
 .DS_Store
 .hermit
 node_modules/
-
-# Staged bundled ACP bridge tools (regenerated by apps/staged/scripts/prepare-acp-tools-resource.sh)
-apps/staged/src-tauri/resources/acp/bin/*
-!apps/staged/src-tauri/resources/acp/bin/.gitkeep
-apps/staged/src-tauri/resources/acp/node/
-apps/staged/src-tauri/resources/acp/node-runtime.json

apps/staged/README.md

@@ -64,15 +64,19 @@ If you installed manually (not via the install script), copy `scripts/staged` to
 
 ### AI Agent Setup (ACP)
 
-Staged discovers ACP providers by CLI command name. For Claude Code ACP:
-
-```bash
-npm install -g @zed-industries/claude-agent-acp
-```
-
-This package installs the `claude-agent-acp` executable.
-
-After installing, open Staged and run **Settings -> Doctor** to verify the Claude check is detected as installed.
+Staged manages the Claude Code and Codex ACP bridges itself: on every launch
+it installs (or upgrades) them into `~/.staged/packages` on a Staged-managed
+Node.js runtime, so no host Node or manual `npm install` is needed. The first
+launch downloads them, which requires network access; after that they work
+offline. Other agents (Goose, Pi, copilot, amp) are discovered by CLI command
+name on your PATH, and **Settings -> Doctor** can install the npm-based ones
+into the same Staged-private prefix.
+
+Open **Settings -> Doctor** to verify agent checks are detected as installed.
+
+To develop against a local bridge checkout, export `STAGED_ACP_TOOLS_DIR`
+pointing at a directory with the bridge binaries — this disables the managed
+installs and resolves bridges from that directory instead.
 
 ## Development
 

apps/staged/justfile

@@ -9,7 +9,6 @@
 install:
     pnpm install
     cd src-tauri && cargo fetch
-    ./scripts/ensure-acp-tools.sh
 
 # ============================================================================
 # Development
@@ -23,11 +22,10 @@ dev repo="":
     # Install JS deps if needed
     [[ -d node_modules ]] || pnpm install
 
-    # Stage the pinned ACP bridge tools and point the app at the staged dir so
-    # dev builds resolve the same bundled bridges as packaged builds.
-    ./scripts/prepare-acp-tools-resource.sh
-    export STAGED_ACP_TOOLS_DIR="$(pwd)/src-tauri/resources/acp/bin"
-    echo "Using ACP tools dir: ${STAGED_ACP_TOOLS_DIR}"
+    # Dev instances share the managed ACP bridges and Node runtime in
+    # ~/.staged/packages with every other Staged instance. Export
+    # STAGED_ACP_TOOLS_DIR manually to point sessions at a local bridge
+    # checkout instead (it disables the managed installs).
 
     # Derive a stable port from the working directory so the same worktree
     # always gets the same port. This avoids changing TAURI_CONFIG between
@@ -62,7 +60,6 @@ dev repo="":
 
 # Build the app for production
 build:
-    ./scripts/prepare-acp-tools-resource.sh
     pnpm run tauri:build
 
 # Generate the release-only Tauri config with updater settings
@@ -71,7 +68,6 @@ release-config:
 
 # Build a signed/notarized release bundle once release config exists
 release-build target="aarch64-apple-darwin" *args:
-    ./scripts/prepare-acp-tools-resource.sh {{target}}
     pnpm exec tauri build --target {{target}} --config src-tauri/tauri.release.conf.json {{args}}
 
 # Create a release branch, bump staged versions, and open a release PR
@@ -137,9 +133,9 @@ release version:
 
     echo "Pushed tag staged/v{{version}} — CI will build and publish the release."
 
-# Update acp-tools.lock.json to the newest npm releases of the bundled ACP bridge tools that have aged past the 50h cooling-off window
-bump-acp-tools *ARGS:
-    node scripts/update-acp-tools-lock.mjs {{ ARGS }}
+# Fetch official Node.js release checksums and update node-runtime.lock.json (e.g. `just bump-node-runtime v24.12.0`)
+bump-node-runtime *ARGS:
+    node scripts/update-node-runtime-lock.mjs {{ ARGS }}
 
 # ============================================================================
 # Code Quality