GPU for Agents 0.6.0: agents install it themselves

Your agent installs GPU for Agents itself

Paste one line into Claude Code, Codex, Gemini CLI or Cursor:

Set up GPU for Agents for me. I'm using Claude Code. Fetch https://gpu4agents.jambu.ai/install.md with curl and follow its steps.

The agent installs the gpu command (uv brings its own Python: nothing to install first on Linux or macOS), the skill and the MCP tools, and rents nothing. You connect your GPU account in your own terminal, so the agent never sees the key:

gpu login

Prefer a terminal? curl -fsSL https://gpu4agents.jambu.ai/install.sh | sh, or npx skills add jambuai/gpu4agents for just the skill.

Added

• install.sh: needs only curl. Installs uv if missing, then gpu4agents on a Python uv downloads when needed, removes an old jambu-gpu tool, and sets up every agent runtime it finds (--agent to pick one).
• INSTALL.md (served at /install.md): the steps an agent follows from the pasted prompt.
• gpu login: hidden prompt, checks the key against Vast.ai, saves it in ~/.gpu/credentials (mode 600). --check reports whether a working key is found; --stdin reads it from a pipe.
• gpu agent install -t codex, -t gemini and -t auto. Codex, Gemini CLI and Cursor share the skill in .agents/skills/gpu4agents/; Codex gets the MCP server in ~/.codex/config.toml, Gemini CLI in .gemini/settings.json.
• The skill is published at skills/gpu4agents/, works with npx skills add, and now covers installing, connecting the account, monitoring (status, logs, events, ls, sweep) and exit codes.

Changed

• The skill is named gpu4agents (was gpu); gpu agent install replaces the old folder it wrote before.
• Cursor gets the skill in .agents/skills/ instead of .claude/skills/.

Validated: a headless Claude Code, in an empty home with no Python tools, installed and configured everything from the one-line prompt and sent the user to gpu login without asking for the key. See docs/ACCEPTANCE.md.

Full changelog: CHANGELOG.md