Skip to main content
HoloDesktop CLI stores local state under:
Treat this directory as sensitive. It can contain credentials, identity metadata, instructions, skills, screenshots, and run logs.

​
Core paths

​
Runtime cache

When hai-agent-runtime is not on PATH, HoloDesktop CLI downloads the pinned runtime version to:
The download is sha256-verified before install. On macOS, the executable lives inside the downloaded app bundle:
HoloDesktop CLI resolves runtime binaries in this order:
  1. hai-agent-runtime on PATH;
  2. managed install under ~/.holo/runtime/;
  3. download-on-first-run.

​
Logs

Runtime startup logs are written under:
The file name includes the agent API port:
Use these logs for startup failures, runtime crashes, model backend errors, port conflicts, and permission-looking errors.

​
Run artifacts

Default run artifacts live under:
Override the run directory for a single CLI run:
The most important file is:
Each line is one runtime event. Observation events can include base64 JPEG screenshots of the visible desktop. Do not publish run directories without reviewing them.

​
Token files

When HoloDesktop CLI spawns a runtime and no explicit HAI_AGENT_RUNTIME_API_TOKEN is set, it generates a bearer token and publishes it locally so other local clients can attach to the same runtime:
The token file is removed when the owning client closes the spawned runtime.

​
Skills

Skills are installed under:
Each skill directory name becomes the skill name HoloDesktop CLI sees. Keep directory names lowercase and hyphenated. To author skills, memories, and rules, see Customize with skills, memories, and rules. Bundled skills can be seeded automatically by the client, and examples may install their own skills. The expense-report example installs:

​
Host config files

Host-specific config locations depend on the host. For Claude Code, project-local MCP config is associated with the workspace where you run:
Run install commands from the workspace where you expect the host to discover HoloDesktop CLI.