# Control Center \\ A home for your developer day

> Bring tickets, code reviews, AI agents, meetings and pipelines together. A free, open-source developer workspace for desktop, web and phone.

Control Center is a developer operations hub for one person running many streams of work. Tickets, pull requests, agents, conversations, meetings, calendar, pipelines and a personal feed share one place.

- One server, every surface: desktop, web and a paired phone render the same server-owned state. The server owns databases, credentials, external APIs and execution. The phone does not run agents. Optional fleet workers execute leased jobs without owning databases, credentials or budgets.
- Connected work: a ticket is the record. Execution happens in a conversation and its isolated copy-on-write worktree; Windows uses git worktree. Plan Studio opens from the conversation's plan row. In orchestrate mode, hiring waits for approval.
- Your next action: the inbox groups pull requests and pins approval and failed-sync blockers. Tickets, projects, a command palette and implemented Linear sync keep work connected. Jira and ClickUp are reserved names with no adapter.
- Review with context: commit-range diffs, threads, checks and deployment previews sit beside the work. A review you publish uses your forge account; agent and background publishing use the app identity. Ship, show, ask is advisory, not a mandatory gate.
- The rest of the day: read-only Google Calendar, with RSVP where permitted; server-side meeting recording and transcription, speakers, notes, decisions and action items. Summarization follows recording. RSS reading is personal, not workspace-scoped.
- Your boundaries: per-conversation propose only, act with approval or act freely profiles operate within permission policies and budgets. Soft budgets warn; hard budgets pause an agent. An approval prompt without a connected approver is denied.
- Soundscape: generative focus, relax, sleep and rise moods shaped by time and server-fetched weather. The same conditions produce the same piece.
- Solo first: collaboration chrome stays hidden with one human. Members, roles and ephemeral presence layer on when needed.
- Product media: the landing inbox is a silent looping capture of pull requests grouped by review status. Other slots are described placeholders. The separate public demo uses invented data and scripted agents with a locked-down mutating surface.
- Source: https://github.com/SamuelAlev/control-center

## The tools you’ll reach for every day.

Run the work, review what changed and keep the decisions.

### [Parallel agents](https://usectrl.dev/manual/guides/parallel-agents/)

Give each task an isolated Git worktree. Follow the run, steer an agent or take over without disturbing the rest.

### [Pull request review](https://usectrl.dev/manual/guides/review-merge-pr/)

Read diffs with discussions and checks alongside. Add an AI review when it helps, then publish with your own forge account.

### [Connected tickets](https://usectrl.dev/manual/guides/manage-tickets/)

Sync Linear, set priorities and assign the work. Link the ticket to the conversation where it gets done.

### [Meeting notes](https://usectrl.dev/manual/guides/record-meeting/)

Record and transcribe on your server. Keep the decisions and action items after the call ends.

### [Repeatable pipelines](https://usectrl.dev/manual/guides/create-pipeline/)

Build a workflow once. Run it on a schedule, from an event or by hand, and inspect every step.

### [Account switching](https://usectrl.dev/manual/guides/adapters/)

Choose the accounts each agent can use, then rotate across them without losing the run's context.

### [Usage quota](https://usectrl.dev/manual/guides/manage-costs/)

Check provider allowance and reset times before starting the next run.

### [Soundscapes & focus](https://usectrl.dev/manual/guides/focus-mode/)

Run a timed focus session, quiet notifications and shape the soundscape playing under it.

### [Observability](https://usectrl.dev/manual/guides/manage-costs/)

Follow live agents and inspect run costs, token use and latency in your workspace.

### [Skill and agent editors](https://usectrl.dev/manual/guides/manage-skills/)

Edit workspace skills and configure each agent's model, instructions and permissions.

### [One inbox](https://usectrl.dev/manual/guides/triage-inbox/)

Reviews, approvals and blockers in one queue. Jump to the next task with the command palette.

### [Check in from your phone](https://usectrl.dev/manual/concepts/remote-control/)

Follow your runs and handle approvals without returning to your desk.

## Approve a push before it runs.

Put Git pushes, PR publishing and other guarded actions behind an approval. Review what the agent is about to do before it changes anything.

No approver connected? The action is denied. Permissions are enforced by your server, not by a prompt.

## Good questions.

### Is Control Center only for AI agents?

No. Control Center puts tickets, pull requests, conversations, meetings, calendar, pipelines, agents and a personal RSS reader in one workspace. Agents are one part of the desk, not a prerequisite for using the others.

[Explore the features](https://usectrl.dev/#features)

### What is the difference between a ticket and a conversation?

A ticket records the work and its status; execution happens in a conversation. The conversation can provision an isolated copy-on-write worktree before an agent run. On Windows, provisioning uses a Git worktree.

[Follow a sample workflow](https://usectrl.dev/#workflows)

### Where do agents run, and what does the server do?

The server owns the workspace database, credentials, APIs and agent execution; desktop and browser clients display and control that work. Optional fleet workers pull leased jobs and stream events, but do not hold the database, credentials or budgets.

[Read the architecture guide](https://usectrl.dev/manual/concepts/architecture/)

### How much control do I have over an agent run?

Each conversation can use Propose only, Act with approval or Act freely. Permissions and a sandbox still bound allowed actions; approval requests without an approver are denied. Soft budget limits warn, hard limits pause, and runs keep a log.

[Preview the controls](https://usectrl.dev/#boundaries)

### Does an orchestrate plan hire agents automatically?

No. Orchestrate can research and propose roles, child tickets and a plan, but hiring waits for approval. Plan Studio opens from the plan row in the originating conversation; a ticket assignment alone does not start a run.

[Follow the sample workflow](https://usectrl.dev/#workflows)

### Can I run agents from the paired phone?

The paired phone is a thin client for the same server-backed workspace, not a second execution host. Desktop, browser and phone show the same operation; agents execute on the server or on optional leased fleet workers.

[See the connected surfaces](https://usectrl.dev/#surfaces)

### Which integrations can I use?

Linear ticket sync is implemented; Jira and ClickUp do not have adapters. Connected Google Calendar events are read-only, with RSVP only when the calendar grants write permission. Slack threads can bridge into conversations, and connected code hosts supply pull requests and checks.

[Read the manual](https://usectrl.dev/manual/)

### When do meeting notes and action items appear?

The live transcript can separate speakers while recording. After you stop, the summarizer processes the meeting and stores its notes, decisions and action items; recording and processing are distinct states.

[See the day in context](https://usectrl.dev/#day)

### Is the public demo a live workspace?

The public demo is a separate, locked-down build with invented data and scripted agents. Its records and runs are examples, not your own work.

[Explore the live demo](https://usectrl.dev/demo)

## Make yourself at home.

Your next developer day can start here. Free and open source.

- [Download · macOS](https://usectrl.dev/download/macos)
- [Download · Windows](https://usectrl.dev/download/windows)
- [Download · Linux](https://usectrl.dev/download/linux)
- [View releases](https://github.com/SamuelAlev/control-center/releases/latest)
- [Read the quick-start guide](https://usectrl.dev/manual/quick-start/)
- [Source on GitHub](https://github.com/SamuelAlev/control-center)

---
Canonical page: https://usectrl.dev/
Language: en-US
