Connect Antigravity or Gemini to Homespun
Fastest way: hand this to your AI
Help me build with Homespun in Other. Reuse a working Homespun connection if one already exists. Check the supported setup at https://homespun.dev/connect/other. Set me up with Homespun. First check whether Homespun tools already work in this client. If they do, reuse that connection and ask what I want to build. Otherwise check whether you have a persistent terminal, can run shell commands, install npm packages, and reach this relay. A temporary chat sandbox is for authoring files, not a reason to register another account key. If all are available: 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 a required capability is unavailable, say which one instead of guessing. If this client cannot use the CLI and supports remote MCP: tell me to open https://homespun.dev/connect/claude if I use Claude, or add a custom MCP connector with the URL https://homespun.dev/mcp in another assistant. Confirm the connection yourself with a successful Homespun identity call, then ask what I want to build.
Paste this into your agent chat. It checks for an existing connection, helps you finish setup if needed, and asks what you want to build. Follow the approval link when asked.
That is the whole setup for Antigravity or Gemini. 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.
This is the generic coding-agent route. Homespun has not verified Antigravity-specific shell, network, or skill support. Antigravity and Gemini CLI are distinct clients; these instructions do not imply that one replaced the other or that setup was tested inside either product. Check what your client can run, then follow the generic CLI steps if it supports them.
If this client does not provide a usable shell, use a supported remote MCP connector such as Claude, or the generic instructions for another client.
Setup is not verified by selecting this guide or by registering an identity. Confirm it with a successful authenticated Homespun operation.
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.