LiteLLM Agent Control Plane screenshot thumbnail

LiteLLM Agent Control Plane

Agents scattered across vendor consoles become one tidy workspace in LiteLLM Agent Control Plane, which puts Claude Managed Agents, Cursor, OpenCode, OpenClaw, Deep Agents, and Hermes behind a single login, one API, and one dashboard. Describe an agent in plain language or start from a template for a deep researcher, an inbox triager, or a security reviewer, then tick the tools, skills, and MCP integrations it may use and pick the runtime that executes it. Chat happens inline with streamed output, sessions persist across runs, and a memory layer carries context from one session to the next. Routines launch agents on a cron schedule, and each scheduled run lands in the history as its own session. An MCP proxy injects upstream credentials at the wire, so agents never hold real secrets, and provider keys sit encrypted in a vault. Colleagues can reach the same agents from Slack, Microsoft Teams, Google Chat, or a webhook, and developers can drive everything through a REST API with a live try-it reference. Administrators issue per-user virtual keys with budgets, model limits, and expiry dates, and an inbox gathers anything that needs a human decision. 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
T3 Code screenshot thumbnail

T3 Code

T3 Code puts every coding agent you already pay for behind one control surface, so Claude Code, Codex, Cursor, Grok Build, OpenCode, and Antigravity all run on your server while you direct them from your phone, browser, or desktop. Start a thread, choose the provider and model that fit the job, and watch the agent work in a shared conversation instead of a terminal you have to babysit. Permission modes decide when an agent must stop and ask, and its approvals, questions, and plan reviews arrive in the same thread wherever you happen to be connected from. When the work lands, review it file by file in the built-in diff view, then commit, push, and open pull requests through the Git and GitHub integrations without leaving the app. A real terminal sits beside the chat, and projects, settings, and scheduled tasks stay attached to the machine where the code actually runs. Install it as a background service and reach it from anywhere through T3 Connect, a Tailscale or LAN pairing, or the hosted web client, with a pairing code guarding local access. Outside agents can also drive threads over MCP, launching, messaging, and waiting on work across machines you have linked together. 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
Archestra screenshot thumbnail

Archestra

Archestra delivers the enterprise AI infrastructure layer that organizations need when managing multiple LLM providers, MCP servers, and AI agents across teams becomes unmanageable. The LLM gateway routes requests across Anthropic, OpenAI, Azure, Bedrock, and DeepSeek with virtual API keys, per-team cost limits, and dynamic model routing — giving every developer one token for Claude Code, Cursor, or Codex while finance tracks spend per department. The MCP gateway authenticates tool calls with OAuth 2.1 and On-Behalf-Of tokens so each tool executes as the calling user, not a shared service account, eliminating credential sprawl. The private MCP registry lets teams publish custom tool servers with approval flows promoting servers from dev through staging to production, each environment maintaining its own credentials and network egress policies. The Kubernetes operator manages MCP server lifecycle — deploying containers, scaling, health-checking, and routing gateway traffic to local servers automatically. The agent runtime supports scheduled triggers, email and webhook invocations, sub-agent delegation, reusable skills, and sandboxed code execution with a K8s-native filesystem. Deterministic guardrails including Dual-LLM verification and Lethal Trifecta protections prevent dangerous tool calls before execution. Built-in OpenTelemetry traces and Prometheus metrics provide full observability without additional tooling. Docker deployment exposes the Admin UI on port 3000 and API on port 9000 with a single command. 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 licensed.

Deploy
Edict screenshot thumbnail

Edict

Edict is a multi-agent orchestrator that runs every AI request through a court-style chain: a crown prince agent triages it, a planning department drafts the work, a review department can veto the plan, and specialist ministries execute what survives. Casual chat gets a direct reply, while real commands become kanban tickets whose titles are scrubbed of file paths and metadata. A vetoed plan returns for rework; an approved one is dispatched in parallel to ministries for finance, documentation, engineering, compliance, infrastructure, and HR. Commands arrive through Feishu, Telegram, or Signal channels configured in OpenClaw. The dashboard shows cards by state with heartbeat badges and stop, cancel, and resume controls, plus a department monitor and a memorial archive that turns finished work into five-phase timelines you can copy as Markdown. Nine edict templates add parameter forms and cost estimates, an officials panel ranks agents by merit score while tracking token spend, and per-agent model switching restarts the gateway in about five seconds. Agent thinking, tool calls, and results stream live. A permission matrix limits who may message whom, illegal state jumps are rejected, and every transition lands in an audit log. Worked examples cover competitive analysis, code review, and weekly reports. Dashboard login protects the console, and a systemd unit keeps it running across reboots. 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
Agent Swarm screenshot thumbnail

Agent Swarm

