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

How to install Percho and start your first agent chat with Percho

Download a prebuilt installer and open a visual chat with the Pi coding agent.

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 wants a visual desktop interface for the Pi coding agent instead of a terminal-only workflow.

The problemSetting up a coding agent with a visual chat, tool approvals, and themes usually means building or wiring up tools by hand.

The outcomeA working Percho app on your desktop with a first chat session open, ready to send prompts to the Pi engine.

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. Open the Releases page at https://github.com/Jaxton07/percho/releases and download the installer for your system.
  2. On macOS, if Gatekeeper blocks the app, open System Settings, go to Privacy & Security, and click Open Anyway next to Percho.
  3. On Linux, run chmod +x percho-linux-x86_64.AppImage before the first launch, and install libfuse2 first on Ubuntu 22.04 or 24.04 and derivatives.
  4. Open Percho and sign in to a provider with the in-app OAuth flow or an API key.
  5. Create a new session in a project and send a first prompt.

Prompt for your agent

Using the repo Jaxton07/percho, find the installer for <platform> on its Releases page and report the exact file name. Confirm the file name appears in the README download table for that platform.

Caveat. Builds are ad-hoc signed, so macOS may show a malware warning on first launch and Windows may show a SmartScreen prompt.

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