Pi Jev Compaction — npmjs.com

Run pi install npm:pi-jev-compaction, or pin the release with pi install npm:[email protected]. Pi treats bare package names as local paths, so the npm: prefix is required for registry installs. Local-clone, project-level (-l), and session-only (pi -e) installs are also documented.

Yes. Each user brings their own personal key from console.typesafe.ai/settings/keys. Without a key the extension falls back to Pi's built-in summary rather than failing, and CI can inject TYPESAFE_API_KEY from a runner secret.

Prefer export TYPESAFE_API_KEY in your shell profile, or write it to ~/.config/pi-jev-compaction/env with chmod 600. Do not put it in config.json: that file accepts thresholds only, and parsing plus /jev-setup strip any apiKey field.

The extension fails soft. On a missing key, network or auth errors, malformed responses, history that cannot fit the state budget, reduction below minReductionRatio, or an abort, it returns no compaction and Pi continues with its built-in LLM summary.

keepThreshold (0.5), preserveRecentMessages (6), minReductionRatio (0.25), maxStateTokens (25000), maxRequestTokens (30000), truncateHeadChars (300), model (jev-latest), and baseUrl. Each has a matching PI_JEV_* environment override.

The algorithm and question format come from fast-jev-compaction (MIT). That Claude Code plugin can replace the entire message list, but Pi cannot, so this extension works within Pi's compaction limits.

Whether a key was detected (never the secret itself), the config and env-file paths, effective options, and the last compact outcome including the reason it fell back, such as no_key, jev_error, reduction_too_small, cannot_fit, or aborted.