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

How to run the local web dev server behind an HTTP proxy with Pi Agent Desktop

Route model and API calls through a proxy while developing Pi Agent from source.

Who it is forA developer on a network that requires an HTTP proxy who wants to run Pi Agent from source.

The problemModel and API requests fail on a network that only allows traffic through a proxy.

The outcomeThe local dev server starts at localhost:30141 and sends its model and API requests through the configured proxy.

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. Clone the repository from https://github.com/abcwyc/pi-agent-desktop and open it in a terminal.
  2. Install dependencies with npm install.
  3. Start the dev server through your proxy, replacing 127.0.0.1:7890 with your proxy address: HTTP_PROXY=http://127.0.0.1:7890 HTTPS_PROXY=http://127.0.0.1:7890 NO_PROXY=localhost,127.0.0.1 npm run dev. (inferred, check the README)
  4. Open http://localhost:30141 in your browser and send a test message to confirm model requests work.

Prompt for your agent

Using the abcwyc/pi-agent-desktop README, prepare the commands to start the dev server behind the HTTP proxy at <proxy-url>. Expected output: the exact environment variables and the npm command to run. Verify that NO_PROXY keeps localhost and 127.0.0.1 off the proxy.

Caveat. The README says the dev server listens only on 127.0.0.1, so it is reachable from this machine only unless you use the separate LAN mode, which needs a password.

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