# AI use cases for Remote Installer (icodesign/remote-installer) Repo: [icodesign/remote-installer](https://github.com/icodesign/remote-installer) | Use cases: 5 | Page: https://dedupedai.com/use-cases/icodesign-remote-installer/ Remote Installer is a command-line tool that shares a signed iOS or Android build from your computer over a temporary HTTPS link so a phone can install it directly. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Install a new iOS build on a remote iPhone via link: https://dedupedai.com/use-cases/icodesign-remote-installer/share-ios-build-to-iphone-via-link/ - Share a signed Android APK for direct phone install: https://dedupedai.com/use-cases/icodesign-remote-installer/share-android-apk-to-phone-browser/ - Share a build for one hour with a single download: https://dedupedai.com/use-cases/icodesign-remote-installer/share-build-with-download-and-expiry-limits/ - Keep an install link alive after an AI agent exits: https://dedupedai.com/use-cases/icodesign-remote-installer/keep-install-link-alive-after-agent-exits/ - Share an iOS build only inside a private tailnet: https://dedupedai.com/use-cases/icodesign-remote-installer/share-ios-build-privately-over-tailnet/ ## How to install a new iOS build on a remote iPhone via link with Remote Installer Repo: [icodesign/remote-installer](https://github.com/icodesign/remote-installer) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Send a signed iPhone build to a tester anywhere with a link and QR code, skipping TestFlight. **Who it is for:** An iOS developer or vibe coder who needs a teammate or their own phone to test a fresh build while away from the Mac. **The problem:** TestFlight adds processing wait time, and getting a dev or ad hoc build onto a phone remotely is otherwise slow. **The outcome:** The phone installs the signed build from a temporary HTTPS link printed by the command, with a QR code for the camera. ### Steps 1. Install the tool with `brew install icodesign/tap/remote-installer`. 2. Confirm the target iPhone's UDID is in the provisioning profile and that the app was rebuilt after the device was registered. 3. Run `remote-installer share /path/to/MyApp.app` (or use your `.ipa` path). 4. Keep the command running, then open the link in the phone's browser or scan the QR code with the camera. 5. Tap Install and confirm Install in the system prompt, then check the Home Screen for the result. ### Prompt to paste into your agent ```text Use the repo icodesign/remote-installer to share the signed build at with `remote-installer share `. Return the printed install URL and confirm the command is still running. Verify the iPhone is listed in the embedded provisioning profile before sharing. ``` ### Caveat Remote Installer only distributes an existing signed build and does not sign, re-sign, or register devices, so the iPhone must already be in the provisioning profile. 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/icodesign-remote-installer/share-ios-build-to-iphone-via-link/ ## How to share a signed Android APK for direct phone install with Remote Installer Repo: [icodesign/remote-installer](https://github.com/icodesign/remote-installer) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Send a signed standalone APK to an Android phone through a link and let the phone download it. **Who it is for:** An Android developer or tester who needs a debug or test APK on a physical phone away from the desk. **The problem:** Google Play Beta requires setup and processing, and sideloading an APK to a remote device usually means file transfers. **The outcome:** The Android phone opens the link, downloads the signed APK from the browser, and installs it from the downloads folder. ### Steps 1. Install the tool with `brew install icodesign/tap/remote-installer`. 2. Make sure the APK is a signed standalone APK; App Bundles (.aab) and .apks sets are rejected. 3. Run `remote-installer share /path/to/MyApp.apk`. (inferred, check the README) 4. Open the printed link in the Android browser or scan the QR code, then open the APK from the browser's downloads. 5. Follow the Android prompts to finish installing the APK. ### Prompt to paste into your agent ```text Use the repo icodesign/remote-installer to share the signed APK at with `remote-installer share `. Return the install URL and state that the APK is a standalone APK. Verify that the file is not an .aab or .apks file before running. ``` ### Caveat Split-only APKs are rejected when apkanalyzer is available, and Android App Bundles are intentionally not installable through this tool. 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/icodesign-remote-installer/share-android-apk-to-phone-browser/ ## How to share a build for one hour with a single download with Remote Installer Repo: [icodesign/remote-installer](https://github.com/icodesign/remote-installer) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Cap a shared build by download count and time so an outside tester gets one install window. **Who it is for:** A developer who must hand a build to someone outside the team and wants it to stop being available automatically. **The problem:** A public link stays live indefinitely unless you stop it by hand, which risks leaving a build reachable after it was meant to expire. **The outcome:** The link closes after one successful download or one hour, whichever comes first, and the temporary copy is removed. ### Steps 1. Install the tool with `brew install icodesign/tap/remote-installer`. 2. Run `remote-installer share MyApp.ipa --max-downloads 1 --expire-after 1h`. 3. Send the printed URL or QR code to the recipient. 4. Wait for the install to finish, or let the command exit at the limit. 5. If the share is still open, stop it with Ctrl+C so the tunnel closes and the temporary copy is deleted. ### Prompt to paste into your agent ```text Use the repo icodesign/remote-installer to run `remote-installer share --max-downloads 1 --expire-after 1h` and return the install URL. Verify the output states both limits before handing the link to anyone. ``` ### Caveat The full public URL works as a capability, so anyone who receives it can install the build until a limit is reached, and the limits do not add authentication. 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/icodesign-remote-installer/share-build-with-download-and-expiry-limits/ ## How to keep an install link alive after an AI agent exits with Remote Installer Repo: [icodesign/remote-installer](https://github.com/icodesign/remote-installer) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Run a bounded share as a launchd background worker so the link survives the agent's session. **Who it is for:** A developer using a coding agent on a Mac who needs the agent to hand back a working install URL and then finish its turn. **The problem:** When an agent command ends, a normal foreground share closes, so the install link stops working before the phone can use it. **The outcome:** The agent returns a JSON session with an install URL, the share keeps running under launchd, and the developer can check or stop it later. ### Steps 1. Install the tool with `brew install icodesign/tap/remote-installer`. 2. Run `npx --yes @icodesign/remote-installer share MyApp.ipa --background --expire-after 30m --json` and note the printed share ID. (inferred, check the README) 3. Check the share with `remote-installer status`. 4. Read the output with `remote-installer logs` if the phone cannot connect. 5. Stop the share with `remote-installer stop` once installation is done. ### Prompt to paste into your agent ```text Use the repo icodesign/remote-installer to run `npx --yes @icodesign/remote-installer share --background --expire-after 30m --json` and return the install URL and share ID. Verify the response includes a bounded expiry before ending the turn. ``` ### Caveat The --background mode is macOS only and requires a bounded expiry, and the README says the share lifecycle does not survive plain & or nohup. Risk, remote script: A background worker keeps serving the build after the agent's turn ends, so the agent must always set a bounded expiry and the human must check the share status. 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/icodesign-remote-installer/keep-install-link-alive-after-agent-exits/ ## How to share an iOS build only inside a private tailnet with Remote Installer Repo: [icodesign/remote-installer](https://github.com/icodesign/remote-installer) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README Keep the install link inside your Tailscale network so it is not public on the internet. **Who it is for:** A developer whose team already runs Tailscale and who does not want a build reachable from the public internet. **The problem:** Quick Tunnels and Funnel links are public, so a team that must keep builds private needs an access boundary. **The outcome:** The install link is reachable only by devices on the tailnet, and the terminal labels it as Tailnet only. ### Steps 1. Install Tailscale and confirm the phone is on the same tailnet, or allowed by its access policy. 2. Install the tool with `brew install icodesign/tap/remote-installer`. 3. Run `remote-installer share MyApp.ipa --provider tailscale-serve`. (inferred, check the README) 4. Confirm the terminal shows `Tailnet only` next to the URL. 5. Open the link on the phone while it is on the tailnet and tap Install. ### Prompt to paste into your agent ```text Use the repo icodesign/remote-installer to run `remote-installer share --provider tailscale-serve` and return the URL. Verify the terminal labels it as Tailnet only and that the phone is on the same tailnet before sharing. ``` ### Caveat Tailscale Serve requires the phone to be on the same tailnet or otherwise allowed by access policy, and DNS settings may need to be enabled on the devices that open the link. 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/icodesign-remote-installer/share-ios-build-privately-over-tailnet/