diff --git a/docs/get-started/clients.mdx b/docs/get-started/clients.mdx
index 9f6e9127c..fd67e1528 100644
--- a/docs/get-started/clients.mdx
+++ b/docs/get-started/clients.mdx
@@ -181,6 +181,7 @@ These connectors bridge ACP into other environments and transport layers:
 - [acp_rpc_bridge](https://github.com/Intellexie/acp_rpc_bridge) — terminal binary that bridges stdio-based agents to HTTP, giving non-network agents network capability; supports ACP and Pi RPC protocols with ACP Streamable HTTP and OpenCode REST API endpoints
 - [ACP to AG-UI](https://github.com/namanrajpal/acp-to-agui) — bridges any ACP agent to web frontends via [AG-UI](https://docs.ag-ui.com) events over SSE; works with CopilotKit, AG-UI HttpAgent, or custom UIs (Web)
 - [AgentRQ](https://github.com/agentrq/acp-gateway) — bridges stdio-based ACP agents to the AgentRQ - Human-in-the-loop task collaboration service using MCP server.
+- [AHP-ACP Gateway](https://github.com/formulahendry/ahp-acp-gateway) — bridges AHP clients to configured ACP agents through a persistent WebSocket host, with model and configuration mapping, replay and reconnect, permission handling, and cross-platform lazy agent startup
 - [Aptove Bridge](https://github.com/aptove/bridge) — bridges stdio-based ACP agents to the Aptove mobile client over WebSocket
 - [ACP Remote](https://github.com/vcoderun/acpkit/tree/main/packages/transports/acpremote) - remote WebSocket transport for ACP agents and clients.
 - [OpenClaw](https://docs.openclaw.ai/cli/acp) — through the [`openclaw acp`](https://docs.openclaw.ai/cli/acp) bridge to an OpenClaw Gateway