DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find an earlier decision in past Pi sessions with Pi Posthorse

Search prior conversation and sub-agent runs in the project to recover a decision or error detail.

Credentials. History can include user messages, assistant thinking, tool arguments, errors, and images, and retrieved content enters your selected model's context, so check for sensitive data before sharing it with a provider.

Who it is forA developer returning to a project after context was rolled over who needs the exact wording of an earlier decision, error, or tool result.

The problemAfter a rollover, the earlier conversation is out of the active window and the exact details are hard to find again.

The outcomeThe model retrieves the matching history entries, including images, and continues with the recovered details.

What you need first

  • Node 24.12.0 or later
  • Pi 1.0.0 or later (official Pi or the fitchmultz/pi fork)
  • A terminal where you can run pi commands
  • A decision on whether notes under .pi/notes/ should be added to .gitignore

Steps

  1. Install Posthorse with pi install npm:pi-posthorse and restart Pi.
  2. Ask Pi to search earlier conversation using the history tool, for example by a keyword from the decision.
  3. Ask for the all: true option when the earlier work may be in another session of this project or in a nested subagent run.
  4. Read the returned entries and ask Pi to confirm which one matches the decision you need.
  5. Keep the recovered details in a note if the next steps depend on them.

Prompt for your agent

Using the pi-posthorse repo (fitchmultz/pi-posthorse), use the history tool in the project at <project-path> to search earlier sessions for the decision about <topic>, including other sessions with all: true. Expected output: the matching history entries with their session context. Verify that each quoted detail appears in the returned history entries before you rely on it.

Caveat. Posthorse makes no network requests itself, but any history content you retrieve is sent to the model and provider you have selected.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page