[Feature Request] Have you considered adding ACP support?

[CoutinhoTTS]

Context

Hi! I was wondering if you’ve considered adding support for ACP (Agent Client Protocol).

I previously brought up a similar idea in Vue DevTools, so I wanted to share the discussion here as well:

vuejs/devtools#1133

I think ACP could be a nice way to make it easier to integrate with different coding agents.

Would love to hear your thoughts!

[antfu]

Oh yeah! That's something in my mind but I haven't started it. Would you like to try to build it with Devframe so we can see what we can do on Devframe to make it easier to support?

for example, in the a11y devtools, we have the feature to select a11y violations and an auto-generated context prompt for agents to fix the. Right now, it requires users to copy and paste it into their own agent; once this is implemented, it could be a one-click "send to agent" when the service exists.

[clanzhang]

Hi! I'd like to take a stab at this. Here's my understanding and proposed approach — would appreciate feedback before opening a PR.

Context

Devframe already exposes its API surface to coding agents over MCP via @devframes/agentic. ACP complements this by standardizing the editor ↔ agent communication layer. The key difference:

• MCP (already implemented): agent discovers and calls Devframe tools
• ACP (proposed): Devframe UI initiates conversations with the user's coding agent, attaching runtime context

Proposed approach

I see two phases:

Phase 1: ACP client adapter in @devframes/agentic

A new src/acp/ module that:

• Implements the ACP client role (JSON-RPC over stdio for local agents, HTTP for remote)
• Handles initialize, session/new, session/prompt lifecycle
• Exposes a high-level API like ctx.agent.sendToAgent({ prompt, context }) that plugins can call
• Reuses MCP types where possible (ACP is MCP-friendly by design)

Phase 2: a11y plugin integration (the concrete use case)

In the a11y plugin, when violations are selected:

• Generate the context prompt (already partially done today)
• Instead of copy-paste, offer a "Send to agent" button
• The button calls the ACP client to start a session with the attached context (selected violations, component info, suggested fixes)

Questions

1. Should the ACP client live in @devframes/agentic alongside the existing MCP server, or as a separate package (e.g. @devframes/acp)?
2. For transport: start with stdio only, or also sketch HTTP from the beginning?
3. Should Devframe also expose itself as an ACP-compatible agent (so editors can discover Devframe tools via ACP session setup), or is the client role sufficient for now?

Happy to start with Phase 1 as a draft PR if the direction looks right.

[antfu]

@clanzhang please don't let the LLM speaks to you.

[CoutinhoTTS]

Devframe

OK. I'm more than willing to give it a try.
A few days ago, I explored the functions of devtools + acp. In the future, I will try to contribute to Devframe.

[clanzhang]

@clanzhang please don't let the LLM speaks to you.

oh

[clanzhang]

@clanzhang please don't let the LLM speaks to you.

@antfu 我想做两件事:

1. 在 @devframes/agentic 里加 src/acp/，实现 ACP client。本地 agent 走 stdio，远程走 HTTP。处理 initialize、session/new、session/prompt 生命周期。给插件暴露 ctx.agent.sendToAgent({ prompt, context })。类型尽量复用 MCP 的。

2. a11y 插件接入：选中违规项后加"发给 agent"按钮，替代手动复制粘贴。按钮起一个 ACP session，把选中的违规项、组件信息和修复建议带上。
   想确认几点：

3. ACP client 放 @devframes/agentic 里还是单独拆包？

4. transport 先只做 stdio 还是 HTTP 也先搭个架子？

5. Devframe 要不要也作为 ACP agent 暴露出去，还是先只做 client？
   方向 OK 的话我先从第一步开始写 draft PR。

[antfu]

Since it would be shipped with some ui, I think it would be a better fit as a composable devframe (like how the terminals plugin works), so the users can opt in to it. And plugins like a11y can detect if the ACP plugin is installed to conditionally show the icon

[clanzhang]

Since it would be shipped with some ui, I think it would be a better fit as a composable devframe (like how the terminals plugin works), so the users can opt in to it. And plugins like a11y can detect if the ACP plugin is installed to conditionally show the icon

做成 composable devframe 确实更合适，用户自己决定要不要装。我去看 terminals plugin 的实现，照着那个模式来。