v0.5.9
PiTTy v0.5.9
PiTTy v0.5.9 adds a Memory browser for the pi-hermes-memory extension, fixes messages hanging during compaction, and corrects a stale-sample bug in the Codex usage burn-rate calculation.
Memory Browser
- Added a Memory browser (
/memory, orCtrl+Mon terminals that report it distinctly from Enter) for thepi-hermes-memoryextension: search across global Memory/User/Failures notes and the current project's memory, and remove individual entries with a confirmation step. - Reads and edits the extension's own Markdown files directly (no RPC support exists for this), and refuses to delete an entry if the underlying file changed since it was loaded, to avoid clobbering a concurrent writer.
- Added
pi-hermes-memoryto optional-integration detection so the browser can point you at installing it when it's missing.
Compaction Reliability
- Messages sent while Pi is compacting no longer hang waiting on a request that the agent won't answer until compaction ends. PiTTy now tracks compaction state from
compaction_start/compaction_endevents, queues any message typed during that window locally, and flushes it automatically once compaction finishes. /compactnow warns instead of starting a second overlapping compaction if one is already running.- The RPC client no longer misroutes a response that arrives after its own client-side timeout already fired; it's now logged and dropped instead of being resolved against a stale request id.
Codex Usage Tracking
- Fixed the last-hour usage delta being computed from a stale sample (e.g. after PiTTy was closed for a long time), which could report a misleading burn rate. The delta is now left unset unless a sample from within the last hour is actually available.
Regression Coverage
- Added unit tests for memory parsing/removal, the compaction queuing state machine, RPC late-response handling, and the Codex usage anchor fix.