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

How to answer agents from your phone when they need you with Vela Term

Scan a QR code to browse your session tree and reply to agents from iOS or Android.

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

Credentials. The QR code pairs your phone with your sessions, so treat it like a login and do not share a screenshot of it.

Who it is forA developer who starts long agent tasks at a desk and wants to respond from a phone when away.

The problemAn agent waits for input while you are away from the computer, and the task stalls until you return.

The outcomeYou get a push notification when an agent needs you, and you can read its replies and answer from your phone.

What you need first

  • A computer running macOS, Windows or Linux
  • The VelaTerm installer from velaterm.com/download
  • A logged-in local Codex or Claude Code install for agent sessions and audits
  • A phone with the VelaTerm iOS or Android app for mobile access

Steps

  1. Install the Vela Term desktop app and open your sessions on the desktop.
  2. Open the remote access option and show the QR code for pairing.
  3. Install the Vela Term phone app for iOS or Android and scan the QR code.
  4. Browse the session tree, read the agent replies and send your answer.

Prompt for your agent

Pair the VelaTerm phone app with the desktop app for the project at <project-path} by scanning the QR code shown in remote access. Expected output: the session tree on the phone with the same sessions as the desktop. Verify that a push notification arrives when an agent in that project waits for input.

Caveat. Mobile access depends on the desktop app running and paired, so the phone cannot reach sessions on a machine that is off or disconnected.

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