fabro/lib/apps
Bryan Helmkamp c4ed995b44
Add fabro-pebble-sandbox: a driver handle as pebble's Environment
Petri creates and owns every run sandbox through the sandbox driver, so
what Fabro still needs around a driver handle is the Pebble glue: the
Environment pebble's coding agent runs its tools through, the exec policy
(stop grace, working directory, StripAll, the termination mapping, the
redacted output tail), pebble's port routes over the driver's preview
URLs, the secret redactor, the path helpers, and a log rendering that
appends a failed command's redacted tail. This crate holds that glue,
moved from fabro-sandbox, over `Arc<dyn Sandbox>` plus a working
directory instead of `RunSandbox`, with a `MockSandbox` double behind
`test-support`.

`fabro exec` creates its host sandbox directly on the driver's Host
provider and activates it; Ask Fabro wraps the attached handle. Both
keep the provider alive beside the sandbox where the session's processes
are the provider's process groups.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-19 13:37:38 -04:00
..
fabro-cli Add fabro-pebble-sandbox: a driver handle as pebble's Environment 2026-09-19 13:37:38 -04:00
fabro-mcp-server Drop the dependency edges with no production use 2026-09-19 09:33:31 -04:00
fabro-server Add fabro-pebble-sandbox: a driver handle as pebble's Environment 2026-09-19 13:37:38 -04:00
fabro-spa refactor: organize crates into three layers 2026-07-23 17:59:34 -04:00