Skip to content

Latest commit

 

History

History
81 lines (57 loc) · 5.08 KB

File metadata and controls

81 lines (57 loc) · 5.08 KB

sb-runtime

Lightweight agent sandbox with Cedar policy and signed receipts. One Rust binary, no Docker, no k3s, no gateway.

┌──────────────────────────────────────────────────────────────┐
│  sb exec --policy dev-safe.cedar -- /usr/bin/cat /etc/hosts  │
│                                                                │
│  1. Cedar evaluates   → allow / deny (400 µs)                  │
│  2. Ed25519 receipt   → .receipts/000001.json (tamper-evident) │
│  3. OS sandbox        → Landlock + seccomp (Linux)             │
│  4. execve            → the target command runs confined       │
└──────────────────────────────────────────────────────────────┘

sb-runtime answers a question several AGT / OpenShell users have been asking: can we get the "walls + brain + receipts" pattern without Docker/OCI/k3s/gateway infrastructure? This is a single 8 MB binary that runs on dev laptops, CI, and edge.

Status: v0.1.0-alpha.1 — design-partner preview. Linux sandbox backend works (Landlock + seccomp). macOS / Windows backends are stubs; use --allow-unsandboxed on those platforms to run with Cedar + receipts only. We're actively looking for design-partner input on the AGT provider interface and the Cedar schema for agent actions — open an issue or reply to microsoft/agent-governance-toolkit#748.

Quick start

cargo install --path crates/sb-cli    # or: cargo run -p sb-cli --
sb exec \
  --policy examples/basic/policy.cedar \
  --receipts .receipts \
  -- /usr/bin/cat /etc/hosts

sb verify .receipts/
# ✓ 1 receipts verified (2026-04-17T...Z → 2026-04-17T...Z)

The signed receipt format is compatible with @veritasacta/verify — your auditor can verify a chain offline with npx @veritasacta/verify .receipts/ without installing the sb binary.

Architecture

sb-cli            — the `sb` binary
├── sb-policy     — Cedar policy evaluator
├── sb-sandbox    — OS sandbox (Landlock + seccomp on Linux; macOS/Windows WIP)
└── sb-receipt    — Ed25519-signed, JCS-canonical, hash-chained receipts

Each sub-crate is usable independently. sb-receipt is deliberately minimal (zero I/O, pure crypto) so it can be dropped into other Rust agent frameworks.

Commands

sb exec --policy P --sandbox S -- CMD ARGS… evaluate P, apply S, emit receipt, exec CMD
sb verify DIR verify a chain of receipts offline
sb keys generate mint a fresh Ed25519 keypair

--allow-unsandboxed skips the sandbox step (Cedar + receipts still fire). Useful on macOS / Windows until the native backends ship; do not use in production.

Why not just…

  • …use Docker? Docker is great but heavy for CI, edge, and dev-laptop agents. sb-runtime is 8 MB and starts instantly.
  • …use OpenShell? OpenShell is the right design, but it expects Docker/OCI/k3s/gateway infrastructure. sb-runtime is the local-first version of the same idea. AGT's agent-os-kernel can talk to either; swap via config.
  • …use firejail / bubblewrap? Those are filesystem sandboxes. They don't evaluate Cedar policy before the exec, and they don't emit signed receipts. Combine them with sb-runtime if you want — sb does Cedar + receipts + Landlock+seccomp, they do extra fs isolation layers.
  • …just use Cedar? Cedar decides. It doesn't enforce or audit. sb-runtime is the enforcement layer.

Licensing

MIT. No runtime dependencies on ScopeBlind services; no telemetry. The optional managed tier (hosted receipt archival, team dashboards, compliance exports) is available at scopeblind.com/pricing but the sandbox runs local-only forever with the free binary.

Design-partner program

We're looking for 3–5 engineers to co-design the AGT provider interface, the Cedar schema for agent actions, and the macOS / Windows backend priorities. If you're building in this space (agent governance, policy-as-code, secure-element attestation, transparency-log anchoring), open an issue or reach out — early partners get direct input on API surface before v0.1 stabilises.

Related

Contributing

Small repo, fast iteration. PRs welcome. See DESIGN.md for the current roadmap.