THE PUBLIC GUIDE
Command & Control is a self-hosted, authenticated console for conversations, approvals, design work and fleet coordination. This guide covers the established console and clearly marks staged work awaiting release.
The published native phone layout has five primary destinations: Chat, Approve, Design, Features and Board. Native also includes manual Approvals read aloud, started explicitly with no automatic speech. The browser console is published; web and native features can differ. Council is not in the current published native release.
Find sessions and managed jobs, follow conversations, share files and pictures, and use the controls supported by the selected CLI. Delivery status distinguishes a queued message from one the agent actually received.
Answer agent questions and permission requests from your phone. Review the question, options and target before making a choice. Saved decisions remain searchable.
Connect a project to a maker session. Create SVGs, 3D scenes and models, prototypes or slides, then refine versions and hand a selected result to a coding agent.
Follow work from planning through testing, review and delivery. Stage, priority and attention labels distinguish progress, a blocker and a decision waiting on you.
Coordinate Primary, Secondary and Tertiary agents using plans, claims, tasks, results, team messages and shared facts. Keep implementation and independent review separate.
Find enrolled sessions, manage labels and groups, start supported terminals or managed work, and compose a mixed-CLI fleet. Availability depends on the host, installed harness and verified capabilities.
Send notices, directives or halts to selected recipients. Follow collection and acknowledgement separately, inspect expiry and revoke delivery to remaining recipients.
Read provider-reported quotas, credit balances, tokens and reset times with their source and freshness. A missing reading stays unavailable; a failed refresh does not become zero.
Set work priority, near-limit thresholds, supported off-peak scheduling and standing rosters. Configure supported providers according to the capacity they actually report.
Inspect reported host resources and configured site checks. Review incidents, notification subscriptions and optional recovery assignments.
Search setup help and the command reference. Adjust themes, typography, colors, glow, borders and rounding with previews and reset controls.
Inspect supported installed extensions and their declared actions. Capability and confirmation boundaries remain specific to the host and harness.
The published native phone layout places Chat, Approve, Design, Features and Board first. Web-console navigation depends on the installed web release.
Council is source work awaiting release review and publication. It is not in the current published native release.
Descriptor and symbol work is prepared in source. Presentation metadata does not prove a runtime model or authorize a launcher.
The new user-plugin workflow is staged source work. It is distinct from the existing installed-extension tools and is not advertised as delivered.
The private Music work is staged and is not part of a public download promise.
Invalid, expired or unentitled JSON does not grant downloads. Do not share your Authentication JSON in chat or public reports. Installer availability comes from the actual catalog; this guide does not promise unlisted platform support.
The server hosts the console and shared services. A satellite connects another computer running supported agents. Follow the selected package’s setup and platform requirements. Connecting a device, trusting a certificate, configuring public exposure and signing in remain deliberate setup decisions.
Choose Server for the computer that hosts your console, API and database. Choose Satellite to connect agents to an existing server using its private join file. Then choose where the agents and their settings should live.
Regular installers use the selected user account on your computer. During setup, choose which CLI hooks and managed settings to install. All are selected initially; clear any you do not want, including all of them. Optional background services have their own choices.
Docker editions run setup and agents inside a separate Linux instance. Its home directory, hooks, CLI settings, credentials, services and nested Docker data persist in named volumes. Your computer needs a running Docker engine; Windows and macOS use Docker Desktop with Linux containers.
The instance is privileged so it can run systemd and its own Docker engine. It separates configuration, but is not a security sandbox for untrusted code. It does not mount your host home or Docker socket. The workspace is isolated by default; explicitly selecting a host project folder gives the instance read/write access to that folder. Stopping the instance keeps its data.
These descriptions explain the installer families. The authenticated catalog determines which versions and architectures are downloadable now. Docker editions and selective setup options require the release that includes them; a description here does not make an older package support them. macOS and arm64 support must be confirmed in the catalog.
Install the full setup package, open Command & Control Setup from your applications menu, and choose Server. A local browser wizard prepares the console, API and database. Supported Ubuntu/Debian systems can prepare Docker through explicit administrator prompts.
The same full setup package with Satellite selected. It enrolls this computer with an existing server and applies your selected hooks and settings. It does not create another console or database.
A smaller guided package for computers that only join an existing server. It offers no Server role and conflicts with the full setup package, so choose one package rather than installing both.
A self-extracting package with terminal setup for the console, API and database. Requires Docker Engine 28+ and Compose v2 already installed. Selected agent integrations and services use the installing account on the host.
Terminal setup for a computer joining an existing server. Requires Python 3.10+, a reachable server with trusted TLS, its private join file and the selected agent CLIs. Installs only the integrations and optional services you choose.
Creates a Linux Docker instance and runs server setup inside it. The console, API, database, agent home and selected hooks stay in that instance’s persistent volumes. Use this when you want a server with agent settings separate from your everyday account.
Creates an isolated Linux agent environment and joins an existing server. Agent credentials, hooks and settings stay in its own home volume. Run the agents inside the instance; agents launched directly on your host are not enrolled by this installer.
A PowerShell launcher for the isolated Linux server instance. Requires Docker Desktop running Linux containers. Keeps the server and agent configuration in Docker volumes rather than your Windows profile; the server runs in Linux, not as a native Windows service.
A PowerShell launcher for an isolated Linux satellite that connects to your existing server. Run agent CLIs inside that instance, with their settings and credentials in its volumes. This edition does not enroll agents launched directly in your Windows profile.
A Windows launcher that runs the POSIX server installer inside an explicitly selected, existing WSL2 Linux distribution. Install the server prerequisites in that distribution and keep its installation and state on the Linux filesystem. WSL1 and native Windows server operation are unsupported. This package is built separately; download availability depends on the catalog.
Enrolls the Windows user account with an existing server using PowerShell and Python 3.10+ on PATH. Applies your selected hooks and settings to supported agent CLIs in that account. Selecting a CLI’s hooks does not promise that its terminal launcher is supported on Windows. This package is built separately; download availability depends on the catalog.
A planned clickable macOS setup app for a server using Docker Desktop. It is not a release download until the package is built, its signing status is recorded and it passes real Mac validation. The Docker shell edition is a separate artifact.
A planned clickable app to join a Mac to an existing server. Native Mac hooks and background-service support need platform validation. Check the catalog; the presence of a macOS filename alone does not establish support.
The arm64 setup package has not been built and tested for this release. The x86_64 package does not imply arm64 support.
Lists the SHA-256 hashes of the downloadable release files. Use it to check that a file matches the release. A checksum is not a publisher signature; signing status is listed separately for each installer.
Self-hosting C&C does not make cloud model requests local. Review the selected providers, enabled tools and network policy. Independent agent review supplies evidence; it does not enforce an outbound-data boundary.
Earlier fictional screenshots and interactive demos are not included in this refreshed public tour. They are historical source fixtures, not evidence of current release or platform support.