fabro/lib/apps
Bryan Helmkamp dfd2458f76
Test an Ask Fabro turn against the container Petri created
A live-server scenario runs a one-stage workflow on Docker whose command
writes a file into the workspace, opens an Ask Fabro session on the
finished run, and sends one turn. The session attaches to the container
Petri created, stopped at the run's end, starts it again, and its tool
reads the file inside it; the turn succeeds, the tool's output and the
model's reply carry the file's content, and the twin's follow-up request
shows the model read it from the tool. Ask Fabro's tool policy is
read-only, so the shell tool is hidden from the model and refused; the
turn reads the file with the `read_file` tool, scripted on the twin,
instead of a shell `cat`.

The scenario skips, and says why, without the Docker plugin or a daemon,
as the other Docker scenarios do.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-19 14:58:09 -04:00
..
fabro-cli Test an Ask Fabro turn against the container Petri created 2026-09-19 14:58:09 -04:00
fabro-mcp-server Drop the dependency edges with no production use 2026-09-19 09:33:31 -04:00
fabro-server Delete a run's sandboxes through Petri's lease ledger 2026-09-19 14:54:03 -04:00
fabro-spa refactor: organize crates into three layers 2026-07-23 17:59:34 -04:00