v1.0.17 — Thinking inspection tools

Highlights

• Verbatim thinking: /thinking-steps verbatim [branch|all] opens recorded provider thinking without summarizing it. Switch between source, derived steps, and complete review with v, s, and a. Whitespace and Markdown markers are preserved; unsafe terminal characters appear as visible escapes. The three live display modes remain unchanged.
• Recorded-text search: /thinking-steps search [branch|all] [literal text] searches prompts, responses, and available thinking case-insensitively. Results include entry/block/line context and source-line jumps; the first 200 occurrences are shown.
• Alternate-branch comparison: /thinking-steps compare displays alternate responses and their thinking side by side, stacking below 60 terminal columns. Sequential responses on the same branch are not treated as alternatives.
• Export manager: /thinking-steps exports shows available, partial, missing, and unsafe session-linked snapshots. Inspect paths or explicitly confirm deletion of a selected snapshot.
• Compatibility diagnostics: /thinking-steps diagnostics reports loaded extension/Pi versions, patch lifecycle state, and recorded thinking availability without conversation text.

Privacy and deletion safety

Inspection uses recorded provider content only; it cannot recover hidden or redacted reasoning and makes no model calls. Search and comparison do not alter session history or switch branches.

Export deletion validates snapshot paths, ownership markers, and file identities, rejects unexpected files and symbolic links, and rechecks after confirmation. It removes only recognized files and their empty directory, never recursively deletes directories, and preserves session history and other snapshots. Deleted links remain recorded but show as missing; deletion cannot be undone. I/O failures report any partial deletion.

Diagnostics include local paths and provider/model identifiers; review them before sharing. Nothing in these tools enables autosaving or uploads exports.

Validation

• npm run build and 199 behavior/metadata tests passed.
• Separate repository lockfile integrity check passed (200 distinct automated tests total).
• Actual packed/extracted-package build and 199 tests passed.
• Real Pi 0.99.2 and 1.0.0 host-loader smoke checks passed, including verbatim/search/comparison, export management, diagnostics, rendering, autosaving, and cleanup.

Pi development dependency pins are unchanged. These are local validation results, not a claim about remote CI status. npm publication remains separate and maintainer-owned; this GitHub release does not publish the npm package.

v1.0.16 — Scoped review and opt-in autosave

Highlights

• Scoped exports: /thinking-steps export both branch saves only the current branch. Existing export commands still default to all recorded branches; all can be selected explicitly.
• Read-only review browser: /thinking-steps review or review all navigates recorded prompts, responses, available provider thinking, and derived steps directly in Pi.
• Opt-in automatic exports: /thinking-steps autosave on requests 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 status and autosave off inspect 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 build and 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.

v1.0.15 — Installation documentation and repository links

Documentation and metadata updates

• Updated README and package repository, homepage, and issue links to the canonical crustyhacker/pi-thinking-steps repository.
• Added an npm badge and installation quick start.
• Highlighted always-visible thinking panels and session-linked JSON/Markdown exports, with links to export privacy guidance and release notes.

No runtime behavior or dependency changes from v1.0.14.

Install

With Pi installed:

pi install npm:pi-thinking-steps@1.0.15

Restart Pi after installation. View on npm.

Validation

TypeScript build and all 175 tests passed before the release commit.

Changelog · Changes since v1.0.14

v1.0.14 — Always-visible thinking panels and session exports

Highlights

• Thinking panels stay visible for every assistant response in compatible terminal sessions. When no thinking text is available, they show an honest waiting or missing-content label.
• Export prompts and available thinking as a session-linked review tree in JSON, Markdown, or both:

  /thinking-steps export json
  /thinking-steps export markdown
  /thinking-steps export both
  

• Existing collapsed, summary, and expanded modes and Alt+T controls remain available.

Install

With Pi installed:

pi install npm:pi-thinking-steps@1.0.14

Restart Pi after installation. View on npm.

Export privacy

Exports are manual and require an idle, persistent session. Files are saved in private directories beside the session and linked through a session entry outside model context. They include all recorded branches and original historical prompts, so treat them as sensitive conversation data. Provider signatures, redacted payloads, image bytes, and tool/custom-entry contents are excluded. The extension cannot retrieve thinking that the provider does not expose.

Validation

• TypeScript build and 175 tests passed.
• Bundled Pi 1.0.0 loader checks covered rendering modes, Alt+T, exports, session attachment/reopening, model-context isolation, and reversible cleanup.

Full changelog