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

How to run one routine across a shelf of phones, each with its own proxy with Droidline

Drive many phones from one PC, each sending chosen apps through its own upstream.

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

Account pooling. Running one routine across many phones with different proxies can look like account pooling to the apps you automate, so check the terms of each service before you do this.

Who it is forAn operations person who runs the same daily app routine on several phones and needs each phone on its own network path.

The problemRunning the same routine on many phones means managing each one by hand, and routing per app usually needs root or extra hardware.

The outcomeOne PC runs the same routine on several named phones in parallel, with chosen apps sent through a socks5 or http upstream set per phone.

What you need first

  • A PC running Windows, macOS, or Linux
  • An Android phone running Android 9 or later
  • The droidline archive for your system from the Releases page
  • droidline-agent.apk from the same release page, installed on the phone
  • Python 3.9+ or Node.js 18+ if you want to script, or an MCP-capable agent app

Steps

  1. Run droidline serve on the PC and pair each phone with droidline pair, giving each phone a name you choose.
  2. Set a socks5 or http upstream for each phone so its chosen apps use a local VPN route, one upstream per phone.
  3. Write one script that takes a phone name and runs the routine against it, then start it for each phone.
  4. Check the status of each phone for connection, route and permissions before the daily run.
  5. Read the printed results per phone and rerun any phone that failed the routine.

Prompt for your agent

Using the Droidline repo at https://github.com/KnifeLemon/Droidline, write a script that runs the same routine on each paired phone in <phone list>, with each phone using its own proxy upstream. Output one JSON line per phone with its name and a pass or fail result. Verify every phone reports a route in its status before it runs the routine.

Caveat. The README does not give a single command to set proxy upstreams, so confirm the exact setup in the Remote phones and recipes docs before you rely on it.

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