agentconnect-md/agentconnect

Purpose and topology

AgentConnect is a daemon-centric, self-hostable platform for running ACP-compatible AI agents from collaboration channels, GitHub events, webhooks, schedules, and webchat. It separates a management/control plane from edge execution so agent workspaces, runtime credentials, live messages, and sessions remain in the operator’s environment. Core deployment definitions are compose.yaml, deploy/k8s/30-deployment.yaml, and charts/operator/templates/operator-deployment.yaml.

User and operational entry points

The stable agentconnect CLI installs, starts, recovers, upgrades, and delegates to the local daemon; its command entry is packages/cli/src/index.ts, with daemon service lifecycle in packages/cli/src/service/index.ts. The daemon executable begins at packages/daemon/src/index.ts and assembles the long-running edge process in packages/daemon/src/daemon.ts. The management console is a Next.js application rooted at packages/web/src/app/layout.tsx; organization-scoped console routes are under packages/web/src/app/(app)/[slug].

Control Plane: authoritative coordination boundary

The Control Plane owns organizations, identities, agent configuration, placement, access policy, integrations, audit/usage metadata, and API/WebSocket interfaces. HTTP application/server composition is in packages/control-plane/src/app.ts and packages/control-plane/src/http/server.ts; daemon gateway handling is in packages/control-plane/src/ws/gateway.ts. It does not ordinarily persist message bodies or ACP streams: it coordinates and pushes configuration to daemons.

Persistence, identity, and secrets

PostgreSQL/Prisma backs multi-tenant coordination state and repositories, modeled in packages/control-plane/prisma/schema.prisma and accessed through packages/control-plane/src/persistence/prisma.ts. HTTP auth and organization scoping form the main request boundary in packages/control-plane/src/http/plugins/auth.ts and packages/control-plane/src/http/org-scope.ts. Secret handling is explicitly separated through encrypted/brokered providers in packages/control-plane/src/secrets/secretsBroker.ts and packages/control-plane/src/secrets/vault-transit.ts; Logto is supported for hosted/local authentication via compose.logto.yaml.

Daemon execution and session pipeline

A daemon maintains Control Plane connectivity, reconciles assigned agents/configuration, receives platform events, selects an agent/session, and runs the configured runtime locally or in Kubernetes. Session ownership and transcript/turn handling live in packages/daemon/src/session/session-manager.ts and packages/daemon/src/session/transcript-recorder.ts. ACP runtime launch/sandbox boundaries are implemented in packages/daemon/src/acp/acp-host.ts and packages/daemon/src/acp/runtime-launch.ts; runtime selection, credentials, and model discovery are in packages/daemon/src/runtimes/registry.ts.

Messaging, routing, and integration data plane

Platform adapters normalize and render Slack, Telegram, Discord, Feishu, and GitHub traffic, with shared dispatch contracts in packages/daemon/src/platforms/registry.ts and routing rules in packages/daemon/src/router/routing-table.ts. The optional Relay accepts callback/webchat ingress and forwards it to the owning daemon without durable message storage; its server is packages/relay/src/server.ts, ingress manager is packages/relay/src/relay-ingress-manager.ts, and webchat routing is packages/relay/src/webchat-router.ts. Shared daemon–relay–Control Plane frame contracts are defined in packages/protocol/src/index.ts and packages/protocol/src/frames.

Agent capabilities and infrastructure extensions

Agents receive per-agent workspace, Git policy, skills, MCP tools, memory, runtime, and sandbox policy. Workspace/Git execution is bounded by packages/daemon/src/workspace/workspace-manager.ts and packages/daemon/src/workspace/git-origin-policy.ts; MCP injection/control is in packages/daemon/src/mcp/bridge.ts. Memory supports native, managed, and external providers through packages/daemon/src/agents/memory-provider.ts, with Mem0 Cloud/OSS implemented by packages/memory-plugin-mem0/src/server.ts. Kubernetes placement/runtime-pool support spans packages/daemon/src/k8s/runtime-plane.ts and the controller in packages/operator/src/controller.ts.