Meet the new Open Home CLI: build skills and test natively in your IDE

Open Home CLI: Your AI agent should be able to build skills and test natively in your IDE. Now it can. Why It Matters The most powerful thing about voice AI isn't...

Author: Brady McKenna

Open Home CLI: Your AI agent should be able to build skills and test natively in your IDE. Now it can.

Why It Matters

The most powerful thing about voice AI isn't what it can do today  -  it's how fast it can learn new things. An ability that checks the weather. One that controls your home. One that knows your calendar. Each one a new skill, deployable in seconds.

Until now, adding those skills meant opening a browser, navigating a dashboard, uploading files manually. Every time. That friction slows everything down  -  and it makes it impossible for AI agents to participate in their own development. We built openhome-cli to remove that friction entirely. The terminal is now your entire OpenHome workflow


Installation

npm install -g openhome-cli


What You Can Do

Follow the prompts to log in with your API key and session token. Then never leave your terminal again.

Validate an ability before it ships. Deploy it with a single command. Assign it to your agent by name. Open a live chat session and watch it respond in real time. Stream logs. All of it, from the command line  -  alongside whatever coding tools you're already using.


Built for AI Automation

Every command is fully non-interactive. Machine-readable JSON output on everything. Auth via environment variables. That means Claude Code  -  or any AI agent, any CI pipeline, any automation  -  can write an ability, deploy it, assign it, and test it without you switching windows once.

And with openhome mcp, Claude Code connects to OpenHome directly as a native integration via Model Context Protocol. Your IDE isn't just where you write the code  -  it's where the whole voice AI development loop lives.

You describe what you want. The agent builds it. The CLI ships it. You talk to it.

The one human moment

There's one thing that still needs you: refreshing your session token. That's a platform-level security constraint, not a CLI limitation. We've handled it as gracefully as possible  -  the CLI warns you before it expires, tells you exactly which commands need it, and gives you the precise browser console steps to refresh it in under 30 seconds. AI agents are explicitly instructed to stop and ask you rather than retry blindly. Everything else is automated.

Start building today

npx openhome-cli


Resources

Using npx? You'll always get the latest version automatically  -  no manual update steps.

Full docs: docs.openhome.com/guides/getting-started/cli

GitHub: github.com/openhome-dev/openhome-cli

Hardware is on a waitlist, but you can build and deploy abilities today at dev.openhome.com. When your kit arrives, everything you've already built is waiting on it.

Community

Want to share what you make? Submit a PR to the community abilities repo at github.com/openhome-dev/abilities and it shows up in the OpenHome library for everyone. Want to keep it private? Just deploy with the CLI  -  your code never leaves your account.

Come find us on Discord: discord.gg/openhome

Show us what you ship!