Skip to content

Pre-release. HareBox is a working local build with no public service yet. Statuses on every feature say what runs today; speed and reliability figures are targets until measured. Status

Hybrid local and cloud agents

Keep your coding agent on your laptop and send heavy builds, Docker stacks and parallel tests to HareBox, so the laptop stays quiet.

For Developers using Claude Code, Codex or Cursor locally

Why it pays

A quiet laptop Builds, containers and test matrices run on 4 to 16 vCPUs elsewhere, not on your battery.
The agent already knows how HareBox ships an agent skill, llms.txt and an AGENTS.md template for local agents.
Parallel when it helps Fork a warmed machine to run test shards or alternative fixes side by side.

Step by step

Tell your local agent about HareBox
Sign the CLI in, then paste HareBox's AGENTS.md template into your repo's AGENTS.md or CLAUDE.md and install the HareBox skill, both from the docs.
CLI
```
harebox login --key-stdin < ~/.harebox-key
harebox doctor
```
Push your working tree to a sandbox
Copies the project, skipping .git and node_modules.
CLI
```
harebox new --name build --size large
harebox push current .
```
Run the heavy work there
Your agent calls these itself, and gets JSON back when it pipes the output.
CLI
```
harebox exec current -- docker compose up -d
harebox exec current -- npm run test:all
```
Stop it when the session ends
The disk is kept free for 14 days, ready for tomorrow.
CLI
```
harebox stop current
```

Tips

Ask your agent to add --budget to any prompt it sends to a remote harness.
Use labels such as owner=you so harebox list --label owner=you finds your machines.
Prefer harebox exec for single commands; it returns the command's own exit code.

Related use cases