How updates work

Command Center keeps itself current. You install once from the full installer; after that, the app updates itself through a built-in updater — small downloads, verified before they touch your machine, installed without ceremony. This page explains what actually happens, what an update contains, and how the app behaves when you are offline.

The update loop

When the app starts, it checks the official update channel for a newer release. If one exists, it downloads a compact update bundle, verifies it, installs it quietly, and you are on the new version — no reinstall, no wizard, no re-entering anything.

Two properties of that loop matter to you:

• Every update is cryptographically verified. Releases are signed when they are built, and the app checks the signature before installing anything. An update that does not verify is simply not installed — the channel being reachable is never, by itself, enough.
• Updates require your sign-in, not your subscription. The update channel is available to any signed-in account — including one whose subscription has lapsed. Fixes and security patches keep reaching your install regardless of billing status; what your subscription controls is which capabilities are unlocked, not whether your software stays healthy.

What a release contains

An update is not just a new app window. Each release carries the platform itself: the desktop shell, the local services, the agent definitions, skills, and protocols that make your agents competent, and the integrations the production features run on. The whole system moves forward together in one versioned step, so its pieces never drift out of sync with each other.

Two boundaries hold on every update:

• Your data is never touched. Your documents, settings, company identity, memory, missions, and knowledge graph are yours — updates install software around them. Seed files the platform shipped with are only ever laid down where nothing exists yet; a file you have edited is never overwritten.
• The heavyweight runtime rarely moves. The bundled database engine that powers the knowledge graph updates only when its version actually changes — the update check will prompt you through a short repair step on those rare occasions, rather than shipping hundreds of megabytes with every release.

Offline behavior and the grace window

Command Center is a local-first product: your agents, documents, graph, and services all run on your machine, and day-to-day work does not depend on a connection to the account service.

Sign-in status is refreshed quietly in the background while you are online. When you are offline — or the account service is unreachable — everything keeps working on your last confirmed status for a grace window of about two weeks. A warning appears in the app a few days before the window closes, so an expiring grace period never surprises you.

If the window does run out, the app steps down to its signed-out baseline: your data and documents remain fully accessible, and the platform's gated capabilities pause until you are back online and signed in. Reconnecting restores everything exactly as it was — nothing is deleted, reset, or re-downloaded.

What you actually have to do

Almost nothing. Stay signed in, let the app check on launch, and read the changelog when something new lands. If an update ever seems not to have arrived, the troubleshooting section covers the update checks the Doctor view can run for you.

Where to go next

• Install — the first-time setup the updater takes over from
• BYO Claude & keys — what the subscription covers versus what runs on your accounts
• Changelog — what shipped, release by release
• Troubleshooting — if an update did not behave as expected