Top 15 quox CLI commands, with examples

Reason
AgentsQuoxMindAgentic TeamsMirror & QuoxHatQuoxLensRemember
QuoxMemoryQortexCompoundingQuoxPlanCodebase MirrorAct
QuoxFlowQuoxEngineQuoxAgentQuoxChatAutonomyRun
EnterpriseOrganisationsPowers & ToolsmithQlusterQuoxBastionInterfaces
QuoxMCPQuoxCLIQuox ConsoleQuoxBoxQuoxVoiceGovern
HITL ApprovalsQuox SecurityAgent HonestyQuoxVaultAI GovernanceAgentic AIProve
For AuditorsVerifiable AI OpsLoggingQuoxSEOEU AI ActCompliance SuiteChannels
Matrix RoomsDiscord ProTelegram ProQuoxSignalCoreCommsAll products A-ZBuild
QuoxProofDeveloper KitPlugin SDKBring your tool to QuoxQuoxpertQuoxSkillsShip and sell
Build and sellBrowse MarketplaceDownloadsProtocolsDev Suite
Dev ServersQuoxBuildQuoxSlotsShared Skills + RulesQlarityDev workflow
RepoBrainGripeTriageFixLoopProofLoopDoneEngineAll products A-ZGet started
OverviewArchitectureProtocols
AEEAOCLVOLTWARDReference
GlossaryAPI ReferencePlugin SDKDockerAll products A-Z
Your terminal is the control plane for a governed multi-agent platform. Not a thin wrapper over an API: the whole of QuoxCORE (agents, fleet, autonomous loops, memory, evidence, roadmap) is drivable from one quox binary.
The part people do a double-take at: when a governed agent hits an action it is not allowed to take on its own, it does not stop and it does not sneak around the rule. It hands you the exact command to release the gate, and you paste it. Governance you can run from a prompt, with a witnessed evidence trail behind every line.
Here are the fifteen we reach for most.
Authenticate once, everything else inherits the session.
quox loginProfiles and orgs are first class: quox --org acme login and quox -p staging login keep separate contexts side by side.
The whole platform's health in one screen: services, queues, workers.
quox statusWhen something feels off, quox doctor runs the deeper diagnostics.
Talk to CommanderQ or route straight to a named agent, streaming by default.
quox chat "which workflows failed in the last hour and why?" --agent cipherNo dashboard needed to ask the estate a question.
Run a governed tool against a managed host. Every call is audited, no raw SSH.
quox fleet exec --tool health-check --input '{"host":"web-prod-01"}'quox fleet status and quox fleet agents show what is under management first.
Stand up an autonomous agentic loop with an explicit capability scope.
quox objective create "triage new gripes and draft fixes" \
--execution-mode loop --loop-backend claude \
--capability-scope repobrain_query,gripe_readA DAG plan is the default. --execution-mode loop runs a QLoop backend instead, and because a loop is not a reviewable plan, it always asks for one human approval before it starts.
This is the one. A running agent reaches a gated step. It cannot self-approve, so it surfaces the exact command for a human to run:
quox objective checkpoints
quox objective approve-checkpoint <objectiveId> <checkpointId>The gate releases, the loop continues, and the approval is witnessed on the evidence chain. Deny with deny-checkpoint, or stop a running loop outright with quox objective halt <id> (same signed kill as a denial).
The same human-in-the-loop pattern for one-off tool runs and requests.
quox inbox list --status pending
quox inbox respond <itemId> --action approve --comment "verified with owner"The approval queue lives in your terminal, not a tab you forgot to open.
Durable, typed memory your agents actually read before re-deriving anything.
quox memory search --query "postgres connection tuning"
quox memory create --content "..." --type factSemantic search across vaults and notes when you want the knowledge, not a keyword match.
quox brain search "how does our billing retry logic work?"DoneEngine answers the only question that matters before a release: can this ship, and what is the evidence? Advisory, never blocks.
quox done check <subject>quox done board is the estate scoreboard across every surface.
Inspect and verify a VOLT evidence bundle. Proof that a run happened the way the logs say.
quox volt verify <bundleId>Paired with quox governance for policies and the WARD hash chain, this is the audit trail, self-serve.
Replay and visualise an agent run end to end: what it saw, what it decided, what it called.
quox trace list
quox trace show <traceId>QuoxPlan's focus lens: what matters right now (P0, blocked, decision needed, in flight, stale).
quox plan focusquox plan show <streamId> opens the full stream, and notes are append-only so the history is intact.
Query, run, and promote governed skills (QSKL Crystals) from the shared library.
quox skills list
quox skills run <crystalId>Ask a live page a question through the governed browser surface, session isolated and receipted.
quox qlarity read https://app.example.com --inspector novaThe safe way to let an agent look at a running page, with arbitrary evaluation always gated behind a human approval.
Try it yourself. Every command above runs in the QuoxCORE web terminal, no local install required. The approval flow (commands 6 and 7) is the one to watch: start a loop, let it reach a gate, and see it print the exact approve-checkpoint line for you to run.
Full command reference is in the docs, and the QuoxCLI product page has the quick start.
QuoxCLI ships with QuoxCORE. Every command is governed, witnessed, and yours to script.