Install the Homespun CLI

Set me up with Homespun. First check whether you can run shell commands. If you can: run `npm i -g @homespunapps/cli`, then `homespun agent register --start --name home`, and show me the approval link it prints. Once I say I have approved it, run `homespun agent register --resume`, read https://homespun.dev/skills/homespun/SKILL.md and ask me what app I want to build. If you did not actually run a command and see its output, say so instead of guessing. If you cannot run commands: tell me to open https://homespun.dev/connect/claude if I use Claude, or to add a custom MCP connector with the URL https://homespun.dev/mcp in any other assistant. When I say it is connected, ask me what app I want to build.

The CLI is the option for people who would rather run things themselves: it deploys from a directory, streams live events with homespun watch, and gives any coding agent the full command surface without an MCP connector at all. It needs Node 20 or newer.

Prefer to do it by hand? Same setup, below. The sign-in step differs on purpose: at your own terminal homespun agent register waits for you and needs no second command, while the prompt uses the two-phase form so the agent can hand you the link instead of holding the terminal open.

1. 1

   Install the CLI

   Install it globally with npm. The binary is called homespun.

   npm i -g @homespunapps/cli

   Copy
2. 2

   Sign in

   Register an agent. This opens a browser for the device-authorization sign-in and writes the resulting key to your Homespun config, so you only do it once per machine.

   homespun agent register --name home

   Copy
3. 3

   Teach your agent the CLI

   Install the Homespun skill into your coding agent. It documents every command, and the relay serves the current copy, so it does not go stale.

   npx skills add homespunapps/homespun --skill homespun

   Copy

   Already installed? homespun skill show prints the same reference from the relay.

This is the route every coding agent takes: Claude Code, Codex, Cursor and Antigravity CLI each get the same one-line prompt on their own page. Chat apps with no terminal use the connector instead, on Claude and ChatGPT. Full command reference on the Homespun docs site.

If something goes wrong

The two most common snags are a blocked pop-up (the sign-in opens in a new window) and a shell that cannot find the homespun binary after installing it. The full troubleshooting list covers the rest, and the docs site explains what a connection can and cannot do.

What to build first

Describe what you want in your own words and your AI builds it. If you would rather start from something proven, install one from the template gallery and change it from the chat.