{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "fitchmultz-pi-posthorse--try-posthorse-for-one-pi-session",
 "repo": "fitchmultz/pi-posthorse",
 "repo_url": "https://github.com/fitchmultz/pi-posthorse",
 "repo_slug": "fitchmultz-pi-posthorse",
 "title": "Test Posthorse in one Pi session before installing",
 "page_title": "How to test Posthorse in one Pi session before installing with Pi Posthorse",
 "summary": "Load Posthorse for a single session to check rollover behavior without a permanent install.",
 "who": "A developer who wants to evaluate fresh-window rollover on a real task before committing to an install in their Pi setup.",
 "problem": "Installing a context extension permanently is a bigger change than a developer may want to make before seeing how it behaves.",
 "outcome": "The developer runs one Pi session with Posthorse loaded, watches rollover happen, and decides whether to keep it.",
 "steps": [
  "Confirm Node 24.12.0 or later and Pi 1.0.0 or later are available.",
  "Run `pi -e npm:pi-posthorse` to start Pi with Posthorse for one session.",
  "Give Pi a long task and watch for the Compacted from card and any new_context request.",
  "Run `pi remove npm:pi-posthorse` later if you decide not to keep it, since removal leaves notes and history in place."
 ],
 "agent_prompt": "Using the pi-posthorse repo (fitchmultz/pi-posthorse), start a single Pi session for the project at <project-path> with `pi -e npm:pi-posthorse`, run a long task, and report whether a new_context request or a Compacted card appears. Verify that pi list does not show a permanent install if the developer asked for a one-session test.",
 "agents": [
  "any"
 ],
 "difficulty": "Beginner",
 "time": "15 minutes",
 "basis": "readme",
 "caveat": "Two Posthorse copies can compete for rollover, so keep only one copy loaded, and check installed sources with pi list.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "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"
 ],
 "risk": "sensitive",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/fitchmultz-pi-posthorse/try-posthorse-for-one-pi-session/",
 "md": "https://dedupedai.com/use-cases/fitchmultz-pi-posthorse/try-posthorse-for-one-pi-session/index.md",
 "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 hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/fitchmultz-pi-posthorse--try-posthorse-for-one-pi-session.json",
 "api_version": "v1"
}