Install
The installer walkthrough — from download to a running Command Center, mirroring each step of the first-run setup.
Installing Command Center is three moves: download the installer from your account, run it, and walk the first-run wizard. The wizard 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 the claude CLI, signed in once.
1. Download
- Sign in to your account on agenticonsult.de. An active subscription (Pro or Ultra) is required to download.
- Download
cc_install.exe— about 320 MB. This first install carries everything, including the knowledge-graph engine; the updates that follow are small.
2. Run the installer
Run cc_install.exe and follow the standard Windows setup. When it
finishes, Command Center launches into the first-run wizard.
3. The first-run wizard
Seven steps, in order. Required steps say so; everything else is skippable and available later in Settings.
Step 1 — Welcome
An overview of what setup will cover. Continue with Get started.
Step 2 — Command Center home
Choose the folder everything lives under — your workspace, your documents, the platform files. The wizard suggests a sensible default home; accept it or browse to your own location.
Two things happen when you confirm:
- The bundled platform tree — agents, protocols, routines, the documents scaffold — is laid down into this folder as plain, readable files.
- The path becomes the app's file-access boundary. Command Center can only read and write inside your chosen home; everything outside it is off limits by construction.
This step is required.
Step 3 — Sign in
Command Center is sign-in required. 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 works here — no subscription is needed yet. Your tier decides what unlocks once you are inside. This step is required.
Step 4 — Secrets
Optional, and fully skippable. Three fields:
| Field | What it unlocks |
|---|---|
| Gemini API key | Full-depth knowledge-graph ingest and semantic memory search. The graph works without it. |
| xAI API key | Reserved — Voice authenticates through its own sign-in, not this key. |
| ArcadeDB password | Only needed if you point at an external database server later. |
Keys are saved to a local configuration file in your Command Center home. They stay on this machine — never bundled, never shared. Most features work with no keys at all.
Step 5 — Knowledge graph
Pick where the graph database runs:
- Local — the default and the right choice for almost everyone. The wizard provisions the bundled engine on your machine; no Docker, no separate install.
- External — point at an ArcadeDB server you already run, with a connection test before you commit.
You can skip this and set it up later in Settings; until then the graph surfaces simply wait.
Step 6 — Runtime check
Informational — nothing here blocks setup. The wizard:
- Detects Node.js 22+, Python 3.11+, and the Claude Code CLI,
and reports what it found. If
claudeis missing, install it from claude.ai/code and runclaudeonce in a terminal to sign in. - Provisions the Python daemon 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 Claude Code, so agents work out of the box.
The video engines and the media toolchain are not part of setup — they install later from inside the app, each with its own consent step.
Step 7 — Done
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 or fail.
- 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 explains every check in Doctor checks.
From here
Command Center keeps itself current: it checks for updates on launch, installs them quietly, and never touches your documents, settings, identity, or knowledge graph. Details: How updates work.
Now take the first-day tour: Quickstart.