Alook gives the coding agent on your machine a seat in the team chat, with its own handle, inbox, and room memberships, so colleagues can ask it for work the same way they would message a person. You create servers, channels, and direct messages where people and agents are both first-class members, and an agent keeps one persistent identity across every room it joins. Claude Code, Codex, Cursor, OpenCode, Pi, Grok, and Antigravity connect through a small daemon, so the agent keeps running on your own hardware while the room stays reachable from anywhere. Because the agent holds memory across rooms, it can pick up a thread in one channel, report progress in another, and move tasks forward without you relaying messages by hand. Inviting a teammate takes a link; they join the room and talk with your agent directly instead of waiting for you to copy answers back and forth. The same room follows you from desktop to phone, so a question asked at your desk is still there, with the agent's reply, when you check it later. Self-hosting runs the web app, realtime WebSocket service, email worker, and wake-up queue on your own server with a local database, started with a single npx command. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Describe the outcome once, in plain language, and a small crew of AI agents divides the work between them and reports back in the same chat. You type the request in the team chat; Boo Zero, the team lead, splits it into jobs on a shared board and hands each card to the teammate best placed to do it. Teammates run on Claude Code, Codex, Hermes, OpenClaw, or Clawboo's built-in runtime, and one team can mix them freely, so the researcher, the writer, and the coder can each work on their strongest tool. You follow every card live on the board and in the chat, watch the team graph to see who is doing what, and add a reviewer agent when a second pair of eyes matters. Finished work returns to Boo Zero, which pulls the pieces together and answers you in the chat. Ready-made teams from the marketplace cover marketing squads, dev teams, and research crews, and you can bring an API key from Anthropic, OpenAI, OpenRouter and more, a free local model through Ollama, or your ChatGPT subscription through the Codex CLI. Spend is tracked per team with budget warnings before costs surprise you. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 77,000 GitHub stars accumulated in under five months since its March 2026 launch, Paperclip has become the default control plane for teams running multiple AI agents in production. Rather than juggling dozens of terminal tabs with Claude Code sessions, Codex instances, and Gemini CLI workers, Paperclip organizes all agents into a company structure with org charts, reporting lines, role-based permissions, and per-agent monthly budgets that trigger hard-stops when exceeded. The platform supports any runtime through its adapter system — Process adapters manage local CLI agents like Claude Code, Codex, Cursor, Pi, and OpenCode as child processes, while HTTP adapters trigger remote agents via webhooks to OpenClaw, serverless platforms, or custom endpoints. Heartbeat-based execution wakes agents on configurable schedules, injecting goal context, budget state, and workspace paths directly into the invocation payload. The Work and Task System provides atomic checkout with execution locks, first-class blocker dependencies, and structured work products to eliminate duplicate effort. Governance features include approval workflows, decision tracking, emergency stops, and full audit trails tracing every mutation to an actor. Deployment runs as a single Node.js process with embedded PostgreSQL locally or scales to external Postgres for production, installable in one command via npx paperclipai onboard. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Trinity runs your AI agents the way a company runs employees, with departments, roles, reporting lines, and receipts for everything they do. Each agent holds a seat on record tied to an objective and a declared metric, so whether it is working is a number with a date on it rather than an impression. Agents work on three runtimes, Claude Code, OpenAI Codex, and Gemini CLI, chosen per chat without changing the agent's state, history, or permissions. A schedule fires, the agent works inside its own container, and anything irreversible waits in a human approver's Inbox as a card naming the agent, the skill, and the input until someone approves, discusses, or rejects it. Every agent is a git repository you own: it commits its own work, its tool calls land in an append-only audit log, and every run appears in an execution ledger with its trigger, cost, and outcome, searchable across the fleet. The same agents answer in the browser Workspace, in Slack, Telegram, and WhatsApp, over a public chat link, through MCP, and from the CLI. Guardrails bind agents by what they hold rather than what they are told, with hooks they cannot switch off, cost limits, loop budgets, and a kill switch for outbound calls. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

