Private execution host

The idea

A root service on the host runs sandbox commands under signed, bounded grants from an issuer. It listens on a private socket and keeps a journal to clean up the Docker objects it owns.

The problem
The app container should never hold the Docker socket, or choose host paths and keys.
Why it matters
Workers cannot choose operator paths or profiles, and unknown cleanup state is kept, not guessed.
Where it stands
Partly built as of

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

  • Workspace sandbox and repository environment

    Worker commands run in a sandbox (local or Docker) confined to the checkout, with a scrubbed environment, allowed binaries, limits and one path guard. Repository setup and readiness are recorded and reused.

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.