> ## Documentation Index > Fetch the complete documentation index at: https://docs.openhome.com/llms.txt > Use this file to discover all available pages before exploring further. # OpenHome CLI > Build, push, test, and deploy OpenHome Abilities from your terminal, your favorite IDE, or an AI coding agent — scaffold from a template, push to your account, and call your Agent by voice. The **OpenHome CLI** lets you build and manage Abilities from your terminal — or your favorite IDE, or an AI coding agent. Scaffold a new Ability from a template, push it to your account, set its trigger words, and voice-test it against your Agent. OpenHome's Dashboard includes a **Live Editor** for performing these actions in the browser — editing an Ability's code, setting its trigger words, and testing it against your Agent. The CLI provides the same workflow outside the browser, so you can stay within your own editor and tooling. As a standard command-line tool, the CLI can also be driven by AI coding agents such as **Claude Code** or **Codex**, or used inside agentic IDEs such as **Cursor** and **Antigravity**. This makes it a fast loop for **build → push → test → deploy** cycles. The CLI lives inside the open-source [`openhome-dev/abilities`](https://github.com/openhome-dev/abilities) repository. ## Install and Set Up Install the CLI using one of the two methods below. **One-line install (macOS and Linux)** is the quickest way to get started. Run: ```bash theme={"system"} curl -fsSL https://app.openhome.com/install.sh | sh ``` This installs the OpenHome CLI and makes it available in your terminal. The one-line installer is currently in **beta** and may not work in every environment. If it fails, install from the repo using the method below and report it on [Discord](https://discord.gg/openhome). **Installing from the repo** is the right choice if you are contributing to the abilities repo or working with Ability source directly. It requires Python 3.10 or newer: ```bash theme={"system"} git clone https://github.com/openhome-dev/abilities.git cd abilities python3 -m venv cli/.venv source cli/.venv/bin/activate # macOS / Linux cli\.venv\Scripts\activate # Windows pip install -e cli cp .env.example .env ``` With either method, the OpenHome CLI becomes available from your terminal. Authenticate the CLI with your OpenHome account: ```bash theme={"system"} openhome login ``` Paste your API key when prompted. Find it in the Dashboard under [Settings → API Keys](https://app.openhome.com/dashboard/settings) → **OpenHome API Key**. Your credentials are saved locally, so you only log in once. **Adding a session token (JWT).** `openhome login` prompts only for your API key, which is sufficient for everyday commands such as `agents`, `list`, `call`, and `chat`. Uploading an Ability's code with `openhome create` or `openhome push` may additionally require a JWT — your browser session token. If an authentication error occurs while pushing an Ability, provide a JWT explicitly: ```bash theme={"system"} openhome login --api-key --jwt ``` To get your JWT, open [app.openhome.com](https://app.openhome.com) while logged in, then either: * Run this in the browser console to copy it to your clipboard: ```js theme={"system"} copy(localStorage.getItem('access_token')) ``` * Or open **DevTools → Application → Local Storage**, find `access_token`, and copy its value. Voice calls (`openhome call`) use the `mpv` player and PortAudio. Install them so you can talk to your Agent: ```bash theme={"system"} # macOS brew install mpv portaudio # Linux sudo apt install mpv portaudio19-dev ``` ## The Core Loop Building an Ability with the CLI follows a repeatable loop: scaffold it from a template, implement your logic, push your code to test it, and commit a version once it works. Each step is a single command, so you can iterate quickly without opening the Dashboard. ```bash theme={"system"} openhome create my-weather -t api-template ``` This scaffolds the Ability into your local `user/` workspace and pushes the initial version directly to your account, where it appears in your Abilities list. You'll be prompted for trigger words and a description (or pass them with `--triggers` and `--description`). Your `user/` workspace is private to you — it's gitignored and never committed. You don't need to track Ability IDs yourself; the CLI remembers which account Ability each folder belongs to, so `openhome push` updates the right one in place instead of creating duplicates. Open `user/my-weather/main.py` and implement your Ability's logic. This file is the entry point for your Ability. As you make changes, push your current code to your account: ```bash theme={"system"} openhome push user/my-weather ``` This updates your Ability in place with the current contents of your folder. It does **not** create a committed version; it updates the working code so you can test it. Talk to your Agent and trigger the Ability with one of its trigger words: ```bash theme={"system"} openhome call # real voice call openhome chat # text chat in the terminal ``` Once the Ability behaves as intended, commit a versioned release: ```bash theme={"system"} openhome push user/my-weather --commit -m "v2: better forecasts" ``` Committing saves a numbered version of your Ability (v1 → v2 → …) that you can continue to iterate on. ## Command Reference ### Account | Command | What it does | | -------------------- | ---------------------------------------------------------------------- | | `openhome login` | Verifies and saves your credentials so you only sign in once. | | `openhome agents` | Lists your Agents with their IDs and names. | | `openhome templates` | Lists the templates and official example Abilities you can start from. | | `openhome list` | Lists your Abilities with their IDs, state, and trigger words. | ### Create & Update | Command | What it does | | -------------------------------------------- | ------------------------------------------------------------------------------------- | | `openhome create -t