Local Auto-Detection
How XO Space automatically discovers local agent CLIs, harnesses, and session paths on your machine.
When you install and boot XO Space locally, it requires zero manual agent configuration. Space automatically scans your $PATH and home directory to detect installed AI coding agent CLIs and their on-disk telemetry.
How Discovery Works
During startup, the xo-space daemon inspects your system for supported agent runtimes:
┌─────────────────────────────────────┐
│ xo-space Boot Auto-Discovery │
└──────────────────┬──────────────────┘
│
┌───────────────────────────┼───────────────────────────┐
▼ ▼ ▼
[ PATH Scan ] [ State Scans ] [ Telemetry Scans ]
• claude CLI in $PATH • ~/.openclaw/openclaw.json • ~/.cursor/projects/
• antigravity in $PATH • ~/.hermes/ • ~/.codex/sessions/
• node / npm / gh • ~/.gemini/antigravity/ • ~/.claude/projects/1. Full Agent Adapters (Chat + Telemetry)
If the CLI executable is found in your $PATH, Space attaches a full BaseAgentAdapter:
- Claude Code: Discovered via
claudeCLI binary or@anthropic-ai/claude-codenpm package. - OpenClaw: Discovered via
openclawbinary and~/.openclaw/directory. - Hermes: Discovered via
hermesexecutable. - Antigravity: Discovered via
antigravityCLI and~/.gemini/antigravity-cli/.
2. Telemetry-Only Runtimes
For IDE extensions and tools that run outside Space but store local session history, Space mounts read-only telemetry modules:
- Cursor: Reads session files from
~/.cursor/to display metrics and edit history. - Codex: Reads session logs from
~/.codex/.
Checking Detected Runtimes
You can check which runtimes Space discovered at any time via the health endpoint:
curl http://localhost:5002/health{
"status": "healthy",
"ai_provider": "claude",
"claude_cli": "/usr/local/bin/claude",
"codex_cli": "codex",
"active_sessions": 0
}If a tool is missing from your $PATH, simply install the agent CLI and restart Space (or run ./cowork-api.sh restart).