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

How to watch a running agent session from a phone browser with Percho

Scan a QR code to follow a session from a tablet or phone and act on approvals.

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

Credentials. Remote prompts and approval decisions can drive tools on the desktop machine, so enable them only on a network you trust.

Who it is forA developer who starts a long agent task at a desk and wants to check progress from another room or device.

The problemA long-running coding task forces you to stay at the desktop to see progress or answer approval prompts.

The outcomeYou see the session on a phone or tablet browser and can respond to approvals while away from the desk.

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 Percho on the desktop and start or open the session you want to watch.
  2. Turn on the cross-device option and show the QR code (inferred: the setting lives in the app's session or settings panel).
  3. Scan the QR code with your phone or tablet browser.
  4. Monitor the session, and only if needed enable remote prompts, stop generation, or allow-once and deny approval decisions.

Prompt for your agent

In the repo Jaxton07/percho, enable the cross-device QR view for the session <session-name> and report the URL scheme you see on the QR code. Verify that a second device can load the session read-only before any remote action is enabled.

Caveat. The README does not describe how the phone connection is secured, so verify the network path before using remote prompts.

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