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

Use from your coding agent

Works locallyWorks in the local build today.

Your coding agent on your laptop, such as Claude Code, Codex or Cursor, can drive HareBox through the CLI: start machines, run builds and tests in them, fork them, and stop them, while your laptop stays quiet.

1. Give it the docs

Add HareBox's docs as an MCP server, so the agent searches and reads current docs instead of guessing:

claude mcp add harebox-docs -- harebox mcp docs

For other agents, register harebox mcp docs as a stdio MCP server. It has two tools, search_docs and read_doc, needs no key, and reads the published docs, so it's always current.

2. Teach it the rules

  • Copy AGENTS.template.md into your repository as AGENTS.md, or into CLAUDE.md.
  • Install the HareBox skill where your agent loads skills.
  • Point it at llms.txt. Everything it needs is reachable from there.

3. Let it work

The CLI prints JSON whenever its output is piped, and every error has a fix that says what to do next, so an agent can run it unattended:

harebox help --json | jq '.commands | length'

Typical requests that work well:

  • "Start a large HareBox sandbox, push this repository to it, run the full test suite there and tell me what fails."
  • "Fork the sandbox three times and try three fixes for the flaky test in parallel; keep the one that passes."
  • "Run harebox run --from ci-base -- make test and report the exit code."

Set a budget first, so a loop can't run up a bill: harebox budget new --limit 25 --action stop.

View as Markdownllms.txt for agents