Every agent on a machine

Each coding agent connects to spacesheep on its own, and each one asks you to sign in on its own: eleven machines with five agents each is about fifty sign-ins. One command per machine connects all of them through a single key instead:

npx -y spacesheep@latest install

It signs the machine in once (one link to approve, on any device), then points every agent it finds at spacesheep mcp, a small local server that uses that key: Claude Code (every account on the machine), Codex, Gemini CLI, Antigravity, Cursor, Windsurf, VS Code and opencode. It also puts the /sheep skill where each of them reads skills. Restart the agents that are open, and they have the tools.

Many machines

From a machine that's already set up, the others take one line, over ssh:

npx -y spacesheep@latest install --ssh lab-1,lab-2,gpu-box

Each machine gets its own key, sent over the ssh connection and never shown on screen, so one machine can be revoked in Settings → API keys without touching the rest. With no ssh, run install on each machine; --code ssc_… (from /start) or --key ss_… signs one in with no browser.

What it changes

• An entry that already reached spacesheep (the server's URL, under any name) is replaced, never doubled, so no tool shows up twice. Everything else in each config file stays as it was; a file with comments in it is left alone and named.
• The tools come live from the server, so a new tool needs no reinstall. Run install again to refresh the skill.
• npx spacesheep mcp status shows which agents go through it; npx spacesheep mcp uninstall takes it back out. --only codex,cursor limits either, --dry-run shows what would change.
• Claude Code's spacesheep plugin brings a connection of its own. If /mcp lists a second spacesheep that asks you to sign in, switch that one off there.