Agent Swarm gives a company one lead AI agent and a crew of coding workers that take requests from Slack, GitHub, Linear, or email and hand back pull requests while people only approve. The lead reads each request, plans it, and delegates to workers that run Claude Code, Codex, pi, opencode, Cursor, or Amp in isolated containers with a full development environment. Every agent keeps a persistent identity, and what one learns goes into shared memory with hybrid keyword and vector search, so the next task starts with context. Schedules run recurring jobs on cron or interval timers, and a DAG workflow engine adds triggers, conditions, per-step retries, and approval nodes that pause until someone answers in the dashboard or in Slack. The dashboard lists tasks, sessions, approvals, agents, people, workflows, scripts, skills, MCP servers, memory, and per-user usage costs. Its Apps feature builds versioned, role-restricted pages such as an incident board or a launch tracker, each with history and rollback. A configuration page tunes steering, memory, and integrations without editing environment files, and official templates supply ready-made agents for coding, review, research, QA, and content work. Workers can expose HTTP services, call approved third-party routes, and pay for x402 APIs in USDC. 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
Happier screenshot thumbnail

Happier

When a dozen coding agents are running at once, Happier puts every session in one list and lifts the ones waiting on you to the top. Sessions that need a decision gather under Needs attention and running ones sit under Working, so nothing stalls unseen. Start Claude Code, Codex, OpenCode, Pi, Cursor, Gemini, Copilot, Qwen, Kimi, Auggie, Kilo, Kiro, or Grok on any computer you have connected, or add a custom ACP backend for another agent CLI. Switch the agent mid-session, let Claude hand a review to Codex as a subagent, and move a live Claude Code or OpenCode session to another machine. Read the tool-call timeline, review the diff, mark exact lines, and send those notes back to the same session or a fresh one. Stage, commit, push, and open pull requests from the Git panel, or give each session its own worktree. Queue messages, steer a running turn, edit files, open a terminal, or dictate to the voice assistant. Pool several accounts so work continues when one hits a usage limit, and watch five-hour and weekly quotas reset. Share a session view-only, with edit rights, or as a public link. Content is end-to-end encrypted by default, and the relay serves the web app, so any browser can reach it. 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
Grasp screenshot thumbnail

Grasp

One sentence in, one reviewed pull request out: Grasp sends coding agents through a visual workflow in isolated sandboxes and leaves every approval to people. Describe a task on the home page and run it as a workflow or a Solo session. A clarify agent first asks one question at a time as clickable option cards with a recommended answer, then writes a requirement spec and plan and builds a page mock you can annotate. Workflows are drawn on a visual canvas with six node types, and failure and rollback edges send work back to an earlier step. Eight agent CLIs, including Claude Code, Codex, Cursor, and OpenCode, can run as agent nodes in a Docker, Kubernetes, or E2B sandbox shared by the nodes of a run. Runs pause at human gates in a shared inbox, and a temporary one-time link lets a reviewer without an account approve or reject. Solo sessions give a single agent an IDE, terminal, and browser, and a noVNC panel lets you watch its Chromium and take over with a click. Specs, plans, test results, and HTML previews are kept as versioned artifacts. A token page breaks cost down by workflow, source, and model. Agents push branches and open pull requests or merge requests through gh, glab, or SSH credentials stored per repository. 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
Cezar screenshot thumbnail

Cezar

Close the laptop; the agents keep shipping. Cezar is an open-source control center that runs Claude Code, Codex, OpenCode, Copilot, and eight other coding agents in parallel on your own server, around the clock. Every task gets an isolated git worktree, so a dozen agents edit the same repository at once without colliding, and overflow waits in a queue. You watch each run live: the agent's text, its tool calls, token counts, and reported cost stream into one cockpit covering all your projects. The workspace dashboard separates what needs your answer, what is running, and what finished, and the usage view totals spend and tokens per project so a runaway task shows up in dollars, not surprises. Repeatable playbooks are plain Markdown skill files, chained into short YAML workflows that can mix a different agent per step, add checks and gates, and open pull requests; nothing merges on its own. Hand it a GitHub issue in one click, connect Jira or Linear to launch from your tracker, and schedule recurring maintenance with automations. Flip Autonomous and a run stops asking questions and just finishes; run the same task two or three times and keep the best diff. State lives in plain files, no database, and the responsive interface works from your phone. 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
Manifold screenshot thumbnail

Manifold

