[Feature Request] Official ACP (Agent Client Protocol) Support & Native Client Bridge in ZCode

Problem Statement & User Demand

Multiple developers in the community (Discord Thread) are seeking to integrate ACP-compatible agent runners, subagent orchestrators, and external clients (such as Codex Sub and community ACP runners) directly with ZCode and the GLM Coding ecosystem.

Currently, community members have attempted to use unofficial reverse-engineered wrappers (such as william0wang/zcode-acp), but these repeatedly break and fail due to Cloudflare anti-bot challenges / CAPTCHA requirements on web endpoints.

Context

• While ZCode provides robust native support for MCP (Model Context Protocol) under Settings -> MCP for extending tools, there is currently no native interface for ACP (Agent Client Protocol).
• Users want to connect external agent harnesses directly to ZCode without maintaining fragile reverse-engineered web scrapers.

Proposed Feature / Solution

1. Native ACP Support in ZCode: Provide first-class, built-in ACP protocol support or an official ACP bridge inside ZCode Desktop.
2. Authenticated Daemon / IPC Bridge: Allow external ACP clients to communicate with ZCode via an authenticated local socket / daemon using official OAuth or API key credentials, bypassing web CAPTCHAs entirely.
3. Seamless Multi-Client Interop: Enable users to drive ZCode workflows from external terminals, subagent controllers, and ACP-compliant tooling.

Reference

• Community Discord Thread: ZCode ACP Discussion
• Requested by: Community members @خالد and @1antares1

Regards,
Roman M.

• Contributor / Ambassador at Z.ai
• The Vibe Coder's Blog on Telegram: https://t.me/VibeCodePrompterSystem

No implementation files or tests are named. Start by reviewing ZCode Desktop’s existing MCP support and the ACP protocol requirements, then define the authenticated local bridge and credential flow. Done means external ACP clients can securely drive ZCode through an official native interface without web CAPTCHA workarounds.