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

How to continue a Pi CLI session in the Percho window with Percho

Pick up a terminal Pi session in the visual app without losing its history.

Authorization notice. Percho is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer who started a task in the Pi CLI in a terminal and wants a visual view to keep working on it.

The problemSwitching from a terminal agent to a visual interface often means losing context or re-entering settings.

The outcomeThe same session appears in Percho with its history, because both tools read the same configuration directory.

What you need first

  • A desktop computer running macOS, Windows, or Linux (x64), or Node.js 22.19 or newer for running from source
  • Access to a model provider through a supported subscription login or an API key
  • For the shared-session use case, Pi CLI sessions stored in ~/.pi/agent/ on the same machine

Steps

  1. Start a session with the Pi CLI in your terminal and let it run or save its state.
  2. Open Percho on the same machine.
  3. Find the session in the project and session sidebar (inferred: the session should be listed under the same project).
  4. Open the session and continue the conversation in the composer.

Prompt for your agent

In the repo Jaxton07/percho, check that the shared ~/.pi/agent/ directory is the one used for sessions, auth, and model settings. Report which session from <session-name> is visible in the Percho sidebar and whether its prior messages load.

Caveat. Percho embeds the Pi SDK and is not a fork, so behavior depends on the Pi engine version bundled with the app.

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