One workspace, a whole roster of AI specialists: Manifold is an agent platform for long-horizon objectives that run through chat, visual workflows, and scheduled tasks. Specialists carry their own model, prompt, and tool allow-list, group into teams, and collaborate across many turns in a chat view that renders HTML visualizations beside text. Models come from OpenAI, Google, Anthropic, or any server that speaks the OpenAI API, such as llama.cpp or vLLM, and image generation reaches OpenAI, Google, or local ComfyUI. The flow editor draws workflows on a canvas, exposes MCP tools as nodes, and turns a saved workflow into a tool that specialists and other flows can call. Pulse schedules specialist tasks at intervals, daily, or once at a chosen time and delivers results to Matrix rooms. Projects isolate agent workspaces to their own folders, load skills from each project's skills directory, and include a file browser with upload, download, and Markdown preview. A Playground versions prompts and datasets and runs experiments that show how a prompt change shifts behavior, while the overview dashboard charts token usage, traces, and logs. Sign-in through OIDC or OAuth2 is optional and adds user and admin roles. 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
Jean screenshot thumbnail

Jean

On your own server, Jean runs a team of AI coding agents, each in its own git worktree, and lets you steer them all from a browser tab. Every task starts from real context: a GitHub issue, pull request, workflow run, Dependabot alert, security advisory, Linear ticket, Sentry error, or a plain prompt. Jean creates an isolated worktree with its own chat sessions, terminal, and diff, so several agents can edit one repository without colliding. Choose the backend per task from Claude, Codex, Cursor, OpenCode, Pi, Command Code, Grok, and Kimi Code, using your own subscriptions and CLI logins. Plan, Build, and Yolo modes, plan approval, and session recaps keep long runs reviewable. Magic commands handle commits, pull request descriptions, AI code review with tracked findings, merge conflict resolution, and release notes, and every prompt is editable with its own model and reasoning effort. A split or stacked diff viewer covers uncommitted changes, branches, commits, and checkpoints, with line comments. Mr. Robot, a beta sweeper, polls open issues and drafts plans in fresh worktrees. Linked projects share context across repositories, and MCP servers can be switched on per project or per session. Token-protected web access works from a laptop or a phone, and the desktop app can attach to the same server. 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.

Deploy
AgentRun screenshot thumbnail

AgentRun

A control room for AI agents, where every run is recorded, capped, and ready to resume after a crash. Mission Control opens first with agent and run counts, tokens, success rate, and cost per day. A Templates page applies ready-made agents for code review, KYB due diligence, lead scoring, market monitoring, and release notes in a single screen. Every run gets a Report tab with the finished answer and a Timeline tab with each message, tool call, and charge. Tools are set to allow, ask, or deny. Spend caps pause a run instead of failing it. An agent can stop and ask a person a question. The Playground starts a run from a form and shows the same request as curl, so each agent doubles as an API. Triggers start capped runs on a schedule, from a signed webhook, or on a GitHub pull request. Learning mode keeps notes, skills, and workflows from each job so repeat work needs fewer tokens. Automated code review, customer research, and competitor digests are typical recurring jobs to hand it. 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.

Deploy
SandBase Harness screenshot thumbnail

SandBase Harness

SandBase Harness gives your AI agents a proper home with sessions, tools, sandboxes, and an audit trail instead of a pile of scripts. The console lists agents with their model, status, and version, and an agent page shows its system prompt, attached tools, and skills. Every session keeps a resumable event log, and a transcript view opens any user or agent message as a rendered or raw event. Built-in tools run in a local process, per-session Docker containers, Kubernetes, or a self-hosted worker queue, and permission policies can always allow a tool or always ask a human first. MCP toolsets, credential vaults, and skill packages extend what an agent can reach, with Anthropic's xlsx, pptx, pdf, and docx skills listed next to your own. Memory stores, webhooks, scheduled deployments, and outcome definitions cover longer-running work. Settings include a model provider form, API keys for bearer authentication, and an interactive API reference for sessions, agents, environments, and vaults. A TypeScript SDK and a bundled MCP bridge connect other tools to the same runtime. 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.

Deploy
Chorus screenshot thumbnail

Chorus

No agent in Chorus touches your code until it has asked clarifying questions, drafted a plan, and won your approval. Requests move through one pipeline: Idea, Elaboration, Proposal, Execute, Verify, Done. Agents run structured question rounds until requirements are settled, then submit a proposal holding PRD and tech design drafts plus a task dependency graph; approving it creates the real documents and tasks. Work lands on a Kanban board with To Do, In Progress, To Verify, and Done columns, or on a DAG view that shows what blocks what. Live presence indicators reveal which agent is touching which card. Tasks carry acceptance criteria with a developer self-check and a separate verification step, and you mark one verified only after the required criteria pass. Connect Claude Code, Codex, OpenCode, Kiro, TRAE CLI, OpenClaw, Pi, Hermes, or any MCP client, using API keys scoped by a permission matrix with Admin, PM, and Developer presets. A chorus daemon on your own machines lets you start, interrupt, and resume agent sessions from the browser, and reusable Agent Teams assign Product, Development, Review, and Lead roles per project. Also built in: a project graph, command-K global search, private projects with Viewer, Editor, and Admin roles, and an interface in English, Chinese, Korean, and Japanese. 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 licensed.

