Skip to content
Control Center

Introduction

Control Center gives you command over a fleet of AI coding agents. Spawn agents, watch them work in real time, review their PRs and manage repos, workspaces and integrations — from a native desktop app, a browser, or your phone.

What you can do

Section titled “What you can do”
  • Message agents: spaces are the primary way to drive the fleet. @-mention an agent and it dispatches into its own copy-on-write worktree, so several can code and review in parallel without touching your checkout
  • Orchestrate the big asks: give the orchestrator a goal, approve the whole-team plan it proposes once and a generated pipeline runs it
  • Review and merge PRs with a built-in diff viewer, inline comments and AI-powered review
  • Hand agents disposable machines: a rig is a throwaway VM — a browser, a desktop, a phone, or an enclosed terminal — the agent drives while you watch live and can take over; dev servers inside are forwarded to localhost, the agent’s browser and https://myapp.test
  • Automate workflows with DAG-based pipelines triggered by events or schedules
  • Manage knowledge with workspace-scoped memory, facts and policies
  • Track work with vendor-agnostic tickets, projects and delegation
  • Record meetings with on-device capture, transcription and diarization, then summarized into notes, action items and decisions
  • See your day with Google Calendar sync, RSVP, meeting alerts and record-and-link
  • Follow the fleet from your phone: pair a device with your server and read messages, reply and triage tickets. The phone takes the best path it can reach — loopback, LAN, tailnet, or TLS — and falls back to an end-to-end-sealed relay that forwards frames it cannot read
  • Drive agents from Slack: bridge a workspace to a chat app and mention the bot, reply in a Slack thread, or file a ticket with a slash command — over an outbound connection, so no public endpoint is needed
  • Integrate with GitHub, Linear, Slack, Google Calendar and over 100 MCP tools

You do not have to install it

Section titled “You do not have to install it”

The same application runs in your browser at app.usectrl.dev, with the same features.

Every client — desktop, web and phone — is a thin renderer over a headless server that owns your data and does the work. The desktop can spawn that server for you; a browser tab cannot, so the web app connects to one you run. That server can sit on your own machine (ws://localhost:9030, no certificate needed) or on a remote host reachable over TLS, a VPN, or a tunnel.

See Install for the browser route and Deployment and clients for how the three clients relate.

Next steps

Section titled “Next steps”