Install

Installing Command Center is three moves: download the installer from your account, run it, and walk first-run setup. Setup takes about a minute of your attention plus a few minutes of unattended provisioning, and everything it configures can be changed later in Settings.

Before you start, have the requirements in place — most importantly an agent CLI, signed in once.

1. Download

1. Sign in to your account on agenticonsult.de. An active subscription (Pro or Ultra) is required to download.
2. Pick your platform:
   • Windows — cc_install.exe.
   • macOS — a disk image, offered as two separate downloads, one per processor family. You choose, because a browser cannot report a Mac's architecture reliably enough to choose for you.

This first download carries everything, including the knowledge-graph engine, so it is large — currently in the region of 350 MB. The updates that follow are small.

Pro and Ultra download the same file. Your tier is carried by your sign-in at runtime, never by a different binary, so changing tier never means downloading again.

2. Run the installer

Windows. Run cc_install.exe and follow the standard Windows setup. When it finishes, Command Center launches into first-run setup.

macOS. Open the disk image and drag Command Center into your Applications folder, then launch it from there.

Where you install decides where your home goes

Command Center resolves its home folder from its own location, on every launch. On macOS this makes the install location a real decision:

/Applications itself is deliberately refused as a home — it is a shared system location, and laying a documents tree and configuration into it would be wrong — so an app installed there keeps its data in your own home folder instead. On Windows the folder you named in the installer is already dedicated to Command Center, so it is used as-is.

The next screen shows you the resolved path and lets you change it before anything is written.

3. First-run setup

The dots across the top of the window name each screen and show where you are. Required screens say so; everything else can be skipped and set up later in Settings. In order:

Sign in

The first screen, and there is no Skip — Command Center is a subscription product and setup does not continue past it. Click Sign in: your browser opens on agenticonsult.de, you approve the device, and the app picks the session up automatically. If the browser cannot hand back to the app, paste the code the browser shows into the wizard instead.

Any account signs in — no subscription is needed to get past this screen. Your tier decides what unlocks once you are inside.

This screen also commits a default home so the rest of setup has somewhere to write. Choosing the folder properly is the next screen's job.

Workspace

Choose the folder everything lives under — the platform files, your documents, your configuration. The path resolved from your install location is already filled in; accept it, or Browse… to somewhere else. This screen is required.

Two things happen when you confirm:

• The platform tree — agents, protocols, routines, the documents scaffold — is laid down into this folder as plain, readable files.
• The path becomes Command Center's own file boundary, in the specific sense below.

What the home bounds, and what it does not

Command Center's own file surface is bounded by this path. The Documents view, the editors, and the file operations the app performs on your behalf resolve against this home and refuse paths outside it. Two exceptions are deliberate, and both are per-action choices you make rather than standing grants: a file you pick in a native open dialog, and a file you drag onto a Voice or image prompt, are read from wherever they live.

Agent sessions are not bounded by it. This is the part worth reading twice, because it is where an install's real file reach is decided:

• A terminal workspace can be pointed at any folder on the machine, including one outside this home. The session in that pane then works in that folder. Command Center recognizes the folder as external and asks how to connect it — Connected keeps Command Center's tools, agents, skills and memory available while the session works there; Standalone launches the agent CLI directly in that folder with none of them attached.
• Panes start without a trust prompt — Command Center writes the trust record for the pane's working directory itself, so that folder's own project configuration and hooks are in scope for the session. No permissions setting changes that. Pointing a pane at a repository you do not trust is therefore a decision, not a formality, and one to make before you point it. The terminal configurator carries the narrower options for exactly that case — including restricting a session to Command Center's own tool servers rather than merging the project's. Terminals explains why the trust record is written up front and what it means for unattended work.

If you want a hard stop rather than a narrower scope, the terminal control plane and its one-click pause are the controls that actually halt agent terminal activity. See Terminals and Autonomy and controls.

Components

Command Center provisions its own supporting pieces rather than asking you to install them. Each is listed with what it costs and what you lose by declining it, and each has its own checkbox:

Anything you skip here can be installed any time from Settings ▸ Doctor, which is their permanent home. This screen deliberately comes before anything provisions, so declining something means it is never installed rather than installed and then removed.

Knowledge graph

Pick where the graph database runs:

• Local — the default and the right choice for almost everyone. Setup provisions the bundled engine on your machine.
• External — point at an ArcadeDB server you already run, with a connection test before you commit. The database password is entered here, on this screen, for both modes.

You can skip this and set it up later in Settings; until then the graph surfaces simply wait.

Runtime

Informational — nothing here blocks setup. This screen:

• Detects your agent CLI and reports what it found. If claude is missing, install it from claude.ai/code and run claude once in a terminal to sign in.
• Detects Node and Python. Node is optional — only the video engines need it, and Command Center can install its own. Python is used only to launch the provisioner, so any Python 3.8 or newer will do.
• Provisions the background service environments automatically — a one-time pass of a few minutes. The background services cannot start before this has run once.
• Generates the agent configuration at your workspace root and trusts the folder for your agent CLI, so agents work out of the box.

Accounts & keys

Optional, and fully skippable. Every credential Command Center itself needs is on this one screen, and it sits after provisioning because the account sign-in needs a service that provisioning creates.

Keys are saved to a local configuration file in your Command Center home. They stay on this machine — never bundled, never shared — but "on this machine" means exactly that: they sit in a readable file under your home, not in the OS keychain. Mail account passwords are the exception and do go to the keychain. Anyone who can read your files can read your API keys, so protect that folder the way you would protect the keys themselves. Most features work with no keys at all.

Speech-to-text

If you kept the speech-to-text component, this is where you choose which local transcription model to download. It comes after provisioning because the picker needs what provisioning produces. The download runs as its own process, so moving on to the next screen does not cancel or lose it.

Summary

Click Enter Command Center. Setup is complete.

4. Verify with Doctor

Doctor is the full readiness checklist — tools, services, environments, and the database, each with a clear pass, fail, or informational result. It is also where you install anything you declined during setup.

• In the app: Settings ▸ Doctor.
• From a terminal, in your Command Center home: python scripts/doctor.py.

A green Doctor run means the platform is ready for real work. If a check fails, it names the fix; the reference covers the checks in Doctor checks.

On macOS, the app keeps its own support files at ~/Library/Application Support/de.agenticonsult.commandcenter. That folder is separate from both the app bundle and your Command Center home, and dragging Command Center to the Trash leaves it — and your workspace — in place. Removing either is a deliberate, manual step.

From here

Command Center keeps itself current, and it checks rather than acts: with automatic checking on it looks for a new version at launch and every four hours, and tells you when one is available. Nothing installs on its own. Installing restarts the app, which would end running agents and terminal sessions, so that step is always a Restart & update you click. You can turn the background check off entirely in Settings ▸ Updates and check by hand instead. Details: How updates work.

Now take the first-day tour: Quickstart.