Deploy
Clodfarm screenshot thumbnail

Clodfarm

While you sleep, a crew of Claude Code agents in a single Docker container keeps building: you plant a mission, the farm splits it into sub-agents on their own branches, and only work that passes your tests ever lands in the repo. Open the farm in your browser and every agent is a pixel Claude walking its plot, tending a task at a terminal or napping when the budget says stop, with the quest log, mission board, and a hatchery for new agents a click away. Each account is paced against its real five hour and weekly usage, measured live, always leaving you twenty percent and never paying overage, and teammates' agents message each other and hand jobs to whichever account still has room. Talk to any agent from the Claude app on your phone, post quests, set schedules like weekday issue triage at nine, and watch live dashboards the agents maintain themselves. Whiteboards let you sketch while an agent draws back full Mermaid architectures for the whole farm to see, the farm's logged-in browser does website work as you, and Slack mentions, Blender scenes, and other models from GPT to a local Ollama all plug into the same queue. 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
Heym screenshot thumbnail

Heym

Heym lets you build AI agents and workflows on a visual canvas, run them from APIs, schedules, or chat, and watch every execution, token, and cost. Describe a system in text or voice and the AI Assistant draws the graph. Prefer hands-on? Compose it from LLM and Agent nodes, conditions, switches, loops, merges, and sub-workflows. An orchestrator calls named sub-agents in parallel. RAG runs on Qdrant or pgvector, and a knowledge graph keeps facts across runs. Triggers: cron, webhooks, messaging integrations, inbox events, WebSocket messages. Playwright nodes automate browsers, and Codex or OpenCode steps work on repositories. Checkpoints pause an agent so a person can accept, edit, or refuse before the run resumes. Every run lands in History. Traces list model requests, tool calls, tokens, latency, and USD cost, and alerts fire on errors, duration, spend, or run count. Evals compare prompts across models. OpenTelemetry exports reach Jaeger, Grafana Tempo, or Datadog. Publish workflows as REST or SSE endpoints, as MCP tools for Claude Desktop and Cursor, or as public Portal chat pages, then add dashboard widgets, Data Tables, a Kanban Board, and Drive file sharing. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Source-available under the MIT License with the Commons Clause.

Deploy
Coral by Subgentic screenshot thumbnail

Coral by Subgentic

No more hunting through terminal tabs for the coding agent that stalled on a permission prompt, because Coral queues every question, approval, and file review in one Inbox. Claude Code, Codex, and Antigravity run side by side as one team, each in its own terminal session, sharing a message board and a task queue where dependencies wait on outcomes and required artifacts. Goals carry a checkable Done when line, and review gates hold dependent tasks until a reviewer approves. Files an agent produces open in a versioned viewer where you comment on passages, mark up images with a pen, arrow, or box, compare version two against version one, then approve, approve with a note, or request changes. A changed-files panel shows each agent's diff beside its chat, and optional git worktrees keep the main checkout clean. Idle agents sleep and wake when a message arrives, and whole teams can sleep through a restart. Scheduled jobs and multi-step workflows run regression suites and audits on a cron, resource queues keep concurrent agents off the same build rig, and analytics break token spend down by provider, model, thinking level, team, and task. A QR-paired phone client approves prompts on the go, and a self-hosted hub follows agents across computers. 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.

Deploy
Trinity screenshot thumbnail

Trinity

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.

Deploy
AgentConnect screenshot thumbnail

AgentConnect

AgentConnect brings Claude Code, Codex, Grok Build, DeepSeek, and any other ACP-compatible coding agent into the chat channels and repositories where your team already works, each with a role of its own. Mention an agent in Slack, Microsoft Teams, Google Chat, Lark, Discord, or Telegram and it replies in the thread, calls on a colleague agent when needed, and keeps its session visible to teammates who can step in. Work can also start from a GitHub, GitLab, Gitea, or Azure DevOps pull request, a Linear issue, a webhook, or a schedule. The web console organizes the fleet into Agents, Sessions, Schedules, Tools and Skills, Knowledge, and Daemons views. Every agent gets its own memory, skills, MCP servers, workspace, and sandbox policy, and reviewed Knowledge pages can be published for all agents to search. Decisions route new conversations to specialist agents and pick the runtime and model for each session. Review bots can run several reviewers with separate instructions on one pull request. Set who may see each agent or session, which repositories it can touch, and which agents it may call. 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.

Deploy