Runner sandbox and egress proxy

The idea

On the person's machine, a slice's CLI runs under sandbox-exec or bubblewrap, which deny by default. It writes only its task folder, and its only network is a proxy that reaches the vendor.

The problem
A CLI on a personal machine could read keys, push code or reach any host.
Why it matters
One rule set, compiled for both platforms, keeps secrets, git remotes and upload hosts out of reach.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Own computer by default, one command

    A person connects their own computer with one pre-approved command; the official Claude Code and Codex CLIs run there under the person's own login, which the platform never opens.

  • Native implementation round

    Implementation runs as one sandboxed Claude Code or Codex session, briefed by a compiled file. Its tools go through the gateway hook. The supervisor gets back only the report, the diff and the checks.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.