From d4f3764bce3ed982da0d8b821ead4def06c73008 Mon Sep 17 00:00:00 2001 From: Bryan Helmkamp Date: Sat, 28 Mar 2026 01:22:13 -0400 Subject: [PATCH] Fix leading space in artifact path doc example Co-Authored-By: Claude Opus 4.6 (1M context) --- docs/execution/context.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/execution/context.mdx b/docs/execution/context.mdx index 7c47820b5..40b50b75c 100644 --- a/docs/execution/context.mdx +++ b/docs/execution/context.mdx @@ -199,7 +199,7 @@ Internal keys (prefixed with `internal.`, `current`, `graph.`, `thread.`, `respo When a stage produces a large output (over 100KB of serialized JSON), Fabro automatically offloads it to the **artifact store** on disk rather than keeping it in the in-memory context. The context value is replaced with a `file://` pointer: ``` - response.plan → file:///tmp/logs/cache/artifacts/values/response.plan.json +response.plan → file:///tmp/logs/cache/artifacts/values/response.plan.json ``` The preamble renderer resolves these pointers and displays a reference to the file path. For remote sandboxes (Docker, Daytona), Fabro syncs artifact files to the sandbox at `{working_directory}/.fabro/artifacts/` so agents can read them.