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

> ## Agent Instructions
> H Platform has four products: the Agents API (managed computer-use agents, base URL https://agp.eu.hcompany.ai/api/v2 or https://agp.hcompany.ai/api/v2 for the US), the Models API (OpenAI-compatible Holo vision-language models at https://api.hcompany.ai/v1), HoloDesktop CLI (Holo on the user's own desktop), and HoloTab (a free no-code Chrome extension that runs Holo in the user's browser, with recordable routines and schedules).
> Authenticate with a bearer API key from the HAI_API_KEY environment variable. SDKs: `pip install hai-agents` (Python, `from hai_agents import Client`) and `npm install hai-agents` (TypeScript, `import { HaiAgentsClient } from "hai-agents"`). CLI: `hai`.
> Agents do work in a browser or on a desktop; describe the task as an imperative instruction. To run a task quickly, prefer the pre-built agent `h/web-surfer-flash`. Read results from the session's `latest_answer` after it reaches a terminal status.
> Sessions are the unit of work; wait for a terminal status (completed, failed, timed_out, interrupted) before reading the answer. Use webhooks or the `changes` long-poll endpoint to follow progress.

# Paths and files

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

HoloDesktop CLI stores local state under:

```text theme={"system"}
~/.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={"system"}
~/.holo/runtime/<version>/
```

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

```text theme={"system"}
~/.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={"system"}
~/.holo/logs/
```

The file name includes the agent API port:

```text theme={"system"}
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={"system"}
~/.holo/runs/
```

Override the run directory for a single CLI run:

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

The most important file is:

```text theme={"system"}
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={"system"}
~/.holo/agent-token-<port>
```

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

## Skills

Skills are installed under:

```text theme={"system"}
~/.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={"system"}
~/.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={"system"}
holo install claude-code
```

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

## Next steps

<CardGroup cols={2}>
  <Card title="Customize the agent" icon="sliders" href="/holo-desktop-cli/how-to/customize">
    Memories, rules, and skills the CLI loads from these paths.
  </Card>

  <Card title="Security and privacy" icon="shield-halved" href="/holo-desktop-cli/security-and-privacy">
    What run artifacts can contain.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.