<p align="center" <img src="packages/web/src/app/icon.svg" width="88" alt="AgentConnect logo" / </p
<h1 align="center"AgentConnect</h1
<p align="center" <strongRun AI coding agents where your code and credentials live, then connect them everywhere your team works.</strong </p
<p align="center" <a href="https://github.com/agentconnect-md/agentconnect/actions/workflows/test.yaml"<img src="https://github.com/agentconnect-md/agentconnect/actions/workflows/test.yaml/badge.svg" alt="Test status" /</a <a href="https://www.npmjs.com/package/@agentconnect.md/daemon/v/latest"<img src="https://img.shields.io/npm/v/%40agentconnect.md%2Fdaemon/latest?label=daemon%20latest" alt="Latest daemon version" /</a <a href="https://www.npmjs.com/package/@agentconnect.md/daemon/v/rc"<img src="https://img.shields.io/npm/v/%40agentconnect.md%2Fdaemon/rc?label=daemon%20rc" alt="RC daemon version" /</a <a href="LICENSE"<img src="https://img.shields.io/badge/license-Apache--2.0-blue.svg" alt="Apache 2.0 license" /</a </p
<p align="center" <a href="#why-agentconnect"Why AgentConnect?</a · <a href="#get-started"Get started</a · <a href="#architecture"Architecture</a · <a href="#explore"Explore</a </p
AgentConnect is an open-source, daemon-centric platform for operating AI coding agents across your own infrastructure. Claude, Codex, and other ACP-compatible runtimes can participate in Slack, Telegram, Discord, Feishu, webchat, GitHub events, webhooks, and scheduled tasks.
The execution daemon stays beside the agent and its workspace. The Control Plane coordinates the fleet but never handles the live message path, so established sessions keep running when it is temporarily unavailable.
Why AgentConnect?
Built for teams that want a shared agent platform without moving execution or workspace access into a hosted runtime:
- Keep execution local. Workspaces, agent processes, direct platform
connections, and model-provider traffic stay on daemon hosts you control. Public callback ingress terminates on the optional relay you operate.
- Operate agents as a fleet. Configure runtimes, workspaces, integrations,
secrets, schedules, and sessions from one Web console.
- Preserve data boundaries. The Control Plane stores orchestration metadata,
not message bodies, attachment bytes, or ACP session streams.
- Connect the tools you already use. Bring agents into chat, webchat, GitHub
events, generic webhooks, and scheduled workflows.
- Choose the right memory model. Use managed, native, external, or disabled