Skip to content

Add claude-agent-acp to ai-clis feature#60

Draft
Copilot wants to merge 4 commits into
mainfrom
copilot/add-claude-agent-acp
Draft

Add claude-agent-acp to ai-clis feature#60
Copilot wants to merge 4 commits into
mainfrom
copilot/add-claude-agent-acp

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 9, 2026

  • Investigate previous failing CI runs and initial fixes
  • Inspect the latest remaining failing workflow/job logs for this PR
  • Reproduce or validate the remaining failure locally where possible
  • Apply the smallest fix needed for the remaining failure
  • Run targeted validation, code review, and security checks
Original prompt

This section details on the original issue you should resolve

<issue_title>Add claude-agent-acp to ai-clis</issue_title>
<issue_description>This can be installed via: npm install -g @zed-industries/claude-agent-acp

It should follow the same install/omit semantics as the other items in this feature.</issue_description>

Comments on the Issue (you are @copilot in this section)


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: pofallon <505519+pofallon@users.noreply.github.com>
Copilot AI changed the title [WIP] Add claude-agent-acp to ai-clis Add claude-agent-acp to ai-clis feature Mar 9, 2026
@pofallon
Copy link
Copy Markdown
Contributor

@copilot all of our tests are failing. Review and fix the issues.

Co-authored-by: pofallon <505519+pofallon@users.noreply.github.com>
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Mar 12, 2026

@copilot all of our tests are failing. Review and fix the issues.

Fixed in b2fdf98. I switched OpenCode to npm install -g opencode-ai so the opencode binary is installed on PATH, updated the ai-clis README to include Claude Agent ACP, and fixed the validate workflow to use ./src as the feature base path.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • astral.sh
    • Triggering command: /usr/bin/curl curl -LsSf REDACTED (dns block)
  • claude.ai
    • Triggering command: /usr/bin/curl curl -fsSL REDACTED git conf�� unset 3324681236 ocker credential.userndocker (dns block)
  • containers.dev
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/c5e74fa377e9cf23/node_modules/.bin/devcontainer features test --features ai-clis --skip-autogenerated . (dns block)
  • eastus.data.mcr.microsoft.com
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/c5e74fa377e9cf23/node_modules/.bin/devcontainer features test --features ai-clis --skip-autogenerated . (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/c5e74fa377e9cf23/node_modules/.bin/devcontainer features test --features ai-clis --base-image mcr.microsoft.com/devcontainers/javascript-node:22 . (dns block)
  • https://api.github.com/repos/nvm-sh/nvm/releases/latest
    • Triggering command: /usr/bin/curl curl -s REDACTED vsc-1773324554569-d870033eba9f66287e71ed50509010c4886d5766134ddab834ecf0543b0c269a-features (http block)
    • Triggering command: /usr/bin/curl curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

@pofallon
Copy link
Copy Markdown
Contributor

@copilot investigate our remaining build failure

Co-authored-by: pofallon <505519+pofallon@users.noreply.github.com>
Copy link
Copy Markdown
Contributor Author

Copilot AI commented Mar 13, 2026

@copilot investigate our remaining build failure

Investigated and fixed in 4a2eb66. The remaining failing check was test-global, and its logs showed the failure was in the upstream ghcr.io/devcontainers/features/node install during the global composition test, not in ai-clis. I updated the global scenario to use mcr.microsoft.com/devcontainers/javascript-node:22 as the base image and removed the explicit Node feature from that scenario so the smoke test still has Node available without hitting that failing install path.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • astral.sh
    • Triggering command: /usr/bin/curl curl -LsSf REDACTED (dns block)
  • claude.ai
    • Triggering command: /usr/bin/curl curl -fsSL REDACTED (dns block)
  • containers.dev
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/c5e74fa377e9cf23/node_modules/.bin/devcontainer features test --global-scenarios-only . (dns block)
  • westus.data.mcr.microsoft.com
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/.npm/_npx/c5e74fa377e9cf23/node_modules/.bin/devcontainer features test --global-scenarios-only . (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot AI requested a review from pofallon March 13, 2026 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add claude-agent-acp to ai-clis

2 participants