Skip to content

Start here

Documented Checked against the CLI's current help and source. Not run end to end. CLI 0.3.1, checked 2026-10-16.

Quox is a small command, quox, that you talk to in plain words. Behind it sits QuoxCORE, the engine your agents run in, on your own machine or a server you control.

  • An agent that works while you are away. Build it once, give it a job and a schedule, and it wakes on its own, does the job and posts what it found. See it run.
  • Answers from the agent’s own record. Ask Quox what your agent reported and the answer comes from the agent’s own run, with the numbers tied to the run that produced them. See the answer.

Every command says where to type it:

  • your terminal (blue, $): your normal shell.
  • inside quox (amber, ›): typed after you have started quox, in its conversation.

You need a terminal on Linux, macOS or Windows, and Node.js 20 or later.

On Windows?

On Windows, use WSL2.

your terminal
npm i -g quoxcli

No Node yet? A fresh Linux box usually has none: install Node first. If npm says permission denied (EACCES, common on Linux), do not reach for sudo: see the no-sudo options. More detail is on Install.

your terminal
quox

The Q draws itself in and says hello. The first time only, you see a short notice. Press Enter to continue. More on First run.

What is in the first-run notice?

Who we are, the Terms and Privacy links, the licence, and that the CLI sends no telemetry.

QuoxCORE is the engine your agents run in. Pick the one that fits you.

Inside quox, /connect server points it at your server and signs you in:

inside quox
/connect server https://quox.example.com

It asks for your email and password, then you are in the conversation. Replace the address with your own.

No account on that server yet? Ask whoever runs it to add you (quox org members add). You will see the invitation with quox invites.

If you have not connected Quox to a QuoxCORE yet, it opens Getting started, a setup guide. It is scripted: no AI is running yet, and it says so. It asks what you would like help with, tells you in one line what Quox will do for that, and offers to set one up on this machine for you. The first install takes tens of minutes. Details are on First run and Install.

How the guided setup works, and what works today

The guide sets up QuoxCORE on this machine in Docker. The guide, its machine checks and the guided install are built, and the whole flow has been run end to end on a clean machine: it checks the box, sets up QuoxCORE in Docker, brings the services up healthy, and signs you in. The first run builds the images from source, so the first install takes tens of minutes.

Back in your terminal, not inside quox:

your terminal
quox --demo

This plays a simulated session with demo data. No server is contacted and nothing real runs. Steps 4 and 5 below need a real QuoxCORE, so come back after A or B.

Inside quox, ask something that only reads:

inside quox
what is running?

Quox hands it to the right agent and shows each step as it happens. Nothing here changes anything. Anything risky would wait for your yes (approvals in the terminal are in preview). The answer depends on what your QuoxCORE is running, so yours will differ from anyone else’s.

You can also look at the roster under the status line:

inside quox
/roster all

Actions Quox takes end with a receipt line, which can show as pending at first. To expand the last turn’s policy checks, inside quox:

inside quox
/aocl
What are AEE, AOCL and WARD?

By default Quox shows compact lines for three records as they happen: the envelope (AEE), the policy checks (AOCL) and the witness record (WARD). A receipt line can show as pending until the witness record lands.

To check a receipt yourself against the witness chain, follow Check a receipt yourself. To read the roster in full, see What is running.

The Quickstart is the two-minute version. If something does not go to plan, see Troubleshooting. For the keys, see The conversation.