[Bug]: Failed to start Claude Code ACP: spawn claude-code-acp ENOENT

[gultyayev]

Prerequisites

• I have searched existing issues to avoid duplicates
• I am using the latest version of CodeMie CLI
• I have read the documentation

Bug Description

I followed the documentation for setup & ACP configuration in JetBrains IDE. However, it looks like ACP wrapper is broken or missing something.

Steps to Reproduce

1. Install codemie cli
2. Have latest claude code installed
3. Try adding ACP to WebStorm, or just run codemie-claude-acp

Expected Behavior

It should work

Actual Behavior

Failed to initialize ACP process. Process terminated with exit code: 1. Process output:

✗ Failed to run Claude Code ACP

Failed to start Claude Code ACP: spawn claude-code-acp ENOENT

CodeMie CLI Version

0.0.40

Which agent are you using?

Claude Code (codemie-claude)

Which provider are you using?

Not applicable

Model

No response

Node.js Version

v24.13.1

Operating System

macOS

Configuration (Redacted)

{
  "version": 2,
  "activeProfile": "default",
  "profiles": {
    "default": {
      "provider": "ai-run-sso",
      "codeMieUrl": "https://codemie.lab.epam.com",
      "codeMieProject": "<redacted>",
      "apiKey": "sso-provided",
      "baseUrl": "https://codemie.lab.epam.com/code-assistant-api",
      "model": "gpt-5-2-2025-12-11",
      "haikuModel": "claude-haiku-4-5-20251001",
      "sonnetModel": "gpt-5-2-2025-12-11",
      "opusModel": "claude-opus-4-6-20260205",
      "name": "default"
    }
  }
}

Error Logs

Additional Context

doctor only "complains" about optional AWS CLI missing. Output excerpt

Installed Agents:
✓ CodeMie Native (v0.0.40 (built-in))
✓ Claude Code (2.1.41)
✓ Claude Code ACP
✓ Gemini CLI (0.28.2)

$ codemie install claude-acp
Claude Code ACP is already installed

[8nevil8]

🔍 Triage Analysis

Root Cause: The claude-code-acp binary from @zed-industries/claude-code-acp npm package is not found in PATH after installation.

Technical Details:

1. Execution Flow:

   • User runs codemie-claude-acp wrapper → bin/codemie-claude-acp.js
   • Wrapper loads claude-acp plugin from registry → src/agents/plugins/claude/claude-acp.plugin.ts
   • Plugin's run() method tries to spawn claude-code-acp command → src/agents/core/BaseAgentAdapter.ts:370-374
   • Spawn fails with ENOENT (file not found)

2. Installation Logic (src/agents/plugins/claude/claude-acp.plugin.ts:71-76):

   • Uses BaseAgentAdapter.prototype.install.call(this)
   • Installs via npm.installGlobal('@zed-industries/claude-code-acp')
   • However, the binary may not be properly linked or accessible in PATH

3. Possible Issues:

   • npm global installation doesn't create the claude-code-acp symlink correctly
   • The binary from @zed-industries/claude-code-acp package might not be executable
   • PATH resolution logic in BaseAgentAdapter.run() doesn't find the binary in npm's global bin directory
   • The package may not have a bin field in its package.json

Files Involved:

• src/agents/plugins/claude/claude-acp.plugin.ts (plugin metadata & install logic)
• bin/codemie-claude-acp.js (wrapper entry point)
• src/agents/core/BaseAgentAdapter.ts (command resolution & spawn logic)

Affected Users: Anyone trying to use Claude Code ACP for IDE integration (Zed, WebStorm, etc.)

Priority: High - Blocks core ACP functionality

---

@homich1991 Assigning to you as the primary author of the ACP plugin functionality (PR #127).

Recommended Investigation:

1. Check if @zed-industries/claude-code-acp package properly exports the binary
2. Verify npm global installation creates the symlink: npm list -g @zed-industries/claude-code-acp
3. Check if the binary is in npm's global bin directory: npm bin -g
4. Consider using npx claude-code-acp instead of spawning the binary directly
5. Add fallback logic to try npx if direct command resolution fails

[8nevil8]

Note: Unable to auto-assign to @homich1991 (Roman Meerson) as they're not a repository collaborator. The issue should be manually assigned or Roman should be added as a collaborator first.

Alternative: Can assign to @narach (Siarhei) who contributed to the ACP wrapper binary.

[8nevil8]

📝 Author Correction

After reviewing the full git history:

Original Author: @narach (Siarhei Belavus, siarhei-belavus@users.noreply.github.com)

• PR feat(agents): add Claude Code ACP plugin for IDE integration #111 (Jan 30, 2026): Created the entire Claude Code ACP plugin
  • Added src/agents/plugins/claude/claude-acp.plugin.ts (73 lines)
  • Added bin/codemie-claude-acp.js wrapper
  • Implemented session analytics, silent mode, post-install hints
  • Full IDE integration support

Later Contributor: @homich1991 (Roman Meerson)

• PR fix(agents): use BaseAgentAdapter for claude-acp to support npm-only … #127 (Feb 4, 2026): Fixed installation bug
  • Overrode install() method to use npm-only installation (BaseAgentAdapter)
  • Fixed issue where ClaudeAcpPlugin inherited native installation from ClaudePlugin

---

Recommendation: Assign to @narach (Siarhei) as the original author and primary architect of the ACP plugin. However, @homich1991's installation fix in PR #127 is directly related to this bug, so his input would be valuable.

The current issue (spawn ENOENT) appears to be related to the command resolution logic after npm installation, which falls under the installation flow that both authors worked on.