# Set up Hivra from your coding agent

> Instructions for AI coding agents (Claude Code, Codex, Cursor, Gemini CLI and others). Your person asked you to set them up on Hivra. Follow these steps. Prompt they paste: "Set me up on Hivra so I have an AI agent running in the cloud. Read https://hivra.cloud/setup.md and follow it."

Hivra gives an AI agent a cloud computer of its own, so it keeps running when their laptop is closed. They chat with it in the browser, and it can browse, run code and run scheduled jobs.

## Ground rules

- A person signs in and presses Launch. You cannot do that for them: never create accounts, never ask for their password, never try to pay.
- Every computer that Hivra Cloud runs for you needs a paid plan, from $9.99 a month for 2 vCPU and 4 GB of RAM. A free account works with a computer or server you connect yourself. There is a 7-day money-back guarantee on card payments. Say this before you send them to Launch, so it is not a surprise.
- API keys go into Hivra's own page, never into this chat, a file or a commit.
- Ask before you push code anywhere.

## 1. Pick the agent

If they already said which agent they want, use it. If they asked you to move yourself or your current work to the cloud, pick your own kind (Claude Code → `claude-code`, Codex → `codex`). Otherwise ask one short question, with `hermes` as the default.

| id | agent | good for |
| --- | --- | --- |
| `hermes` | Hermes | an everyday assistant that remembers, browses and runs scheduled jobs (the default) |
| `claude-code` | Claude Code | Anthropic's coding agent, for moving coding work to the cloud |
| `codex` | Codex | OpenAI's coding agent |
| `openclaw` | OpenClaw | an assistant the person talks to from Telegram, WhatsApp, Discord or Slack |
| `agent-zero` | Agent Zero | an agent that takes a goal, plans it and works through it |

More agents, and what each one suits: https://hivra.cloud/agents

## 2. Send them to Launch

Use `venice-key` only for Hermes or Codex if they want to use their own Venice API key. Other agents in this list do not accept a Venice key on Launch.

Build the Launch link for what your person chose and give it to them:

```
https://hivra.cloud/dashboard/launch?agent=<agent id>&inference=venice&ref=agent-setup
```

For example, Claude Code on Hivra credits: https://hivra.cloud/dashboard/launch?agent=claude-code&inference=venice&ref=agent-setup

- `inference=venice` selects Hivra credits. Leave `inference` out to let them choose from the options on Launch.
- Open the link in their browser if you can (`open <url>` on macOS, `xdg-open <url>` on Linux, `start <url>` on Windows). Otherwise print it and ask them to open it.
- Tell them: sign in or create an account, check the choices, press Launch. Setup takes a few minutes and the agent's page shows progress. Their agent then appears under Agents at https://hivra.cloud/dashboard/agents.

## 3. Carry your work over (only if they want it)

If they want the cloud agent to pick up what you are working on now:

1. Ask before pushing. Then commit and push your work to a branch on GitHub (or another git host they use).
2. Write a short handoff note: the repository URL and branch, what is done, what is next, how to run it and its tests, and anything they decided. Leave out every secret and key.
3. Tell them to paste the note as their first message in the new agent's chat. To let the agent push to GitHub, they can connect GitHub from the agent's page.

## 4. Finish

Tell them in two or three sentences what you set up, the link to open it, and that it keeps running in the cloud. Managing it (model, updates, sleep, deleting it) is on the agent's page under Manage.

## Help

- Agents: https://hivra.cloud/agents
- Pricing: https://hivra.cloud/pricing
- Everything else: https://hivra.cloud/llms.txt
