Use HoloDesktop CLI from the terminal

Running a task from the terminal is the most direct way to use HoloDesktop CLI, and the quickest way to check it works before you wire it into an agent host. One holo run and the agent is operating your desktop.

Before you start

Complete the Quickstart, then choose a hosted or local model. For hosted mode:

holo whoami

For local mode, make sure your OpenAI-compatible server is running.

Run a task

Hosted mode uses H Company’s Models API:

holo run "Open TextEdit and write a short note saying HoloDesktop CLI is installed"

Local mode uses your server:

holo run \
  --base-url http://localhost:8000/v1 \
  "Open TextEdit and write a short note saying HoloDesktop CLI is installed"

Add --model when the backend needs a specific model. For hosted mode, use H Company API model IDs such as holo3-1-35b-a3b or holo3-122b-a10b:

holo run \
  --model holo3-1-35b-a3b \
  "Open TextEdit and write a short note saying HoloDesktop CLI is installed"

Local mode uses the model ID exposed by your local server. For example, a server running the Holo 3.1 35B checkpoint might expose Hcompany/Holo-3.1-35B-A3B.

holo run \
  --base-url http://localhost:8000/v1 \
  --model Hcompany/Holo-3.1-35B-A3B \
  "Open TextEdit and write a short note saying HoloDesktop CLI is installed"

Useful options

Option	Use it when
`--base-url`	You want local mode with an OpenAI-compatible server
`--model`	Your hosted or local backend needs a specific model ID
`--max-steps`	You want to cap how many agent steps the CLI can take
`--max-time-s`	You want a wall-clock timeout
`--runs-dir`	You want run event logs somewhere other than `~/.holo/runs/`
`--profile`	You want per-step timing output at the end of the run
`--quiet`	You only want the final answer printed

Write good task strings

The agent only sees the task string you pass to holo run. Include the app, the account or workspace when it matters, the action to take, and what success looks like. Good:

holo run "Open Calendar, show today's events, and report each event with its time and title. Do not create or edit anything."

Too vague:

holo run "What's on today?"

Check it worked

The task prints progress in the terminal, then a final answer. Run logs are written under:

~/.holo/runs/

Runtime startup logs are written under:

~/.holo/logs/

What’s next

Use MCP when you want Claude Code, Cursor, Codex, or another host to call the CLI as a tool.

Getting Started

Integrations

How-to guides

Reference

Examples

Use HoloDesktop CLI from the terminal

Before you start

Run a task

Useful options

Write good task strings

Check it worked

What’s next

​Before you start

​Run a task

​Useful options

​Write good task strings

​Check it worked

​What’s next

Before you start

Run a task

Useful options

Write good task strings

Check it worked

What’s next