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

How to run Percho from source to customize its themes with Percho

Install dependencies, start the dev build, and run the checks before changing the UI.

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 to change Percho's themes, UI plugins, or tool-call cards, or contribute a fix.

The problemCustomizing a desktop app's interface requires a working development environment and a way to verify changes.

The outcomeA running development build of Percho with typecheck and tests passing, ready for UI changes.

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. Install Node.js 22.19 or newer.
  2. Run npm install in the repository folder.
  3. Run npm run dev to start Percho in development mode.
  4. Run npm run typecheck and npm run test after each change. (inferred, check the README)
  5. If the Electron binary download stalls in China, set ELECTRON_MIRROR=https://npmmirror.com/mirrors/electron/ before installing.

Prompt for your agent

Using the repo Jaxton07/percho, install dependencies and start the development build, then run `npm run typecheck` and `npm run test`. Report the results and confirm the three packages (shared, backend, desktop) are present.

Caveat. The README warns that the backend package is the only place importing the Pi SDK, so keep Pi SDK changes inside that package.

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