v0.3.3
pi-pretty v0.3.3
Summary
This patch release combines the recent rendering and FFF-path fixes into a single v0.3.3 release.
What changed
- Fixed themed tool background rendering so
toolSuccessBgandtoolErrorBgfill the full rendered width for core tool output. - Preserved the active tool background across ANSI reset sequences to avoid broken background bands inside highlighted output.
- Kept error rendering on
theme.fg("error", ...)while switching error panels totoolErrorBg. - Moved pi-pretty FFF data from:
~/.pi/agent/fff
- To:
~/.pi/agent/pi-pretty/fff
- Added a helper to resolve the pi-pretty-specific FFF directory under
getAgentDir(). - Updated README to document the pi-pretty-owned FFF data location.
- Added a test that verifies the generated frecency/history DB paths use the new per-extension location.
Files
src/index.tstest/fff-integration.test.tsREADME.mdpackage.jsonpackage-lock.json
Verification
npm run typecheck✅npm test✅ (47 tests)npm run lint⚠️ still reports pre-existing Biome diagnostics in legacy code paths; no new release-blocking failure was introduced for this patch.
Upgrade notes
If your Pi theme defines:
{
"toolSuccessBg": "#1e2e1e",
"toolErrorBg": "#2e1e1e"
}core tool panels now render those backgrounds across the full line width instead of only behind printed characters.
When FFF is available, pi-pretty now stores frecency/history data under:
~/.pi/agent/pi-pretty/fff/
Existing data under ~/.pi/agent/fff is not migrated automatically by this release.