Install Space

Requirements

Use Linux or macOS. On Windows, run the installation and your agents inside WSL; native Windows is not supported. You need git and a working curl command. Docker is not required.

The installer fetches uv when needed, creates a Python 3.12 virtual environment, and installs Space's Python requirements. Other tools enable specific features:

Missing optional tools are reported at startup. They do not prevent you from browsing local projects.

Install and open

Choose a workspace directory, open a terminal there, and run:

curl -fsSL https://quirq.ai/install | sh

The command clones xo-space into that directory, creates xo-space/venv, writes initial configuration to xo-space/.env, and creates .quirq/ for local state. It prints the resolved roots, readiness checks, log paths, and browser URL.

Open http://localhost:5002/space/, or the URL printed by the installer if it selected another port. Keep the terminal running. The server runs in the foreground; Ctrl-C stops it.

Check Setup before running an agent

Open Setup in the top bar. Check the XO projects root, the machine-local state root, the active chat backend, and native session sources.

The installer defaults to claude_code, watches all supported installed runtime sources, and skips agent installation. Install and authenticate your chosen agent using its normal workflow. For example, if you use Claude Code:

npm install -g @anthropic-ai/claude-code

An existing native login can supply authentication. Setup also supports write-only credential fields for runtimes that use environment credentials. Installing Space does not supply an agent subscription, API key, or OAuth login.

See runtime discovery when an executable or session store is missing.

Understand the install directory

For a fresh install started in your workspace:

workspace/
├── xo-space/                 server checkout and Python environment
│   ├── .env                  install configuration
│   └── venv/
├── .quirq/                   machine-local configuration and telemetry
│   ├── quirq.log             server output
│   └── commands.log          external commands run by Space
├── .xo/                      portable workspace records
└── my-project/               your files and optional project .xo/ metadata

Your agents' native conversations stay in their own home directories. Project stats and session indexes are under .quirq/projects/; workspace graphs and session aggregates are under .quirq/workspace/.

Start again or update

From the workspace directory:

# Start the existing checkout without fetching an update
./xo-space/install.sh

# Update the managed checkout, then start it
curl -fsSL https://quirq.ai/install | sh

The update path preserves a checkout with local changes or one on a different branch. Read the startup message if an update is skipped. The installer does not add a system service, scheduled job, or login item.

If Setup says a restart is needed, stop and rerun a foreground install yourself. A managed deployment can support the restart action; an unsupervised local process cannot restart itself through that button.

Change configuration

The installer creates .env once and preserves later edits. Common settings are:

For an install-time override:

curl -fsSL https://quirq.ai/install | PORT=8080 sh

Exported settings override .env; settings saved through Setup may take precedence for the runtime and credentials it manages. Root selections are also persisted in roots.env. Setup shows the effective configuration, which is the useful place to check when an environment edit appears not to take effect.

Keep the state root outside project folders. The default hidden .quirq/ directly under the workspace is allowed; other nesting combinations are rejected to avoid copying projects into machine-local state during relocation.

Install from a clone

For a checkout you manage yourself:

git clone https://github.com/quirq-ai/xo-space.git
cd xo-space
./install.sh

This uses the checkout in place without fetching or resetting it. With no saved root configuration, the launch directory becomes the workspace. Choose explicit roots in Setup if you want projects elsewhere. For code changes, follow the contributor setup, which starts from development.

Remove a local install

Preview what removal would do:

./xo-space/uninstall.sh --dry-run

Then run ./xo-space/uninstall.sh when ready. It stops the server and removes managed installation/state files while preserving project folders by default. Read its summary: a checkout with local changes is kept, and native agent installations are separate from Space.

Prefer hosting instead? Open XO Managed Cloud. Otherwise continue with your first Space.