agentconnect

AgentConnect is an open-source platform where teams and AI agents work together across the tools they already use, including Slack, Telegram, Discord, and GitHub. Connect Claude Code, Codex, Gemini CLI, or any ACP-compatible runtime, then start work from a conversation, pull request, issue, webhook, or schedule.

Give each agent a role, then choose the runtime, model, workspace, memory, tools, skills, permissions, and sandbox policy it needs. Agents can call one another while your team follows the work in shared channels and from one console.

A small daemon runs the agents in the environment you operate. One console lets your team configure the fleet, connect channels and triggers, control access, and follow the work they are allowed to see.

Why AgentConnect?

AI agents are taking on work across the team, but most still live in individual terminals. AgentConnect brings them into the team's shared workflows:

• Work as one team. Create agents with different roles and let them call on one another, while people follow along in the conversations where the work happens.
• Keep work where it happens. Link agents to bots in Slack, Telegram, and Discord, or to repositories and workflows on GitHub.
• Choose the right agent for every job. Configure each agent's runtime, model, workspace, tools, and machine independently.
• Carry context forward. Give each agent its own memory and skills, and let the team publish reviewed organization knowledge that every agent can find on demand.
• Set clear boundaries. Decide who can see each agent and session, which repositories and tools it may use, and which other agents it may call.
• Stay in control. Self-host the Apache-2.0 stack, run agents in your environment, and change runtimes without locking the team to one vendor.

Get started

Pick the path that matches what you want to do.

Self-host locally

Start the Web console, Control Plane, Relay, and PostgreSQL with Docker Compose:

git clone https://github.com/agentconnect-md/agentconnect.git
cd agentconnect
docker compose up -d --pull always

To build the images from the checkout instead of pulling the published ones, run docker compose up -d --build. Every service in compose.yaml carries a build definition, and the built images take the tags the stack already references.

Open http://localhost:3000. The default stack listens only on 127.0.0.1, uses local no-auth mode, and is intended for local evaluation.

The Compose stack does not run agent daemons. Add a daemon from the Web console, then run its generated command on each machine that should host agents, workspaces, and runtime credentials.

Past the local stack — sign-in, public URLs, and provider apps — a guided path helps. Open Claude Code in the checkout and ask it to set up AgentConnect: .claude/skills/agentconnect-setup runs those steps as an interactive tutorial and verifies each checkpoint before moving on. The rest of this section covers the same ground by hand.

To evaluate local sign-in without configuring DNS or TLS, use the optional official Logto overlay and its browser-based Setup Server:

docker compose -f compose.yaml -f compose.logto.yaml up -d

Continue with the browser-based local-auth bootstrap in the @agentconnect.md/setup walkthrough. The default no-auth Compose command above is unchanged.

For image pinning, production networking, sign-in, secrets, GitHub App setup, and optional Mem0 configuration, see the AgentConnect OSS guide.

AgentConnect Cloud

AgentConnect Cloud provides a hosted management console while agents continue running in your environment. Join the Cloud waitlist.

Build your stack

Architecture