Connect Codex to Homespun

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.

That is the whole setup for Codex. It installs the Homespun CLI, gets you signed in, and then has the full command surface: deploy an app, read its data back, watch it live.

Prefer to run the commands yourself? They are on the Homespun CLI page, which is the same setup done by hand.

Nothing to edit in ~/.codex/config.toml: the skill installer writes where Codex already looks, so the setup is the same three commands every other coding agent runs.

Sign-in is a browser round trip from homespun agent register --name home, so there is no API key or client secret to keep anywhere.

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.