Skip to main content

Quick Start

This guide walks you from a fresh install to a running parallel-session workflow with tickets, code review, and a bot. Plan for ~15 minutes.

0. Sign in​

Open http://<your-server>:5000 (or :8080 if you deployed the container image) and sign in with Google, Microsoft, or Generic OpenID Connect. The first user signed in is auto-promoted to Admin and gains full system access.

Access tokens are short-lived; refresh tokens last 7 days. Auth state stays in sync across browser tabs automatically.

1. Configure an agent provider​

The built-in Polygent Code agent works out of the box with no CLI to install. For the other providers, Polygent shells out to the agent CLIs already installed on the server — wire them up before creating workspaces. Supported providers: Polygent Code, Claude Code, Gemini CLI, OpenCode, Kilo CLI, Codex, Qwen Code.

Tip: You can switch providers per session, per workflow, per ticket, or per bot. There is no global vendor lock.

2. Create a workspace​

A workspace binds Polygent to a Git repository and is the unit of multi-tenant isolation.

  1. Click New Workspace in the sidebar
  2. Fill in:
    • Name and Default branch (e.g. main)
    • Git URL + Git PAT (GitHub or Azure DevOps)
    • Ticket source (None, GitHub, or TFS) if you want external sync
    • Max concurrent tickets (queue throttle)
  3. Click Create — you become the first workspace user automatically

3. Run your first session​

A session is an AI run inside an isolated Git worktree.

  1. From My Work on the sidebar, click plus button
  2. Pick a mode:
    • Develop — ephemeral worktree, task-focused (closes on completion)
    • Chat — persistent worktree, ongoing conversation
  3. Pick the agent provider and model
  4. For Develop mode - Optionally toggle session modes: Code Architecture, UX Enhancement, Edge Cases, Code Review, Verification, Update Tests, Update Docs
  5. Type your first message — use @ to mention files and / to call slash commands or skills

You'll see live updates as they happen: agent messages, tool calls, file changes, and token/cost tracking.

4. Run sessions in parallel​

Click plus button again, and start another one. Each session gets its own isolated working folder. The sidebar shows all active sessions and tickets with live progress.

5. Create a ticket (PM/manager flow)​

Tickets turn AI sessions into trackable, queueable work.

  1. From My Work on the sidebar, click plus button and choose Create Ticket
  2. Fill in title, description, and (optionally) attach files
  3. Choose:
    • Workflow — multi-step procedure to run
    • Provider + Model
    • Developer + QA assignees
    • High priority (jumps the queue)
  4. Click Queue — the ticket enters the priority queue, throttled by the workspace's Max concurrent tickets

Tip: Use Request bot and ask him to create a ticket for you — he can fill in all the details from a plain-language description.

Tickets flow through stages: Pending → Queued → Implementation → Developer Approval → QA Approval → Pull Request → Completed (a ticket can also end in Failed, Canceled, or Merge Conflicts). The Activity Feed and Rework History panel show the timeline, including QA rejection rounds.

Tip: Use Start Ticket Templates to capture preset configurations for common ticket types.

6. Plan a feature in plain language​

Use the Planner when a stakeholder describes a feature but doesn't know the implementation details.

  1. From My Work on the sidebar, click plus button and choose Plan
  2. Pick the workspace, provider, model, and target branch
  3. Write a plain-language description and attach any context files
  4. Choose an auto-answer mode (MVP, Balanced, Features-Rich, or Custom) to let AI answer its own questions
  5. Step through the 6-step wizard: Configuration → Understanding → Clarifications → Recommendations → Specifications → Review
  6. Edit the generated plan on Review step, then click Create Ticket to convert it into a ticket and kick off implementation immediately

7. Review and merge​

When a session or ticket reaches Developer Approval or QA Approval:

  1. Open the Tickets page and click into the ticket
  2. Approve, or reject with feedback (text and/or file attachments)
  3. Once merged, Polygent creates a PR (GitHub or Azure DevOps) or performs a direct merge, depending on the workspace's Merge Mode
  4. PR status (Open / Merged / Closed / Conflicts / Failed to Create) is tracked live

8. Try a bot​

Bots are workspace-scoped (or global) AI assistants with a fixed system prompt — great for fast Q&A and triage.

From My Work on the sidebar, click plus button and choose your bot (e.g. Request for ticket creation, Debugger for debugging help).

9. Open a session in your IDE (optional)​

When you want to drop into a session locally:

  1. Open the Session page and click Open in IDE
  2. Copy the Bash or PowerShell one-liner and run it in your terminal
  3. The script downloads a single-use changes zip and unpacks it on top of your local clone
  4. Push uncommitted edits back with the matching Upload from IDE one-liner, or git push to your own remote and use Pull from Remote in the session

Tokens are minted with a 5-minute TTL and are single-use.

10. Schedule recurring work​

Use Automations to run sessions on a schedule (cron), once at a specific time, or in a continuous loop after each session completes. Pick the session type (Develop, Chat, or Bot), an inline prompt or a workflow, the provider/model, and the trigger. Failed automations auto-disable after 3 consecutive failures.

11. Capture team knowledge​

Polygent has two systems that turn each session into reusable team knowledge:

  • Insights — auto-extracted from completed Develop sessions. Categorize, dismiss, or convert into tickets.
  • Memory stores — per-workspace named buckets that agents read and write at runtime via MCP tools.

12. Run a Round Table​

When a decision needs multiple viewpoints:

  1. From My Work on the sidebar, click plus button and choose Round Table
  2. Pick personas (Moderator, Devil's Advocate, Senior Developer, QA Lead, Product Owner, Designer, or custom)
  3. Send a message — Polygent runs sequential per-persona replies plus an orchestrator cross-exchange loop
  4. Call a vote, generate a running summary, or export the conversation to TXT or Markdown
  5. Convert the discussion into a ticket or plan with one click

What's next​