Many moving parts.
One Control Center.

A home for your code, agents, reviews and everything else that makes a developer day.

Get Control CenterExplore the live demo

Give good work room to happen.

Run agents in isolated worktrees. Follow their tools, steer the work and keep the context.

macOS, Windows, LinuxAlso on web and phone

Bring the tools you already work with.

Connected through your server, not another copy of your day.

GitHub Linear GitLab Claude MCP

The tools you’ll reach for every day.

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

An agent conversation in Control Center with its task context and activity.

Parallel agents

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

Run agents in parallel

Control Center pull request review with code changes and review context.

Pull request review

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

Review a pull request

Control Center ticket board showing tasks grouped by status.

Connected tickets

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

Manage tickets

A meeting in Control Center with transcript and meeting information.

Meeting notes

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

Record a meeting

Control Center pipeline view with workflow steps and run status.

Repeatable pipelines

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

Build a pipeline

Control Center account pool editor showing eligible accounts for an agent.

Account switching

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

Manage model providers

Control Center usage panel showing provider quotas and reset times.

Usage quota

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

Manage costs

Control Center focus timer and soundscape controls.

Soundscapes & focus

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

Use focus mode

Control Center observability view showing live agents and run insights.

Observability

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

Inspect agent runs

Control Center skill editor and agent settings.

Skill and agent editors

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

Manage skills

One inbox

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

Read the documentation

Keep the thread. All the way to shipped.

Work moves between tools. Its context should come along.

  1. Start with the ticket.

    Set the priority, name the owner and link the conversation. The ticket keeps the record.

    Control Center ticket board showing tasks grouped by status.

    The intent

  2. Give the work its own space.

    Discuss a plan, prepare an isolated worktree and run the agent. Steer or take over when you need to.

    An agent conversation in Control Center with its task context and activity.

    The work

  3. Bring the result into review.

    Read the changes, follow the discussion and publish with your forge account. The story stays connected.

    Control Center pull request review with code changes and review context.

    The result

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.

Configure action approvals

An agent run paused at a Git push approval request. Show the proposed command, working directory and the operator’s approve/deny controls.

Native desktop

Image / video placeholder

Control Center inbox grouping pull requests by review status and showing a pending approval.

1440 × 900
Phone companion

Image / video placeholder

Phone companion showing the same workspace, a pending approval and the status of an agent run.

390 × 844

Your desk is a place. Your work isn’t.

Start on desktop. Check in from the browser. Stay close from your phone. One server keeps the operation together.

Native desktopIn your browserPhone companion

Your server owns the data and execution. Your devices stay in sync.

Find your platform

Good questions.

A few things to know before you settle in.

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

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

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

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

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

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

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

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

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

Make yourself at home.

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

macOS

Apple Silicon · macOS 13+

Download

Windows

x64 · Windows 10+

Download

Linux

x86_64 · AppImage

Download
Open the web appConnect to a server you run.Open the phone companionPair with your server over a sealed relay.

Prefer to host it yourself? Run a headless server

Read the quick-start guide