Support ACP (agentic coding protocol)

[versecafe]

What would you like to be added?

The Agentic Coding Protocol currently maintained by the Zed team which is currently supported as an expiremental feature in both the gemini cli and claude code cli.

Why is this needed?

It provides deep editor integrations for viewing and reviewing diffs along with MCP passthrough from the source editor.

Additional context

merged pr for gemini support google-gemini/gemini-cli#4266

looking to help get this off the ground myself if there is interest in the feature from the qwen-code team

[cchance27]

This would be such a nice addition!

[m1ttt]

I was able to make it run by placing this in the agents

[abishekmuthian]

I was able to make it run by placing this in the agents

says "unsupported version" for me.

Edit: Updating to 0.0.9 fixed the issue, thanks.

[trieloff]

I've been running into #384 as one of the tools I have set up in Zed uses search as a tool name. In fact, multiple, which is a problem as search is a very popular tool name and OpenAI required the presence of search and fetch tools for their MCP implementation. So any MCP server that aimed for portability is likely incompatible with Qwen.

Unless there is a way to exclude MCP servers from being shared by Zed, this integration would still need work.

[versecafe]

It seems to work outside of the authentication support where if you are not already authed it is currently only exposing Vertex, Gemini API Key, & Google OAuth from the AuthTypes up through the protocol, this might be resolved with the sync with gemini 0.2.1 PR but it may also require some manual work to connect up remove the invalid google auth options to have a smooth user experience

[Dima-369]

Thanks for the screenshot above. I typed it out, so the next one can just paste this into your settings.json 🙂

"agent_servers": {
  "qwen": {
    "command": "qwen",
    "args": ["--experimental-acp"],
    "env": {}
  }
}

It works great for me on qwen 0.0.11.

[metallerok]

qwen 0.0.14 doesn't work.

Internal error: "server shut down unexpectedly"

[LeOndaz]

Works for me on 0.0.14 with the solution provided by @Dima-369

[wardenxyz]

Thanks for the screenshot above. I typed it out, so the next one can just paste this into your settings.json 🙂

"agent_servers": {
"qwen": {
"command": "qwen",
"args": ["--experimental-acp"],
"env": {}
}
}
It works great for me on qwen 0.0.11.

Zed: v0.208.4 (Zed Preview)
OS: Windows 10.0.26100
Memory: 15.7 GiB
Architecture: x86_64
GPU: Intel(R) Iris(R) Xe Graphics || Intel Corporation || 31.0.101.4502

Hi, I added your configuration to my settings.json, but Zed shows "program not found." Could this be due to using a pre-release version of Zed? Or is there something else I might be missing?

[Dima-369]

Could this be due to using a pre-release version of Zed?

I doubt it, I use custom-builds of main, and did not have such issues before.

Or is there something else I might be missing?

Try out using the absolute path of qwen (use where qwen) in the config, then restarting Zed.

[wardenxyz]

Could this be due to using a pre-release version of Zed?

Sorry, the AI misunderstood me. What I meant was: could this issue be because I'm using a pre-release version of Zed? @Dima-369

I've switched to an absolute path, and Zed no longer shows an error, but it can't send messages. I suspect this might be because Zed for Windows isn't fully stable yet.

[aritradgupta]

I have the same problem here on Windows as @wardenxyz

The hard coded path also doesn't work like above.
qwen-code version: 0.0.14

[wardenxyz]

#963 It’s a bug, fixing