Skip to content

spike(ship): Bundle Node runtime + pinned ACP adapters for self-contained Claude/Codex/Pi #928

Closed as not planned

Description

@cursor

Question

Should ai-buddy ship a Node runtime + pinned adapter trees for Claude/Codex/Pi to eliminate the external Node dependency, or is "install Node" + loud error (#831) the acceptable compromise for V1?

Why now

#735 census identified Node+npx as the only remaining silent external dep (now loud after #831). Three of seven named presets need it. Bundling would make those three self-contained.

Scope

In

  1. Size/license table — Node runtime + node_modules for @agentclientprotocol/claude-agent-acp, codex-acp, pi-acp. Measure compressed and on-disk. License compatibility (MIT adapters + Node.js license).
  2. Update cadence — Adapter versions currently track @latest via npx. Bundled pins become our update responsibility. Frequency? Manual or automated bump?
  3. Distribution impact — Binary size increase per platform. Download size. Install size.
  4. Alternative: offline node_modules — Ship adapter trees, still require user-installed Node. Smaller than full Node bundle, still eliminates network/npx cold start.
  5. Recommendation — Keep external (declare Node), bundle Node+adapters, or bundle adapters-only. Decision input for V1.

Out

  • Implementing the bundling in this issue (follow-up if decision is "bundle").
  • Other harness CLIs (separate per-preset decisions; not Node-dependent).

Done when

  • Size table: Node runtime + 3 adapter trees, compressed and on-disk, per platform (macOS aarch64/x86_64, Linux x86_64, Windows x86_64).
  • License table: Node.js license, adapter licenses, compatibility with ai-buddy MIT.
  • Update cadence analysis: how often adapters publish, manual vs automated bump strategy.
  • Comparison: (a) status quo (declare Node), (b) bundle Node+adapters, (c) bundle adapters-only + require Node.
  • Recommendation with rationale. Decision point for Oded/product.

Related

Decision (2026-09-23)

Not planned for V1. Oded on #932: do not bundle Node; declare + graceful fail + README. Follow-ups: #929, #930, #948, #949, #950.

— Cursor agent (Architect), on @omesser's behalf.

Activity

  1. added this to the V1 milestone on Sep 23, 2026
  2. moved this from Todo to Done in Fidgeton Sep 23, 2026
  3. omesser commented on Sep 29, 2026

    @omesser
    Owner

    Research evidence later landed (spike stays not planned)

    #1147 merged to main (2a36804). Measured note: docs/research/harness-without-npx.md.

    What that covers from this spike's Done-when (evidence only; no bundling shipped):

    • Size / cold-warm npx costs for the three adapters, plus sidecar Node / SEA / Bun / Deno paths
    • Licenses and supply-chain notes
    • Update cadence (@latest churn)
    • Comparison of declare / pin-and-run-with-node / bundle runtime / compile alternatives
    • Recommendation: keep ADR-0035 (declare Node); optionally replace npx with a Fidget-managed pin

    V1 product call on #1147 (owner): still not bundling Node/npx and not pinning adapters — keep declaring. UX follow-ups already filed: #1160 (cold first-run timeouts), #1161 (Chat during init), #1162 (launcher version probe).

    Leaving this issue closed as not planned (bundling remains out for V1). No reopen.

    — Cursor agent (Coder), on @omesser's behalf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    • Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions