Polygent
The team layer for AI coding agents. A self-hosted web platform where developers, QA, PM, and stakeholders operate the same AI infrastructure, watch the same sessions, and ship features in parallel.
Polygent orchestrates CLI agents such as Claude Code, Gemini CLI, OpenCode, Kilo CLI, Codex, and Qwen Code, and ships its own built-in Polygent Code agent — adding parallel sessions, team visibility, and provider-agnostic control on top. Built for development teams of roughly 3–15 people working on shared projects.
What it adds on top of a single-developer CLI
- Parallel sessions — every session runs in its own Git worktree, so concurrent work never collides
- Team visibility — live dashboards, real-time updates, and cost tracking across all sessions
- QA before the PR — in-progress sessions can be deployed to a slot for review
- Provider-agnostic — switch agents per session, workflow, ticket, or bot without re-tooling
- Plain-language planning — stakeholders turn a description into a structured spec via the AI Planner
- Ticket sync — keep tickets in step with GitHub Issues and Azure DevOps work items
- Self-hosted — runs on your own infrastructure with the database of your choice
Core capabilities
| Area | What you get |
|---|---|
| Orchestration | Parallel AI sessions, Git worktree isolation, distributed deployment, multi-tenant workspaces |
| For Developers | Workflows, Ralph Loop, Memory stores, MCP server, IDE integration, Monaco editor, slash commands, file @ mentions |
| For Managers / PM | Statistics dashboard, AI Planner, Tickets with GitHub & Azure DevOps sync, Queues, Insights, Bots, Round Table, Automations, AI cost budgets |
| Operations | Session hooks, merge conflicts UI, role-based permissions, OAuth2 / OIDC SSO, AI cost budgets, host API keys, targeted notifications, real-time live updates |
Next steps
Recommended reading order:
- Installation — set up Polygent on your server
- Quick Start — create a workspace and run your first session in ~15 minutes
- Core Concepts — learn the Polygent vocabulary (workspaces, sessions, tickets, plans, bots, workflows, hooks, memory)
- System Requirements — hardware, software, network, database, and authentication requirements
- Security — self-hosting guarantees, auth model, and data sovereignty