Overview
Browse projects, follow agent activity, inspect sessions, and connect your workspace with XO Space.
XO Space is an open-source local server and browser interface for the projects and coding agents on your machine. It brings files, todos, git history, sessions, and costs into one workspace.
Space works with the agents you already use. It can send a prompt to a configured runtime through its API and read activity from supported native session stores. You can also keep working in your usual terminal or editor and use Space to inspect the results.
Screenshots in this section use fictional workspace data.
This walkthrough includes six primary tabs and the top-right Wiki resource from
revision 8267c08,
currently awaiting merge into development. The rest of the documented behavior
follows development at 5221119; technical guides identify their source
versions. The public installer follows the release branch main, which can
differ. See the UI version notes and
installation options.
What you can do
| Area | Use it to |
|---|---|
| Projects | Survey projects in Dashboard, browse rows and project drawers in List, inspect relationships in Graph, explore folders in Tree, and manage shared repositories in Sharing. |
| Timeline | Read mapped files' first Git dates or project commit days, play through the date range, and click a dot to focus its file or project in Graph. |
| Sessions | Compare available runtime telemetry, tokens, estimated costs, models, tools, and session details. |
| Inbox | Review new sessions, blocked todos, GitHub issues, sharing events, connected-service updates, and items posted by agents. |
| Wiki | Find a quick start and topic summaries, then open detailed documentation. |
| Setup | Check roots, agent readiness, watcher coverage, credentials, reporting status, and updates. |
| Connectors | Connect external accounts, choose tools available to the workspace, and configure supported polling sources. |
Space opens on Dashboard under Projects. Clicking Projects opens List.
All five project lenses keep the same Projects tab highlighted. The keyboard
shortcuts are Projects 1, Timeline 2, Sessions 3, Inbox 4, Setup 5,
and Connectors 6.
Wiki at the top right opens the local quick start and topic directory in the same tab. Its Open docs links open detailed guides in new tabs. GitHub beside Wiki opens the source repository in a new tab.
A project is a folder
Every eligible direct child folder of the configured XO projects root appears as a project. You can browse an existing repository immediately. Creating a scaffolded project through the API adds project identity, operating documents, memory folders, and portable metadata.
Space keeps three kinds of data separate:
- Your project: source files, documents, and portable
.xo/records such as project identity and todos. - Machine-local state:
.quirq/holds configuration, watcher state, project telemetry, workspace aggregates, and Inbox state. - Native agent stores: conversations remain in the runtime's own storage.
The first-run guide shows how to choose the root, create a project, and make its first piece of work visible.
Runtime support
Claude Code, Codex, OpenClaw, Hermes, and Antigravity have chat adapters and native session support. The active chat runtime is selected separately from the sources Space observes. Cursor contributes read-only session telemetry.
The Sessions dashboard currently aggregates Claude Code, Codex, and Cursor telemetry. Coverage varies by source: a missing cost or token breakdown is shown as unavailable or estimated. See runtime discovery and observability for the distinction between chat, watcher activity, and the Sessions dashboard.
Local or managed
Run Space on Linux or macOS, or inside WSL on Windows. The default local install binds to loopback, needs no XO account for local browsing, and runs while its server process is alive. Agent execution still needs the appropriate runtime and its authentication.
XO Managed Cloud provides a hosted Space. Available runtimes, credentials, integrations, and network access depend on that workspace's configuration; the shared server code does not make every deployment identical.
A signed-out local install sends no XO usage summary. Linking it with an XO credential enables a daily usage summary; sharing and connected services make additional network requests when configured. Read what is stored and reported.