Pi Prompt History

What it does

Scans Pi session JSONL files, extracts user-message text, and stores a searchable copy in a local SQLite database.

Offers exact-cwd Local search and cross-session Global search through commands or Ctrl+R.

Can replace editor text and copy a selected prompt to the system clipboard, or restore or fork from the selected session point.

When to reach for it

Invocation: Press Ctrl+R or run /prompt-history for exact-cwd search; use /prompt-history-global only when cross-project history is intended.

A useful prompt from the current working directory should be reused

Search Local history and load the selected text into the editor.

The prompt came from another Pi working directory

Switch deliberately to Global history and inspect the displayed cwd metadata.

Work should continue from the selected historical point

Choose fork to branch from that entry or restore to switch to the full session.

What it adds

• Persistent prompt indexing independent of the original session-file scan cost.
• Local and Global scopes with current-session, same-cwd, and other-cwd grouping.
• Copy, restore, and fork actions from one interactive history overlay.

How it fits

No related catalog surfaces are recorded.

Common questions

Where does prompt text persist?

• Original prompt text remains in Pi session JSONL files and is also copied into a SQLite database.
• The default database lives in the agent prompt-history data directory, and configuration can move both database and session source paths.
• The extension exposes reindexing and status commands but no data-retention or database-deletion command; remove the configured database separately when its history should no longer remain.

Is Local mode a privacy boundary across projects?

• Local queries filter by exact cwd, but the same database can contain prompts from many working directories.
• Global mode searches all indexed prompts and displays other-cwd metadata. Treat the database as sensitive local data protected by host filesystem access.

Does selecting a prompt create another copy?

• The copy action replaces Pi editor text and also sends the selected prompt to the terminal or operating-system clipboard path, creating another exposure boundary.

It’s working if

• Local search returns only entries whose stored cwd exactly matches the current cwd.
• Global search can show entries from other working directories with source metadata.
• Copy loads the full selected prompt into the editor; restore and fork use the selected session file and entry.

Source and setup

Provenance

Project

Pi Prompt History

Origin

Vedang Manerikar

Current maintainer

Vedang Manerikar

Relationship

original

Installed source

git:github.com/vedang/pi-prompt-history

Source path

View source (src/index.ts)

Compatibility

• Interactive Pi
• Pi session JSONL files
• Bun SQLite or supported Node.js SQLite runtime

License

WTFPL

License publication scope

Source link, independently written summary, and reviewed behavior claims.

Reviewed revision

eedbef7afdf16a317785be469f600d71fadc9ef0

Catalog revision

e0c035a297462c519315abfa1af31a1ed3bd9eef

Setup notes

• Review configured database and session paths before enabling Global search on a shared account.
• Prompt text is stored as readable SQLite content; this extension does not establish a separate encryption boundary.
• Copying uses terminal and platform clipboard mechanisms, whose retention and sharing behavior is outside the extension.
• Created and maintained by Vedang Manerikar under the WTFPL at the reviewed revision.