scriptoriumadmin/fabro
1
0
Fork 0
mirror of https://github.com/fabro-sh/fabro.git synced 2026-09-15 23:32:46 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

docs: clarify file-backed artifact docs

Browse source 
Update the run directory, context, and output docs to describe
large offloaded values as file-backed artifacts while preserving the
existing cache path examples.
This commit is contained in:
Bryan Helmkamp 2026-04-04 00:00:25 -07:00
parent 2842870737
commit c7787e3d31
No known key found for this signature in database
3 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/agents/outputs.mdx
View file

@ -136,7 +136,7 @@ When a stage produces a large context value -- an LLM response, command output,
### How offloading works
After each node completes, Fabro checks every context update. If the serialized JSON of a value exceeds **100KB**, it is written to the artifact store on disk and replaced in the context with a `file://` pointer:
After each node completes, Fabro checks every context update. If the serialized JSON of a value exceeds **100KB**, it is written to a file-backed artifact on disk and replaced in the context with a `file://` pointer:
```
response.plan --> file:///path/to/logs/cache/artifacts/values/response.plan.json
@ -145,7 +145,7 @@ command.output --> file:///path/to/logs/cache/artifacts/values/command.output.j
Values under 100KB remain in the context as-is.
### Artifact storage layout
### File-backed artifact layout
Offloaded artifacts are written to the run's directory:
@ -192,7 +192,7 @@ fabro/meta/{run_id}
command.output.json
```
This means artifact data survives process restarts and can be recovered when resuming a run from a Git branch.
This means file-backed artifact data survives process restarts and can be recovered when resuming a run from a Git branch.
## Remote sandbox syncing

2
docs/execution/context.mdx
View file

@ -196,7 +196,7 @@ Internal keys (prefixed with `internal.`, `current`, `graph.`, `thread.`, `respo
## Artifact offloading
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:
When a stage produces a large output (over 100KB of serialized JSON), Fabro automatically offloads it to a file-backed artifact 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

2
docs/reference/run-directory.mdx
View file

@ -73,7 +73,7 @@ Manager nodes that run sub-workflows write a nested `child/` directory containin
**`cache/`** — Local filesystem cache for file-backed artifacts and captured test assets:
- `cache/artifacts/values/` — large context values offloaded from checkpoints
- `cache/artifacts/values/` — large context values offloaded to file-backed artifacts
- `cache/artifacts/assets/` — captured test artifacts organized by node and retry
## Browsing runs