cockpit setup
Generated reference for cockpit setup, including its syntax, options, results, and constraints from the canonical cockpit CLI source.
Some screens and steps may differ in the latest version.
This reference is generated from the same canonical source distributed as cockpit CLI help. See Cockpit CLI for concepts and safe operating guidance.
Inspect local setup and perform explicit managed installation actions.
cockpit setup status
cockpit setup agent status [claude|codex|antigravity|cursor|qoder|grok|muse]
cockpit setup agent login muse
cockpit setup cli install
cockpit setup cli uninstall --confirm
cockpit setup skill status [cockpit|html-mode|fleet]
cockpit setup skill install <skill> (--agent <agent> ... | --detected)
cockpit setup skill uninstall <html-mode|fleet> --confirm
cli install and cli uninstall edit the user's shell startup file on macOS and Linux and the user PATH on Windows. cli uninstall --confirm removes the very cockpit command the calling agent is using, so the next invocation fails until it is reinstalled from Settings.
Skill installation requires explicit agent targets or --detected; uninstallation takes no agent filter and removes that skill from every agent that has it. Installation and uninstallation require Cockpit's ownership marker and refuse directories with user content. Exact legacy files generated by Cockpit are migrated to the marker on their next installation; only operating-system metadata such as .DS_Store is ignored. Cockpit's core skill is not uninstallable through this command. Setup status reads secure-storage health without running migration. Agent status is read-only and returns command, installed version, available version when supported, and changelog URL. updateAvailable is true when a newer CLI version is available, false when the installed version is current or newer, and null when either version is missing or cannot be compared. This uses the same CLI status and version comparison as Settings > Updates. This command never installs or updates agent CLIs.
For muse, agent status also returns auth, the same sign-in state Settings > Agents > Muse Code shows: authMode (muse-login or api-key), account (emailAddress and name of the account signed in with muse login, or null when signed out), apiKeySaved (whether a Meta API key is saved; the key itself is never returned), and inheritedApiKeyPresent (whether Cockpit itself was started with META_API_KEY; Cockpit removes that inherited key before starting Muse Code's visual UI). Reading it never starts Muse Code. cockpit setup agent login muse opens Settings > Agents > Muse Code in the local Cockpit and starts the same muse login sign-in as its Sign in button; it returns once the request is sent or queued (delivery), not after the sign-in completes. Muse Code keeps one sign-in per user, so there are no Muse Code account profiles; sign in to other agents with cockpit accounts login --agent-type <agent>.