> ## Documentation Index
> Fetch the complete documentation index at: https://hub.hcompany.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Paths and files

> Local files, logs, runtime cache, skills, and run artifacts used by HoloDesktop CLI.

HoloDesktop CLI stores local state under:

```text theme={null}
~/.holo/
```

Treat this directory as sensitive. It can contain credentials, identity metadata, instructions, skills, screenshots, and run logs.

## Core paths

| Path                       | Purpose                                                 |
| -------------------------- | ------------------------------------------------------- |
| `~/.holo/.env`             | Hosted-mode `HAI_API_KEY` written by `holo login`.      |
| `~/.holo/profile.json`     | Cached identity metadata used by `holo whoami`.         |
| `~/.holo/runtime/`         | Managed `hai-agent-runtime` installs.                   |
| `~/.holo/logs/`            | Runtime startup and stderr logs.                        |
| `~/.holo/runs/`            | Runtime run artifacts.                                  |
| `~/.holo/desktop.lock`     | Advisory lock so one desktop task runs at a time.       |
| `~/.holo/skills/`          | Installed HoloDesktop CLI skills.                       |
| `~/.holo/settings.json`    | Client settings such as seeded skills.                  |
| `~/.holo/agents.md`        | Standing HoloDesktop CLI instructions.                  |
| `~/.holo/memories.md`      | General memories loaded into HoloDesktop CLI sessions.  |
| `~/.holo/holo-memories.md` | HoloDesktop CLI-specific memories loaded into sessions. |
| `~/.holo/rules.md`         | Rules loaded into sessions.                             |

## Runtime cache

When `hai-agent-runtime` is not on `PATH`, HoloDesktop CLI downloads the pinned runtime version to:

```text theme={null}
~/.holo/runtime/<version>/
```

The download is sha256-verified before install. On macOS, the executable lives inside the downloaded app bundle:

```text theme={null}
~/.holo/runtime/<version>/hai_agent_runtime.app/Contents/MacOS/hai-agent-runtime
```

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:

```text theme={null}
~/.holo/logs/
```

The file name includes the agent API port:

```text theme={null}
hai-agent-runtime-18795.log
```

Use these logs for startup failures, runtime crashes, model backend errors, port conflicts, and permission-looking errors.

## Run artifacts

Default run artifacts live under:

```text theme={null}
~/.holo/runs/
```

Override the run directory for a single CLI run:

```bash theme={null}
holo run \
  --runs-dir /tmp/holo-runs \
  "Open TextEdit and write the word test"
```

The most important file is:

```text theme={null}
events.jsonl
```

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:

```text theme={null}
~/.holo/agent-token-<port>
```

The token file is removed when the owning client closes the spawned runtime.

## Skills

Skills are installed under:

```text theme={null}
~/.holo/skills/<slug>/SKILL.md
```

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](/holo-desktop-cli/how-to/customize).

Bundled skills can be seeded automatically by the client, and examples may install their own skills. The expense-report example installs:

```text theme={null}
~/.holo/skills/expense-report/SKILL.md
```

## 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:

```bash theme={null}
holo install claude-code
```

Run install commands from the workspace where you expect the host to discover HoloDesktop CLI.