burrow

KO | EN

gitlite — search

#hacktoberfest #golang #deep-learning #docker #macos #nodejs #windows #cli #kubernetes #awesome-list #vue #pytorch #mcp #ios

(★ 11)

OS-isolated sandbox runtime for coding agents

burrow 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Burrow

OS-isolated sandbox runtime for coding agents.

[![CI](https://github.com/jayminwest/burrow/actions/workflows/ci.yml/badge.svg)](https://github.com/jayminwest/burrow/actions/workflows/ci.yml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://raw.githubusercontent.com/jayminwest/burrow/main/LICENSE)

> Each agent digs its own contained space. Coding work happens in burrows, not on the host.

Burrow spins up many sandboxed workspaces in parallel, runs *any* CLI-based coding agent inside them, persists run state, streams events, and gives the user a CLI to steer running agents and observe what they're doing. The host stays clean: no language toolchains polluting `~`, no half-installed deps, no risky agent commands escaping to the user's filesystem.

V1 is local-first and single-user, with `bwrap` (Linux) and `sandbox-exec` (macOS) as the sandbox primitives — no Docker, no daemon. Remote providers are a post-V1 implementation, not a rewrite.

## Install

```bash
bun install -g @os-eco/burrow-cli
# or: npm install -g @os-eco/burrow-cli
```

CLI binaries: `burrow` and `bw`.

## Quickstart

```bash
$ cd ~/projects/web-app
$ burrow init claude                  # scaffold burrow.toml + register claude-code
$ burrow doctor                       # confirm sandbox primitive + toolchains
$ burrow up                           # spin up a project burrow
✓ burrow bur_a3f9 up (workspace: ~/.local/share/burrow/sessions/bur_a3f9/workspace)

$ burrow prompt bur_a3f9 "Add input validation to the login endpoint"
[stream of agent events...]
✓ run completed in 2m14s

# parallel exploration
$ burrow fork bur_a3f9 --task "try a redis-backed approach"
$ burrow prompt bur_b21c "Implement the redis caching layer"

# observe + steer
$ burrow events --follow              # interleaved live events from every active burrow
$ burrow send bur_b21c "stop and write tests first"

# tear down + archive
$ burrow stop bur_b21c
$ burrow destroy bur_b21c             # archives events to the data dir
```

See [`examples/`](examples) for a runnable walkthrough plus a custom-agent recipe.

## What you get

- **Native sandboxing.** `bwrap` on Linux, `sandbox-exec` on macOS. No Docker, no container images, no daemon. The host filesystem outside the workspace is unreachable; the network policy is one of `none | restricted | open`.
- **Any CLI agent.** Built-in runtimes for `claude-code`, `sapling`, `codex`, `pi`, and `pi-chat`. New agents land via a declarative `[[agents]]` stanza in `burrow.toml` — zero core code changes.
- **Parallel work.** A project burrow plus N task burrows, each on its own git worktree, running concurrently behind a per-burrow FIFO queue.
- **Steerable runs.** `burrow send <id> "..."` queues a steering message; the next agent turn delivers it.
- **Durable state.** `bun:sqlite` (WAL) persists burrows, runs, events, and inbox messages. `kill -9` leaves the system recoverable; `burrow destroy` archives the full event log to NDJSON.
- **First-class observability.** `burrow logs <id> --follow` and `burrow events --follow` stream NDJSON events from one or every burrow.
- **Project contract.** [`burrow.toml`](SPEC.md#17-burrowtoml-schema) declares toolchain versions, env requirements, secrets references (op://, env, defaults), network policy, and `[[agents]]`. `burrow doctor` gates `burrow up` on those checks.
- **`burrow ship`.** Build + deploy artifacts via the `tarball`, `docker`, or `fly` ShipTargets — the same shape a future `aws` target would land into.
- **Library-first.** Every CLI command is a thin wrapper over the public `Client` class. `import { Client } from "@os-eco/burrow-cli"` to drive Burrow from TypeScript.

## CLI surface (V1)

```bash
burrow init [agents...]                  # scaffold burrow.toml
burrow doctor [--project <root>]         # health check (sandbox + toolchains + agents)
burrow upgrade                           # print the upgrade command for the installed binary
burrow completions <shell>               # bash | zsh | fish

burrow up                                # spin up a project burrow against the cwd
burrow fork <id> --task "<desc>"         # task burrow on a fresh branch
burrow attach <id>                       # re-activate a stopped burrow
burrow list / show / stop / destroy

burrow prompt <id> "<task>"              # dispatch the default agent (or --agent <id>)
burrow send <id> "<message>"             # queue a steering message
burrow chat <id>                         # interactive REPL — one stdin line per message

burrow logs <id> [--follow]              # one burrow's event log
burrow events [--follow]                 # every active burrow, interleaved
burrow watch [--json]                    # multi-burrow TUI dashboard (NDJSON snapshots with --json)

burrow agents list / show / validate / add
burrow serve [--socket PATH | --port N] [--no-auth]   # HTTP API daemon (see below)
burrow ship [<id>] --target tarball|docker|fly
```

Every command supports `--json` for machine-readable output and `--quiet`/`--verbose` for log level. Exit codes: `0` success, `1` generic, `2` not found, `3` invalid input, `4` runtime/sandbox error.

Full design rationale, the `burrow.toml` schema, and the deferred V2 surface live in [SPEC.md](SPEC.md).

## HTTP API (`burrow serve`)

For driving Burrow from another process — the warren control plane, a future web UI, or any cross-process orchestrator — `burrow serve` exposes the Library API over HTTP. Routes mirror the `Client` namespaces 1:1 (`POST /burrows`, `GET /burrows/:id/events?follow=1`, …) so the in-process Library remains the source of truth. Streaming surfaces (`/events`, `/runs/:id/stream`, `/watch`) emit NDJSON over chunked HTTP byte-for-byte equal to the matching `--json` CLI output.

```bash
# unix socket (default; <cacheDir>/burrow.sock)
$ BURROW_API_TOKEN=$(openssl rand -hex 32) burrow serve --json
{"socket":"/Users/you/Library/Caches/burrow/burrow.sock","auth":"bearer"}

$ curl --unix-socket /Users/you/Library/Caches/burrow/burrow.sock \
       -H "Authorization: Bearer $BURROW_API_TOKEN" \
       http://localhost/burrows

# localhost TCP (opt-in; loopback only)
$ burrow serve --port 4040 --json
```

From TypeScript, swap the in-process `Client` for `HttpClient` without touching call sites:

```ts
import { HttpClient } from '@os-eco/burrow-cli';

const client = new HttpClient({
  transport: { kind: 'unix', path: '/Users/you/Library/Caches/burrow/burrow.sock' },
  token: process.env.BURROW_API_TOKEN,
});

const burrows = await client.burrows.list();
for await (const evt of client.events.tail({ burrowId: burrows[0].id })) {
  console.log(evt);
}
```

Bearer auth from `BURROW_API_TOKEN` is required by default; `--no-auth` bypasses for loopback-only use. Single-user posture — multi-user is an explicit non-goal. See [SPEC §27](SPEC.md#27-http-api-burrow-serve) and `sd plan show pl-5b40` for the full design. For running `burrow serve` as a long-lived daemon (systemd unit, Fly Machine, in-container with the four bwrap flags), see [DEPLOY.md](DEPLOY.md).

The server self-describes via an OpenAPI 3.1 document at `GET /openapi.json` (auth-required) so external consumers can codegen typed clients without hand-rolling against the wire format. Point a browser at `GET /openapi.html` (auth-exempt) for a Scalar-rendered API reference.

## Linux dev container

Linux is burrow's canonical isolation target — the deploy target is a Linux container running `bwrap`. macOS contributors can exercise that exact path locally via the Docker-based dev container under [`.devcontainer/`](.devcontainer):

```bash
docker compose -f .devcontainer/compose.yml up -d
docker compose -f .devcontainer/compose.yml exec dev bash

# inside the container
bun install
bun test && bun run lint && bun run typecheck
bw up && bw fork <id> --task "..."   # bwrap nests cleanly
```

VS Code and JetBrains pick up `.devcontainer/devcontainer.json` automatically (Reopen in Container).

### Why the four `security_opt` / `cap_add` flags

Vanilla `docker run` does **not** work — Ubuntu 24.04 hosts (the most common Docker Desktop and stock-distro target) ship `kernel.apparmor_restrict_unprivileged_userns=1` by default, which blocks the user-namespace creation bwrap relies on. The minimum non-privileged invocation needs all four:

| Flag | Why |
|---|---|
| `security_opt: apparmor=unconfined` | Lifts the host AppArmor profile that blocks `unshare(CLONE_NEWUSER)` from inside the container. Without it, bwrap exits with `EPERM` at unshare. |
| `security_opt: seccomp=unconfined` | Docker's default seccomp profile blocks several syscalls bwrap needs (e.g. `clone3` argument shapes for new namespaces). |
| `security_opt: systempaths=unconfined` | Unmasks `/proc` inside the container so bwrap can mount its own `/proc` in the new pid+mount namespace. Without it: `Can't mount proc on /newroot/proc`. |
| `cap_add: SYS_ADMIN` | Lets bwrap bring up `lo` inside its new netns (`RTM_NEWADDR` needs `CAP_NET_ADMIN`, which `SYS_ADMIN` implies). Without it: `Failed RTM_NEWADDR`. |

`--privileged` works as a fallback but relaxes the outer container far more than necessary. The four targeted flags are the minimum that lets nested-userns bwrap succeed.

Recipe verified on Ubuntu 24.04 host with Docker 28.4.

## Ecosystem

Burrow is part of the [os-eco](https://github.com/jayminwest/os-eco) ecosystem. It does not orchestrate agents — that's [Mycelium](https://github.com/jayminwest/mycelium). It runs whatever agent the orchestrator hands it, in isolation.

## Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md). For security issues, see [SECURITY.md](SECURITY.md).

## License

[MIT](LICENSE)

burrow

burrow 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

burrow

burrow 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README