Skip to main content
Install XORCISE and get it running. When you finish, the web UI is open and nothing is configured yet. Time: about 5 minutes · Interface: command line

Before you start

  • Python 3.12 or newer, with pip or uv.
  • Docker, with the daemon running and the Docker Compose v2 plugin installed. On Debian and Ubuntu that is sudo apt install docker.io docker-compose-v2.
No Docker, or looking around first? Start with xorcise up --stub instead of xorcise up. Everything in this page still works, and the web UI opens as normal, but no mission actually runs.

Install

That is the whole install. Confirm the command is on your PATH:

Start XORCISE

1

Check your host

doctor reports every prerequisite and prints the exact fix for anything that is missing or wrong.
Output
Before you have ever started XORCISE, the data-directory line is expected and doctor exits 1. The next step creates the directory. Any other is real, and its remediation text tells you what to do.
2

Start it

Output
The first start creates ~/.xorcise, writes a starter config, and prepares the database, so it takes longer than later ones. Ports move up to the next free port when something else holds them, so use the URL up prints rather than assuming 3001.Running xorcise up again while XORCISE is already running prints already running — UI at <url> and exits 0. Re-running it is safe.
3

Open the web UI

Open the URL from the previous step in your browser. xorcise ui prints it again at any time.On a fresh install the home page is a Get started checklist. It becomes the Dashboard once you have your first run.
4

Confirm it is healthy

Output
status probes the REST API, the OTLP receiver, and the Docker daemon, and exits 1 if any of them is down.
The Get started page showing the four-step checklist complete and a readiness banner

The Get started page once XORCISE is up. The readiness line is the fastest way to confirm the install is sound before you create a run.

Stop XORCISE

down stops XORCISE, removes leftover mission containers, and tears down the local mission network. It keeps your config, your API keys, your installed missions, and every run and result. xorcise down --keep-data stops XORCISE and leaves everything else running, including the local mission network.
xorcise down --purge deletes all of ~/.xorcise — your config, your API keys, your installed missions, and every run and result. It asks for confirmation unless you add --yes, and in a non-interactive shell without --yes it refuses and exits 2.

Next steps

Your first run

Register an agent, pick a mission, and end holding a real score.