System Requirements
Hardware
| Component | Minimum | Recommended |
|---|---|---|
| CPU | 2 cores | 4+ cores (more if you run many parallel sessions) |
| RAM | 4 GB | 8+ GB |
| Disk | 10 GB free | 50+ GB free (scales with concurrent sessions and repository size) |
Disk usage scales with the number of concurrent sessions, plans, and round tables — each gets its own Git worktree under StoragePath.
Software
| Requirement | Version | Notes |
|---|---|---|
| .NET Runtime | 9.0+ | Runs the API, Session Agent, and Deployment Agent |
| Git | 2.20+ | Worktree-based isolation |
| OS | Windows 10/11, Windows Server 2019+, Linux (Docker) | Windows Service deployment is the recommended path on Windows |
Agent providers
Polygent offers seven providers. The built-in Polygent Code agent needs no CLI install. For the rest, Polygent shells out to provider CLIs already installed on the API server — install whichever you plan to use:
- Polygent Code (built-in, no CLI)
- Claude Code
- Gemini CLI
- OpenCode
- Kilo CLI
- Codex
- Qwen Code
Each external provider's CLI must be on PATH and have valid credentials for the API it talks to.
Database
Polygent supports three database providers, configured via appsettings.json:
| Provider | Use Case |
|---|---|
| SQLite | Default, zero-configuration, suitable for small teams and trials |
| PostgreSQL | Recommended for production with multiple users |
| SQL Server | Enterprise environments with existing SQL Server infrastructure |
See the Database configuration guide.
Network
- The API listens on a configurable port (default
5000for a bare process / Windows Service;8080inside the container image). Override with the standard ASP.NET CoreUrls/ASPNETCORE_URLSsetting. - Real-time updates require WebSocket support — make sure reverse proxies forward
UpgradeandConnectionheaders - Agent provider CLIs need outbound access to their respective APIs (Anthropic, Google, OpenAI, etc.)
- The Session Agent and Deployment Agent services connect back to the API over HTTPS using an API key
- Optional: GitHub and/or Azure DevOps connectivity for OAuth login, PR creation, and ticket sync
Authentication
Polygent supports the following sign-in methods:
- Google OAuth2
- Microsoft OAuth2 (Microsoft 365 / Entra ID)
- Generic OpenID Connect — any OIDC-compliant IdP (Okta, Auth0, Keycloak, etc.)
Configure OAuth credentials in appsettings.json. JWT keys (RS256) are auto-generated under StoragePath on first run. Tokens use secure, HttpOnly cookies and rotate automatically; sign-in state syncs across browser tabs.
Browser support
The client targets evergreen browsers:
| Browser | Minimum |
|---|---|
| Chrome | 110+ |
| Edge | 110+ |
| Firefox | 115+ |
| Safari | 16+ |
WebSockets must be allowed end-to-end for live updates.
Optional integrations
| Integration | Use Case |
|---|---|
| GitHub PAT / OAuth | OAuth login, issue sync, PR creation, public release pulls |
| Azure DevOps PAT | Work item sync, PR/MR creation and tracking |
| Session Agent host(s) | Spread AI sessions across multiple machines |
| Deployment Agent host(s) | Run slot deployments on dedicated machines |
| MCP-compatible CLIs | External agent access to Polygent's ticket/session search |