Docs / Start
CLI reference
Every crossfyre command and what it does. Type in the box to filter the list.
One CLI drives everything. These are the commands you will use most.
crossfyre loginAuthenticate the CLI to your account (API key, username/password, or browser).crossfyre logoutRemove the saved session and stop/disable any installed engines.crossfyre node initEnrol this host as a node. Signed in, it takes the oldest node on your account that has not come online yet; without a session it asks for a node key from the dashboard. Installs that node's engines, provisions the database, and installs the OS service.crossfyre node listList every node on your account, and whether each is online.crossfyre node statusShow the node daemons running on THIS host.crossfyre node up / downStart / stop the node supervisor service (brings all local nodes online or offline).crossfyre node restart / enable / disableRestart the service, or toggle start-on-boot.crossfyre node remove [id] [--inactive]Remove a registered node from this host.crossfyre extension listList engines with install state and daemon health.crossfyre extension install <ambulo|voyage|doorward|toolmark|plessor|all>Download, checksum-verify and start an engine.crossfyre extension remove / update / start / stop / restart <name>Manage an installed engine.crossfyre run <script.cfx> <type:value ...>Run a .cfx script on this machine. It needs no account.crossfyre trace --workflow-id <id> --token <t>Web Tracer: capture the sites you browse into a session's asset graph, through a local intercepting proxy.crossfyre mcpAn MCP server for an AI agent's client, over stdio: the engines on this host, a Workbench open beside it and, with an MCP key, one workspace on the platform. crossfyre mcp cloud login saves the key.crossfyre oast setupInstall your own OAST server as a service and obtain wildcard TLS, for a bring-your-own out-of-band endpoint.crossfyre oast serve / statusRun your OAST server in the foreground, or show its state.crossfyre update [self|all|<ext>]Update the CLI, the node binary, and engines from the release manifest, checking each download's SHA-256 against it.crossfyre statusOverview of local node daemons, engines and the database.crossfyre db <up|down|start|stop|restart>Manage the toolchain database container.crossfyre doctorDiagnose the environment: Docker, database, release-CDN reachability, PATH.crossfyre uninstall [--purge]Remove services, engines, binaries and the database container.