Authorization notice. Termish is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Credentials. Remote screen control gives direct access to the desktop, so use it only on machines you own or are authorized to operate.
Who it is forA developer or operator who needs to check a graphical app on a home or office computer while away from it.
The problemSome tasks need a visual desktop check, such as confirming an app's window or output, and a terminal alone cannot show that.
The outcomeThe user sees the remote screen on the phone and can use touch or a virtual mouse to operate desktop apps next to the terminal.
What you need first
- An Android 8.0+ phone or an iOS device with macOS and Xcode for building
- A reachable development machine or server with SSH access (Mosh also needs UDP and mosh-server)
- Login credentials or a private key for that remote host
- For builds: JDK 17, the Android SDK and Rust via rustup
Steps
- Open the host in Hosts and choose remote screen from its menu.
- Accept the screen service installation from the app if prompted.
- Open the floating window or switch to full screen.
- Use touch or the virtual mouse to check or operate a desktop app.
- Return to the terminal or Herdr workspace when finished.
Prompt for your agent
Using the farlume/termish README and its screen service guide, explain the requirements for viewing the remote screen of <host>. Expected output: a list covering the graphical session, the companion service and macOS recording consent. Verify that the list mentions that lock-screen capture is limited by the desktop's security policy.
Caveat. The README says lock-screen capture and control remain subject to the desktop's security policy, so it may not work on a locked computer.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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