Repository navigation
v1.0.16 — Scoped review and opt-in autosave
Highlights
- Scoped exports:
/thinking-steps export both branchsaves only the current branch. Existing export commands still default to all recorded branches;allcan be selected explicitly. - Read-only review browser:
/thinking-steps revieworreview allnavigates recorded prompts, responses, available provider thinking, and derived steps directly in Pi. - Opt-in automatic exports:
/thinking-steps autosave onrequests confirmation before enabling session-specific snapshots. Defaults are JSON, current branch, thinking only, and 10 retained snapshots. Format, scope, content, and retention (1–50) are configurable;autosave statusandautosave offinspect or disable it. - Portable package tests: validation runs against the actual packed/extracted npm artifact without private repository workflow files. Lockfile integrity is checked separately.
- Compatibility CI: Node 22.19.0/24 and Pi 0.99.2/1.0.0 matrix, with real bundled-host loader checks.
Privacy and retention
Autosaving is off by default. Settings belong to the current session ID; new or separately forked sessions start off. Thinking-only exports can still contain sensitive text quoted by the provider. Hidden reasoning, signatures, redacted payloads, image bytes, tool payloads, system prompts, and custom-entry contents are not exported. Nothing is uploaded.
Retention applies only to owned automatic snapshots, never manual exports. Unexpected files or symbolic links stop cleanup with a warning. Old automatic attachment links may expire. The review browser and export attachments do not add model context or trigger another turn.
Validation
npm run buildand 186 tests passed.- Separate repository lockfile integrity check passed.
- Actual packed/extracted-package build and 186 tests passed.
- Real Pi 0.99.2 and 1.0.0 bundled-host smoke checks passed for rendering, mode controls, branch export, review, autosave/retention, and cleanup.
Pi development dependency pins are unchanged. npm publication is separate and is handled by the maintainer; this GitHub release does not itself publish the npm package.