System requirements

Command Center ships as a self-contained installer for Windows and macOS. The installer carries the platform itself — the app, the agent infrastructure, and the knowledge-graph engine — and first-run setup provisions the rest. What remains for you to bring is small and deliberate: your machine, your agent subscription, and your account.

At a glance

First-run setup checks Node, Python, and your agent CLI for you and reports what it found. None of those checks stops you finishing setup, and you can fix any of them afterward. Python is the one you cannot do without in practice: with no Python at all the provisioner cannot run, so the background services never start. See Install.

What the installer bundles

Everything the platform needs to run arrives in one download:

• The application — the desktop shell and every view.
• The full platform tree — the agent definitions, skills, routines, protocols, and agent-facing tool servers, laid down as readable files in the Command Center home you choose during setup.
• The knowledge-graph engine — ArcadeDB plus the Java runtime it needs. On Windows the runtime is carried inside the installer; on macOS it is fetched during provisioning. Either way there is no Docker and no separate database install.
• A managed Python runtime — each background service gets its own environment, provisioned automatically on first run.
• A documents scaffold — a clean workspace with a worked example, ready for your own content.

The bundle contains no accounts, no API keys, and no one else's data.

Third-party runtimes that ship with it

Two third-party binaries ship with Command Center unmodified, rather than being left for you to install, and both carry license obligations worth stating plainly:

• A pinned Java runtime (Eclipse Temurin), because the knowledge-graph engine runs on Java. It is licensed under GPLv2 with the Classpath Exception — the exception is what keeps your own code, and Command Center itself, unaffected by that license.
• Microsoft's console binaries (conpty.dll and OpenConsole.exe, on Windows), pinned so terminal panes behave the same on every Windows build rather than depending on whichever version the machine happens to carry. Licensed under the MIT license, © Microsoft Corporation.

NOTICES.md, at the root of your Command Center home, is the full third-party notice file — including the written offer for the Java runtime's corresponding source that its license requires.

What you bring

• Your agent subscription. Command Center is bring-your-own: agents run through your own claude CLI sign-in, on your plan and your limits. OpenAI's codex CLI can drive individual terminal panes and routines as a second engine. See BYO Claude & keys.
• Your subscription tier. Pro or Ultra, managed on the product page. Signing in requires only an account; the tier decides which surfaces unlock. See Tiers: Pro & Ultra.
• Optional API keys. A Gemini key unlocks full-depth semantic search in the knowledge graph — the graph itself works without it. Voice (Ultra) connects to a provider account you bring. All keys are entered locally and stay on your machine.
• Optional proxies. Heavy news and YouTube harvesting can route through residential proxies from any provider — off by default. See Bring your own proxy.

Your account and your machines

One subscription covers two machines. Signing in again on a machine that is already signed in does not consume a second slot — it is the same machine.

Signing in on a third machine is allowed and does not fail. What happens instead is that the least recently used of your existing machines is signed out server-side. That machine keeps running on its cached sign-in until its next refresh, then steps down to the signed-out baseline — your data and documents stay fully accessible, and the subscription-gated surfaces pause. Settings ▸ Doctor on that machine names the reason, so an unexpected step-down is diagnosable rather than mysterious. Signing in there again reverses it, and evicts whichever machine is now least recently used.

Reinstalling does not free a slot. Sign-in state survives replacing the app, on both platforms — a machine is released by another machine taking its place, not by an uninstall.

Network expectations

• Local by default. The background services and the knowledge-graph engine bind to localhost only — nothing listens on your network.
• Outbound when you work. Agent runs call your agent provider on your own subscription; the intelligence desk fetches the sources you configure; sign-in and the update check talk to agenticonsult.de. Those are the connections the platform itself initiates — anything else that leaves the machine is something you configured or an agent you dispatched.
• Offline tolerance. Once signed in, Command Center keeps working for up to 72 hours without reaching the account service. In practice that is 36 to 72 hours, because it renews at half-life rather than waiting for expiry, and there is no extra grace period afterward — the tolerance is the sign-in's own lifetime. Update downloads keep working for a further four days on purpose, so security fixes still reach a machine whose features have paused. Reconnecting restores everything immediately and deletes nothing. The Account card shows the remaining time as a duration rather than a date. Details: How updates work.