Just a few days ago, OpenClaw received a significant update.
OpenClaw 2026.2.26 Update Highlights:
- ACP Agents as first-class runtimes
- Android support
- Major security fixes
The big news is that OpenClaw has elevated ACP Agents to first-class runtimes. This means OpenClaw can now function as an ACP Client, connecting to any ACP Agent.
Interestingly, this capability isn't entirely new. Back in January, OpenClaw itself could already act as an ACP Agent, allowing it to be connected by any other ACP Client.
Today, I had a thought: wouldn't it be even more convenient to connect to OpenClaw directly from VS Code?
So, I immediately updated my VS Code ACP Client extension to add support for OpenClaw!
Important Compatibility Note
The latest version of OpenClaw as an ACP Agent seems to have some bugs. I found that using OpenClaw v2026.1.30 works flawlessly, with smooth, responsive operation.
npm i -g openclaw@2026.1.30
Setup
To make OpenClaw run in VS Code, you need to run openclaw onboard in your terminal to setup the OpenClaw.
More details: https://docs.openclaw.ai/start/onboarding-overview
Supported Agents
The ACP Client extension currently supports nine major Agents by default:
- GitHub Copilot
- Claude Code
- Gemini CLI
- Qwen Code
- OpenCode
- Codex CLI
- Qoder CLI
- Auggie CLI
- OpenClaw
You can also configure it to connect to additional ACP Agents.
Open Source
Both my two projects are fully open source:
- VS Code ACP Client Extension: GitHub Link
- ACP UI: GitHub Link
Give it a try and let me know your experience! The integration brings us one step closer to seamless AI assistant workflows within our development environment.
Top comments (0)