Skip to main content
Use the CLI to run one desktop task from a terminal, script, or local development loop. It is also the quickest way to check HoloDesktop CLI before you install it into an agent host.

​
Before you start

Complete Installation, then choose a hosted or local model. For hosted mode: 
uv run holo whoami
For local mode, make sure your OpenAI-compatible server is running.

​
Run a task

Hosted mode uses H Company’s Models API: 
uv run holo run "Open TextEdit and write a short note saying HoloDesktop CLI is installed"
Local mode uses your server: 
uv run 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: 
uv run 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. 
uv run 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

OptionUse it when
--base-urlYou want local mode with an OpenAI-compatible server
--modelYour hosted or local backend needs a specific model ID
--max-stepsYou want to cap how many agent steps the CLI can take
--max-time-sYou want a wall-clock timeout
--runs-dirYou want run event logs somewhere other than ~/.holo/runs/
--profileYou want per-step timing output at the end of the run
--quietYou only want the final answer printed

​
Write good task strings

HoloDesktop CLI receives 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: 
uv run 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: 
uv run 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 HoloDesktop CLI as a tool.