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

How to resume past Pi coding sessions from a desktop window with Pi Agent Desktop

Find earlier Pi sessions by project and continue them without digging through .jsonl files.

Who it is forA developer who has used Pi in a terminal and now wants to pick up old coding sessions for a project.

The problemPast Pi sessions are hard to find and reopen when they are buried in terminal history or session files.

The outcomeThe user sees their projects in the app, opens a past session, and continues the conversation with the agent.

What you need first

  • A supported machine: Apple Silicon Mac on macOS 11 or later, Windows 10/11 x64, or Linux x64 with WebKitGTK 4.1 and GTK 3
  • Pi sessions or Pi model keys on this machine (optional, only needed to see existing history)
  • For the proxy use case: Node.js 22 and npm, plus a running HTTP proxy address

Steps

  1. Open the releases page at https://github.com/abcwyc/pi-agent-desktop/releases and download the Apple Silicon aarch64.dmg, the Linux .deb, or the Windows x64-setup.exe.
  2. Install the app. On macOS, drag Pi Agent into Applications.
  3. If macOS blocks the first launch, run xattr -dr com.apple.quarantine "/Applications/Pi Agent.app" and open the app again.
  4. Open Pi Agent and select your project in the sidebar to see its past sessions.
  5. Open the session you want and send a new message to continue it.

Prompt for your agent

Using the abcwyc/pi-agent-desktop README, explain how to locate and resume a past Pi session for the project at <project-path>. Expected output: the session name and date the user should open. Verify that Pi reads sessions from ~/.pi/agent/ before reporting success.

Caveat. The app reads Pi's local data directory by default, so sessions created on another machine will not appear unless their files are copied into ~/.pi/agent/ or PI_CODING_AGENT_DIR points there.

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