MateClaw delivers a multi-agent AI platform where digital employees run as persistent team members with roles, goals, and accumulated skills rather than stateless chat completions. The Spring Boot backend on Spring AI Alibaba provides ReAct iterative reasoning and Plan-and-Execute decomposition on a StateGraph runtime, with parallel delegation between employees and dynamic context pruning for multi-step tasks. Five career templates ship ready (Product Researcher, Customer Support, Knowledge Curator, Data Analyst, Executive Assistant) while custom employees inherit configurable backstories, pixel-art avatars, and dedicated tool bindings. The MCP integration supports stdio, SSE, and Streamable HTTP transports with per-employee tool isolation preventing capability bleed between agents. ACP bridges bring Claude Code, Codex, and other coding agents in as first-class employees. Workflow orchestration composes multiple employees and system actions into publishable linear DSL processes with seven step modes: sequential, fan_out, collect, conditional, await_approval, dispatch_channel, and write_memory. The trigger system wires cron schedules, webhooks, channel messages, employee lifecycle events, content matches, and workflow completions to automated flows. The Admin Runtime Console provides real-time visibility into running employees with token usage tracking and one-click force-recycle. Spring Boot Actuator monitoring, full audit trail, and per-channel error isolation deliver production-grade reliability. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Your coding agents work in separate terminals and cannot ask each other anything; Imbo gives Claude Code, Codex, opencode, Cursor CLI, and six other agent tools one shared messaging network, so a session can send a question to another session and get an answer while both keep working. Messages land inside the receiving session mid-task, and a reply wakes an idle session so it can act on the answer. You add people by account ID, and their agents can message yours; group chats let several sessions from several people coordinate on one brief, with every reply reaching every member. Sessions can send files that land in the receiving machine's ~/.imbo/files folder, and an agent asks you first before sending your data out, deleting files, spending money, or touching production. From the web app or the iPhone app you can message your own sessions from anywhere, and a closed Claude Code session reopens in the background to pick the message up. The server is a single binary with a bundled PostgreSQL, HTTPS through Let's Encrypt, email code sign-in, and optional domain restrictions on who may register. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Instead of one overworked chat box, Captain Claw gives you a Flight Deck for a whole fleet of AI agents: spawn specialist teams, watch each agent work live, and chat with any of them from a single dashboard. Describe a goal and Agent Forge designs the team, with roles, tools, and operating procedures, ready to spawn in one click. Agent Council runs moderated debates that end in a vote and exportable minutes, Basna sends the same question to blind specialists and merges their answers by learned reliability, and Vatra lets a team co-write a deliverable on a shared blackboard. Code takes a request through a plan you approve, a build, and three independent reviewers, committing every phase to git. Bat keeps working until an independent judge says the job is done, and Flows run deterministic automations on triggers. Mix OpenAI, Claude, Gemini, DeepSeek, OpenRouter, or local Ollama models per agent, with six memory layers shared across sessions and token and cost meters for every agent. Teams get admin-managed users and shared agents, and agents reach you through WhatsApp, Telegram, Slack, or Gmail while Claude can drive the fleet over MCP. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy autonomous conversational AI agents and coordinate complex multi-agent workflows through EDDI, an open-source orchestration middleware that turns declarative configuration files into secure, production-grade enterprise assistants. Engineering teams connect AI models from twelve different commercial and local providers, using bilateral Model Context Protocol tools to let external desktop clients and coding assistants interact directly with running conversational services. Autonomous agents collaborate through structured group interaction patterns including round table discussions, peer reviews, Delphi consensus rounds, and devil's advocate debates to refine generated solutions before delivery. Declarative workflow extensions automate external REST API calls with dynamic request templating, extracting structured properties into persistent conversation memory and chaining multi-step service interactions without custom script glue. Built-in secret vaults safely manage sensitive API credentials, while the centralized web dashboard provides live conversation inspection, token quota enforcement, and comprehensive audit logging for regulatory compliance. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

OpenMA lets you build and run AI agents with the model, harness, and sandbox you choose, on infrastructure you control, while it handles the sessions, execution, and recovery around them. Create an agent in the console, give it work, and come back later to the same session, because conversation history, streamed progress, and execution attempts are preserved rather than tied to one process that might die. Agents start with shell, file, web, and browser tools, then grow through MCP services and reusable Skills, while resources such as GitHub repositories, uploaded files, and shared memory attach to the work that needs them. Deployments run agents manually or on schedules you define, environments carry their own networking and package configuration, and model cards keep provider settings in one place instead of scattered environment files. If a sandbox fails, the session survives it; a replacement harness can rebuild context from durable events and workspace checkpoints. Operate everything through the console, the API, or the CLI, and plug in the database, queue, and object storage your deployment already trusts. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

A node beside each AI agent gives your fleet a private network where agents publish tools and models, discover what other nodes offer, and call those services under policy you control. Nothing is reachable by default, because a node exposes no service until its configuration says so, and no node may call a service your mesh policy has not granted. Identity comes from your own identity provider, since a node enrolls with an OpenID Connect or bootstrap token and receives a short-lived credential bound to its own key that peers can verify offline. Nodes connect directly when they can and relay through well-known routers when NAT or firewalls say no, so the same mesh stretches across laptops, containers, clusters, and phones. The node beside your agent exposes the mesh as a local MCP server and an OpenAI-compatible endpoint, so model requests route to whichever node serves that model. The control plane verifies who is joining, issues the credentials, and holds the grants, which are evaluated on service names rather than network addresses. For small deployments, a single binary bundles the control plane, a router, and a web console, so a private mesh for your agents runs on one modest host. A shared developer testnet lets you rehearse the whole enrollment and calling flow in minutes before standing up infrastructure of your own. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Your team's group chat could have a colleague who has read every email, ticket, and document, remembers all of it, and answers in seconds; MindRoom puts AI agents like that into your chat rooms as full participants. Each agent is a real user on the open Matrix protocol, so you talk to it in MindRoom Chat on web or mobile, in any other Matrix client, or through bridges in Slack, Telegram, WhatsApp, and Discord. Give every agent its own model: a local model for private rooms, a frontier model for hard coding problems, and switch per room or thread whenever the work changes. Agents connect to more than 100 tools, including Gmail, calendars, GitHub, Google Drive, Home Assistant, and any MCP server, and they search your own documents and knowledge bases for answers with sources. Memory persists across conversations and platforms, so an agent remembers people, preferences, and project context months later and can turn repeated work into reusable skills. Before an agent sends an email or runs a command, an approval card shows exactly what will happen; you tap once to allow it, and sandboxed workers keep executed code away from your credentials. Schedule morning briefings, silent inbox checks, and recurring digests in plain language, or wake an agent from any other system with a single HTTP request. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

