@vanillagreen/pi-output-policy
v1.0.4
Published
OMP-style large-output policy for Pi tool results: minimization, bounded truncation, and spill-file preservation.
Downloads
542
Maintainers
Readme
pi-output-policy

OMP-style large-output policy for Pi tool results.
Install
Via npm:
pi install npm:@vanillagreen/pi-output-policyVia vstack:
cargo install --git https://github.com/vanillagreencom/vstack.git vstack
vstack add vanillagreencom/vstack --pi-extension pi-output-policy --harness pi -yRestart Pi after installation.
What it does
- Preserves oversized output under
~/.pi/agent/vstack/pi-output-policy/sessions/<session-id>/artifacts/when possible; never under the project.pi/directory. - Uses head truncation for search/listing tools and tail truncation for command/log tools.
- Adds explicit truncation notices with size, line count, direction, and artifact path.
- Leaves file
readresults unmodified by default; enabletruncateReadOutputsto cap reads. - Leaves edit/write results and diff details unmodified by default; enable
truncateMutationOutputsto cap file mutations. - Leaves details payloads intact by default so extension state, subagent details, and diffs are preserved; enable
sanitizeDetailsfor stricter UI safety caps. - Keeps shell-output minimization off by default; enable
shellMinimizer.enabledto compress noisy command logs before truncation.
Limit
Pi's built-in tools may already truncate before tool_result. This extension can only preserve the text it receives, so custom tools that return full large text benefit most from spill preservation.
For truncated file reads, continue reading the original source file with offset/limit. Session tool-results/*.json files are wrapper artifacts for the already-returned tool result; they may contain escaped, line-hostile JSON and usually do not recover file content beyond Pi's read limit.
