# AI use cases for Termish (farlume/termish) Repo: [farlume/termish](https://github.com/farlume/termish) | Use cases: 5 | Page: https://dedupedai.com/use-cases/farlume-termish/ Termish is an open-source Android and iOS terminal app for SSH and Mosh sessions, with a Herdr workspace, optional native agent chat, SFTP files and a remote-screen view. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run Codex in Herdr from your phone: https://dedupedai.com/use-cases/farlume-termish/run-codex-in-herdr-from-phone/ - Chat with a coding agent in native phone chat: https://dedupedai.com/use-cases/farlume-termish/chat-with-coding-agent-natively/ - Keep a remote terminal task alive on a weak network: https://dedupedai.com/use-cases/farlume-termish/keep-remote-task-alive-on-mobile-network/ - Build the Termish Android debug app from source: https://dedupedai.com/use-cases/farlume-termish/build-termish-android-debug-from-source/ - View and operate a remote desktop from your phone: https://dedupedai.com/use-cases/farlume-termish/view-remote-desktop-from-phone/ ## How to run Codex in Herdr from your phone with Termish Repo: [farlume/termish](https://github.com/farlume/termish) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README Start a coding task on a remote machine from a phone and check its output in the Herdr terminal. **Who it is for:** A developer away from their desk who needs to give a coding agent a task on a remote development machine and follow its progress. **The problem:** Coding agents run on a remote computer, but the developer has only a phone and needs a reliable way to start tasks and see results. **The outcome:** Codex runs inside Herdr on the remote host, and the developer can see live output, send a screenshot or file, and review the result from the phone. ### Steps 1. Open Hosts in Termish, tap `+`, and enter the SSH address, username and password or private key. 2. Verify the server's host key fingerprint on first connection. 3. Open the host menu and choose Herdr. If Herdr is missing, accept Termish's guided installation. 4. Start Codex from Herdr, give it a task, and follow its output in the terminal. 5. Upload a screenshot or file if useful, then check the result through the remote-screen window or in the terminal. ### Prompt to paste into your agent ```text Using the farlume/termish README, give step-by-step instructions to connect a phone to over SSH, open Herdr, and start Codex with the task . Expected output: a numbered checklist of app steps. Verify that the checklist includes host key verification before the first login. ``` ### Caveat The README gives no list of Codex or Herdr versions that are tested, so confirm compatibility on your own host. Risk, remote script: Termish can offer guided installation of Herdr on the remote host, so review what the installer changes before accepting it. Risk, credentials: SSH passwords or private keys are stored in the phone's Keystore or Keychain, so protect the device with a lock. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/farlume-termish/run-codex-in-herdr-from-phone/ ## How to chat with a coding agent in native phone chat with Termish Repo: [farlume/termish](https://github.com/farlume/termish) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Use a phone-native chat interface for Codex, Claude Code or another supported CLI on a remote host. **Who it is for:** A developer who wants a conversational interface to a coding agent on a server, without working in a raw terminal. **The problem:** Terminal-based agents are hard to follow on a small screen, especially when streaming replies, tool calls and file attachments are involved. **The outcome:** The developer holds a chat with an agent running on the remote host, attaches files, stops tasks and resumes conversations from the phone. ### Steps 1. Add the remote host in Hosts and connect over SSH. 2. Confirm the remote host has the agent's own login or a supported API provider configuration. 3. Open the host menu and choose Agents, then select Codex, Claude Code, Gemini CLI, OpenCode or Pi. 4. Send a task, attach a file if needed, and follow streaming replies and tool calls. 5. Stop a task or resume an earlier conversation from the chat list. ### Prompt to paste into your agent ```text Using the farlume/termish README, list the setup needed to use the Agents entry with on host . Expected output: a short list of prerequisites and the steps to start a chat. Verify that the list states that the remote host needs the agent's own login or a supported API provider configuration. ``` ### Caveat Agent chat is an alternative to the Herdr terminal workspace, not a replacement, and the README says approvals depend on each agent's protocol. Risk, credentials: The agent's login or API provider settings live on the remote host, so check who can access that account before you connect from a phone. Risk, remote script: Missing CLIs can be installed from the app, which runs installation steps on the remote host. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/farlume-termish/chat-with-coding-agent-natively/ ## How to keep a remote terminal task alive on a weak network with Termish Repo: [farlume/termish](https://github.com/farlume/termish) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Use Mosh with a tmux session so long-running commands survive phone sleep and network changes. **Who it is for:** A developer who starts a long build or agent session on a server and needs it to keep running while the phone moves between networks or sleeps. **The problem:** Standard SSH sessions drop when the connection changes or the app goes to the background, which can interrupt work. **The outcome:** The terminal reconnects after network roaming, and the remote program keeps running inside a named tmux session. ### Steps 1. Open the host in Hosts and choose Mosh in the host's connection settings. 2. On the remote, make sure `mosh-server` is installed and a UDP port is reachable; accept guided installation if it is missing. 3. Set the startup command to `tmux new -A -s main` in the host settings. 4. Start the long-running task inside the tmux session. 5. Reconnect later from the same host; the session should still be running. ### Prompt to paste into your agent ```text Using the farlume/termish README, describe how to set up a Mosh connection to that starts the command `tmux new -A -s main`. Expected output: a checklist covering mosh-server, UDP reachability and the startup command. Verify that the checklist includes the note that tmux or Mosh is needed for terminal continuity. ``` ### Caveat The README says iOS suspends the app in the background, so long tasks still depend on tmux or Mosh on the remote host. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/farlume-termish/keep-remote-task-alive-on-mobile-network/ ## How to build the Termish Android debug app from source with Termish Repo: [farlume/termish](https://github.com/farlume/termish) | Difficulty: Advanced | Time: 90 minutes | Basis: From the README Compile a debug Termish APK from the open-source code with Gradle and the Android SDK. **Who it is for:** An Android developer or contributor who wants to test or modify Termish before it is released. **The problem:** Contributors need a working local build to test changes, and the README asks for specific tools before the first build. **The outcome:** A debug build of the Android app is produced by Gradle without release signing keys. ### Steps 1. Install JDK 17, the Android SDK and Rust via rustup. 2. Set `ANDROID_HOME` or the SDK path in `local.properties`. 3. Run `git clone https://github.com/ttermish/termish.git`. 4. Run `cd termish`. 5. Run `./gradlew :composeApp:assembleDebug`. ### Prompt to paste into your agent ```text Using the farlume/termish README, build the Android debug app from a local clone at . Expected output: a debug APK produced by `./gradlew :composeApp:assembleDebug` with no release signing keys. Verify that the build command ran from the repository root. ``` ### Caveat The README clone URL points to the ttermish organization while this repository is listed as farlume/termish, so confirm the correct remote before cloning. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/farlume-termish/build-termish-android-debug-from-source/ ## How to view and operate a remote desktop from your phone with Termish Repo: [farlume/termish](https://github.com/farlume/termish) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Open a computer's graphical desktop in a floating window and use touch to check apps. **Who it is for:** A developer or operator who needs to check a graphical app on a home or office computer while away from it. **The problem:** Some tasks need a visual desktop check, such as confirming an app's window or output, and a terminal alone cannot show that. **The outcome:** The user sees the remote screen on the phone and can use touch or a virtual mouse to operate desktop apps next to the terminal. ### Steps 1. Open the host in Hosts and choose remote screen from its menu. 2. Accept the screen service installation from the app if prompted. 3. Open the floating window or switch to full screen. 4. Use touch or the virtual mouse to check or operate a desktop app. 5. Return to the terminal or Herdr workspace when finished. ### Prompt to paste into your agent ```text Using the farlume/termish README and its screen service guide, explain the requirements for viewing the remote screen of . 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. Risk, credentials: Remote screen control gives direct access to the desktop, so use it only on machines you own or are authorized to operate. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/farlume-termish/view-remote-desktop-from-phone/