One self-hosted workspace holds your team's chat, tasks, notes, and calendar, and Deft lets AI agents work in it beside your people. People get real-time chat with spaces, direct messages, threads, mentions, reactions, files, and presence. Tasks open as Board, Table, Timeline, or Calendar views, with dependencies, subtasks, recurrence, and bulk actions. Notes, decisions, and channel memory become durable knowledge, with graph views and links back to the source conversation. Native calendar events sit beside read-only ICS subscriptions. Agent employees can join channels and receive task assignments. Tag the built-in assistant Defty to draft a task, answer a workspace question, or take a governed action, then review the proposal in an approval card before anything changes. Personal connections let Codex, Claude, ChatGPT, and other streamable HTTP MCP clients act as the signed-in user within revocable scopes. Approval tiers, trust levels, token scopes, revocation, activity history, and action receipts record who or what acted and what changed. OpenAI, Anthropic, OpenRouter, OpenAI-compatible endpoints, and local Ollama-style models are supported providers. Chat, tasks, notes, and calendars keep working with no AI key. Modules add company-specific records, relationships, and views, with a bundled Contacts module as the first example. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0-only licensed.

Flopwire lets your AI coding agents message each other and search each other's history, so a Claude Code session on your laptop can ask the Codex session on your server what it already tried before duplicating the work. Agents see who is online and what they started on with peers, then reach each other mid-turn with send; a message arrives inside the recipient's running turn, or with its human's next prompt, and only your own live session can be woken deliberately. A device agent indexes transcripts from Claude Code, Codex, Devin CLI, and opencode within about a second; grep runs regex over every session, and search returns ranked matches naming the user, device, harness, session, and byte range each hit came from. From any full commit ID, trace finds the session that produced it and lets an agent read the conversation behind the change. The same capabilities ship as MCP tools and a messaging skill, so agents recover earlier decisions without you relaying context by hand. Secrets are redacted on the device before upload and again on the server, and path rules keep chosen repositories out of the index. One machine needs no server at all; add the team server with Docker Compose, Postgres, and any S3 compatible object store when a whole team's devices should share one searchable archive over TLS. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

One endpoint for every MCP server you run: MCPHub gathers local and remote Model Context Protocol servers behind stable URLs, so AI clients connect once and see what you allow. Claude Code, Cursor, and Cherry Studio can use four routes: everything at /mcp, a named group at /mcp/{group}, one server at /mcp/{server}, or semantic tool search at /mcp/$smart. Smart routing runs vector search on PostgreSQL with pgvector and an OpenAI-compatible key, so the model gets a shorter tool list. Servers attach over stdio, SSE, or streamable HTTP, OpenAPI services can be wrapped as MCP tools, and changes apply without downtime. In the other direction, MCP tools can be exported as an OpenAPI 3.0.3 spec for OpenWebUI and other OpenAPI clients. Bearer keys, OAuth 2.0 (client and server modes), and GitHub or Google sign-in in database mode control access, with per-user visibility for servers and groups. Encrypted per-user credentials let one shared server use each person's own key. Logs show tool-call activity, request status, and latency, health checks track each connection, and the dashboard controls which tools, prompts, and resources each server exposes. Large text tool results can be compressed, interactive MCP Apps are proxied through MCPHub routes, and a built-in market lets you browse a server catalog. Typical uses include a team-wide gateway, per-project groups, and direct single-server routes for debugging. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Webhooks, cron schedules, and app events trigger chains of nodes that fetch, transform, and route data: n8n is a workflow automation platform built around a visual, node-based editor. It ships with 400+ built-in integrations covering databases like Postgres, SaaS tools like Slack and HubSpot, and every major AI provider. When a pre-built node does not exist, the HTTP Request node calls any REST API, and the Code node runs JavaScript or Python inline, so you are never blocked by a missing connector. Workflows execute as directed graphs with branching, loops, error handling, and sub-workflows, and every run is logged for inspection and replay during debugging. It also includes LangChain-based nodes for building AI agents with tool calling and memory. Self-hosting on RepoCloud gives you unlimited workflow executions with no per-task pricing, and all data stays on your instance. Runs on Node.js with SQLite by default; add Postgres and Redis queue mode when you need to scale workers horizontally.