Use froog from your coding agent

Claude Code, Codex, Cursor or any agent on your computer can start and drive sandboxes with the froog CLI, the same as you. Give it three things: the signed-in CLI, the docs and a short rule that says when to use a sandbox. Or connect froog as an MCP server and the agent gets sandboxes as tools.

1. The CLI. Install it as above. An agent has no browser, so sign it in with an API key from the dashboard: echo "$FROOG_API_KEY" | froog login, or just set FROOG_API_KEY in its environment.

2. The docs. froogcorp.com/llms.txt is a short index with the key facts, and froogcorp.com/llms-full.txt (also at froogcorp.com/docs.md) is this whole page as Markdown (about 30,000 tokens). An agent that speaks MCP can search and read them as tools instead, through the docs MCP server: no key, no account.

$ claude mcp add --transport http froog-docs --scope user https://api.froogcorp.com/docs-mcp
$ codex mcp add froog-docs --url https://api.froogcorp.com/docs-mcp
# or on stdio, from the docs built into the CLI (no network):
$ claude mcp add froog-docs -- froog mcp --docs

For Cursor, put { "mcpServers": { "froog-docs": { "url": "https://api.froogcorp.com/docs-mcp" } } } in ~/.cursor/mcp.json. Its tools: search_docs (query, limit up to 20, default 5: the sections that mention the words, best first, with the matching lines), read_docs (section: one section in full, by its title or the start of it) and list_docs.

Skills. The skill pack installs froog skills for Claude Code, Codex, Cursor and the other agents the skills CLI knows:

$ npx skills add https://froogcorp.com

It has froog-cli (the everyday commands), froog-ci (tests and builds with froog run, GitHub Actions), froog-sandbox-per-user (a product that gives each user a sandbox through the API), froog-desktop (computer use, watching, recording and embedding the desktop) and froog-parallel-agents (fork a prepared sandbox, one agent per copy). --skill froog-ci installs one. They are published at froogcorp.com/.well-known/agent-skills/. To install only the main skill by hand, for Claude Code:

$ mkdir -p ~/.claude/skills/froog && curl -fsSL https://froogcorp.com/skill.md -o ~/.claude/skills/froog/SKILL.md

Other agents that read skills (Codex, Cursor) take the same file in their own skills folder.

3. A rule. Put this in AGENTS.md (Codex, Cursor and most agents) or CLAUDE.md (Claude Code) in your project:

## Cloud sandboxes (froog)

Use a froog sandbox for builds, tests, untrusted code, Docker and long jobs. Don't run them on this computer.
Docs: https://froogcorp.com/llms.txt. Prices and limits: run `froog limits`; never quote prices from memory.

- Create: `froog new task-1` (returns when SSH works; `--json` prints the sandbox as JSON)
- Run: `froog exec task-1 -- 'cd app && npm test'` (exits with the command's exit code; `--timeout` up to 3600 s)
- Long job or server: `froog exec task-1 --detach -- 'npm run dev'`, then `froog logs task-1 JOB -f`, `froog kill task-1 JOB`
- Past output, also while stopped: `froog history task-1`, `froog history task-1 CMD_ID`
- One-off: `froog run -- npm test` (a fresh sandbox with this folder; deleted after, exits with the command's code)
- Files: `froog push task-1` (this folder to ~/FOLDER), `froog scp -r ./app task-1:app`, or `git clone` inside the sandbox
- Public URL for a port: `froog host task-1 3000`
- Always pass the sandbox name.
- When done: `froog stop task-1` (keeps the disk 14 days) or `froog delete task-1 --yes` (erases it)