# Two repos created in the same minute: terminal-mac has 2,600 stars, while terminal-phone, which draws an iPhone into the terminal, has a tenth of that · GitHub open source project

> Source: https://stringers.io/en/github/gh_govijr__terminal-phone.html (Stringers / 什么值得做, generated 2026-11-20)
> Stringers tracks which small products suddenly took off each day, investigates why one by one, and distils playbooks from them. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these investigations and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools feed (daily breakouts) / plays (playbooks) / hot / products / data. Setup: https://github.com/komako-workshop/stringers (the user signs in with Google at stringers.io/en/start.html to get a personal URL). Site index: https://stringers.io/llms.txt

> The author's sister project terminal-mac, created the same minute, blew up first. Bloggers mentioned it in passing, and it had 130+ stars before this launch. The author then posted a 45-second demo video on X, which an Instagram repost account picked up. But it only serves iOS devs and the visuals weren't fresh, so it got a tenth of terminal-mac's stars.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-11

govijr/terminal-phone · govijr

# Two repos created in the same minute: terminal-mac has 2,600 stars, while terminal-phone, which draws an iPhone into the terminal, has a tenth of that

**What it is** : a command-line tool that shows a clickable iPhone (simulator or real device) inside your terminal. Agents like Claude Code can also control the same phone through MCP, and it includes App Store screenshots, preview videos, and test flows.

**Why it took off** : its sister project terminal-mac, created in the same minute, blew up first. A blogger wrote about it and mentioned this one in passing, which already had 130+ stars before launch. The author then posted a 45-second demo video on X, and an Instagram repost account shared it around. But it only serves iOS developers, and the visuals aren't novel, so it got a tenth of terminal-mac's reach.

**C** **How you can follow this** : stop building simulator mirrors in the terminal. Copy its launch approach: aim the first project at the broadest audience and have the sister project ready at the same time; in a crowded niche, do the part nobody else offers and can deliver directly (for example, App Store assets from one command), and pair it with a 45-second demo video that's easy to repost.

C grade: within the same week, three people hit the same idea. The competitor mobile-mcp has 10.5k stars and also supports Android, while the author, who already had momentum, got only a little over two hundred stars even with this level of detail. The launch approach is worth learning, but copying the product itself will probably not get you many stars. Still almost unknown

Data (updated daily) · Repo created 2026-11-03 · 300 stars · 7 days +45

GitHub · stars

Data 2026-11-05 → 2026-11-20 (16 days, 16 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

terminal-phone lets you draw an iOS simulator or your own iPhone inside the terminal, so a human can tap with a mouse while an agent like Claude Code controls the same phone through MCP. 9 days, 245 stars: it looks like a rising new project. Break it down, though, and over half its stars came from its sister project terminal-mac, which blew up and carried this one along. The author's own launch video got only 6% of the views terminal-mac's did. The features are detailed, but "view your phone screen in the terminal" already has a dozen-plus players. Below: what it is, where the stars came from, why it got only a tenth of the attention, and what an indie dev building a dev tool that actually gets stars can take from this case.

### Nov 3 morning, one person created two repos

2026 year, Nov 3, Beijing time 11:21: GitHub user govijr created terminal-phone; a minute later, at 11:22, they created terminal-mac. The author is govi, X account @kirtandopamine. Before terminal-mac took off, they had 94 followers on GitHub; now it's 119.

The two repos share one idea: pack an entire graphical device into the terminal so people and agents can share it. terminal-mac packs a whole macOS VM, selling the line "the agent gets its own Mac, you keep yours"; terminal-phone packs an iPhone.

terminal-mac blew up first. Its demo video on X got 700k views, and by 11-11 it had 2,610 stars and 180 forks (GitHub, 11-11). On Nov 4, blogger Flavio Copes wrote two articles about terminal-mac, each adding a line at the end:

> There is a sibling project, terminal-phone, that does the same thing for iOS simulators and real iPhones.

That's how terminal-phone got its first 130+ stars.

### What it is: an iPhone shared between you and an agent

The first line of the README reads "An interactive iPhone in your terminal, shared with your AI agents": a clickable iPhone in your terminal, shared with your AI agent.

- **Display** : 30 frames. In Ghostty, kitty, iTerm2, WezTerm, Warp, and VS Code it renders a sharp image; in terminals without graphics support like Terminal.app it degrades to a half-block character approximation. `--split right` opens a pane next to the current terminal to hold the phone.

- **How people use it** : click to tap, drag to swipe, scroll wheel to scroll; shortcuts switch phones, take screenshots, return to the home screen, and view app logs.

- **How agents use it** : three commands, `observe`, `act`, and `wait`, plus an MCP service. `terminal-phone mcp install` writes it into the config of Claude Code, Cursor, and Codex in one command. Agents get references to UI elements, refuse to run stale instructions once the screen has changed, and every input returns a receipt, so an uncertain tap is never replayed.

- **Real iPhone** : connect over USB or Wi-Fi via WebDriverAgent. Read-only by default; the device owner has to tap Allow before it can take actions.

- **An all-in-one toolkit for indie iOS devs** : saves trigger a rebuild and relaunch; one command exports App Store screenshots and preview videos in the required sizes, with device frames, backgrounds and captions; 12 device colors (silver, deep space black, cosmic orange, deep blue, red...); YAML test flows like Maestro, with JUnit output for CI; one-click status bar override to 9:41.

The requirements are spelled out too: a Mac with Apple silicon, macOS 15 or later, and Xcode 26 or later. The first run also downloads the simulator runtime.

The author shipped 4 releases in two days, from v0.3.0 to v0.4.0, from 11-05 to 11-06, plus a one-line install script and a Claude Code plugin. 11-07 merged the first external contributor's PR, fixing a simulator issue on Xcode 27. It's free, with only GitHub Sponsors and Buy Me a Coffee links.

### Where the stars came from: riding a sibling, launching, then getting reposted

| Date | star | What happened |
|---|---|---|
| 11-03 | 0 | Repo created |
| 11-04 | — | Flavio Copes mentioned it in passing in his terminal-mac article |
| 11-05 | 114 |  |
| 11-06 | 131 |  |
| 11-07 to 11-09 | 132 → 134 | Barely growing |
| 11-09 | 134 | The author's launch video went up on X on 23:30 Beijing time |
| 11-10 | 170 | +36 |
| 11-11 | 223 | +53, the single-day peak; reels reposting it started appearing on Instagram |
| 11-12 | 244 | +21 |

(Daily GitHub star counts.)

**Phase one: spillover from the sister project.** The repo had 134 stars before the author had posted about it. The source was terminal-mac's audience overflow: a blogger mentioned it in an article, the author's profile showed both repos side by side, and new followers from terminal-mac starred it on their way through.

**Phase two: the author's own launch post.** In November 9, the author posted a 45-second video on X with the caption "Introducing terminal-phone. Your real iPhone or iOS simulator, inside your existing terminal." Five selling points followed: agents can use your phone, scripted testing, App Store videos and screenshots, 12 device colors, and free and open source. The repo link went in a reply, and two more replies each demoed the screenshot and video features separately.

The post got 41.9k views, 811 likes and 792 bookmarks (X page, 11-11). Bookmarks were nearly as high as likes, so viewers saved it as a tool, though not many people saw it. terminal-mac's launch post had 702k views and 8,100 bookmarks; terminal-phone got only 6% and 10% of those. The repo gained 89 stars in the two days after the post.

**Phase three: Instagram repost accounts.** In November 11, the AI news account @aiadventureryt posted a reel: "This is a real iPhone, running inside a terminal window… Comment IPHONE and I'll send you the link". @tech.verse_daily posted the same day. terminal-mac had been reposted this way too: a public GitHub repo logs that in their automated reel pipeline, the terminal-mac reel hit 69k views, 60 times the usual, and the log notes "terminal-phone is the natural follow-up". 11-11 was the day with the most new stars, matching the reel timing, but outside evidence can't show the reel caused it.

It has also been listed in plugin directories such as ClaudePluginHub. It hasn't appeared on Hacker News, Reddit or in the press. Searching HN for "Terminal Phone" turns up an unrelated Tor-based encrypted walkie-talkie project from 2026 February (322 points), so the name is already taken.

### Why it reached only a tenth of that

**The audience is narrower.** terminal-mac speaks to anyone using agents, and everyone worries about an agent messing with their computer. terminal-phone only serves iOS developers who have an Apple silicon Mac with Xcode 26.

**The visual isn't as "impossible".** A whole macOS desktop running inside a terminal stops people in their tracks. An iPhone simulator shown in a terminal is something developers have already seen. mobile-mcp demonstrated the same sidebar mirroring in Claude Code over a month earlier (10-02).

**The most compelling selling points are practical but don't break out.** The best-looking parts of the launch post were the device colors and the App Store screenshots and preview videos. Those matter to indie iOS developers, but they don't land for outsiders.

One more detail: the README spot where a demo GIF should go still holds the placeholder comment "Add a demo GIF here". The video only lives on X, so people who arrive from directory sites or repost accounts see a wall of text.

### How crowded this space is

| Project | Scale | Compared with alternatives |
|---|---|---|
| mobile-next/mobile-mcp | 10.5k stars | The most direct rival: a Claude Code plugin that mirrors the terminal sidebar and also supports Android. It only works with kitty-protocol terminals and has no App Store assets. 10-02 |
| getsentry/MobileBuildMCP (formerly XcodeBuildMCP) | 6.6k stars | Lets agents build, run and test iOS apps, with screenshots and UI control, but no live view for humans |
| joshuayoes/ios-simulator-mcp | 2.2k stars | Agent-only control of the simulator, no visual output |
| jo-duchan/tapflow | 1.9k stars | Streams the simulator to a browser, aimed at teams |
| ZSeven-W/dsh-ios | 460 stars | A live simulator plus USB real devices in the DeepSeek Harness sidebar, also via WebDriverAgent |
| sethdeckard/deviceterm | 2 stars | The same idea from August: a built-in terminal that puts the simulator in a pane beside the shell |
| Bethel-nz/rexsim | 1 stars | Released 11-09, 16 minutes before terminal-phone's launch post; also draws the simulator into the terminal over the kitty protocol |
| Maestro, fastlane | 16.4k / 42k stars | Established YAML test flows and App Store screenshot tooling; terminal-phone combines both |
| Apple Xcode 27 Device Hub | All iOS developers | Official tooling that unifies simulators and real devices and exposes an agent interface; the display is in an Xcode window, not in the terminal |

(GitHub star counts, around 11-12.)

At least three people hit the same idea in the same week. terminal-phone wasn't first, and its star growth ranks in the middle: that same week mobile-mcp gained 212 stars, tapflow gained 269, dsh-ios gained 101, and terminal-phone gained 130.

### If it were you

**C: worth studying, but don't build another "iPhone in a terminal".** Even an author with a recent 2,600-star hit, built-in followers and bloggers recommending the work only reached a couple hundred stars. Building another one of these means competing with mobile-mcp at 10.5k stars, which also spans Android, plus Apple itself. The thing to take away is govi's launch playbook.

**Who it fits** : developers who already got a wave of attention from one project and have a next idea; or iOS developers who want to build agent tools, provided they pick a part nobody has done well yet.

**Who it doesn't fit** : anyone wanting another iOS or Android simulator terminal mirror (three people collided on that in one week); anyone whose first project has no audience yet and who hopes to start from a "sister project" (without a first hit, there's no spillover to ride).

**How to do it:**

1. **Aim the first project at the widest audience** , with a visual that makes people stop on sight. terminal-mac used "agents on your own Mac", which every agent user understands.

2. **Prepare the sister project at the same time** , listed side by side in the first project's README and on the author's profile. If the first one takes off, bloggers will mention it in passing and new followers will click through. But plan for the second one reaching a narrower audience, which here meant a tenth of the result.

3. **In a crowded field, build the deliverable piece nobody else has** . terminal-phone's App Store screenshots and preview videos with device colors were the most eye-catching part of the launch video. If you know iOS development, packaging "one command for App Store assets" as a standalone tool agents can call may have more of a chance than another mirror (an inference: I didn't find a project doing exactly this, and I haven't verified how big the demand is).

4. Put the demo GIF on the first screen of the README, and search GitHub and HN for name collisions before settling on a name.

**How to get users** : the author posted a 40-to-45-second demo video on X, with body text of one sentence plus five selling points, the link in a reply, and two or three follow-up replies demoing the best features separately. Make sure the video reads clearly in both landscape and portrait, so the "comment a keyword for the link" AI news accounts on Instagram can repost it directly. Those accounts are already mining developer-tool launch videos for topics. Submit to the Claude Code plugin and MCP directories the same day.

**Timing** : the window for "put the device in the terminal for agents" is measured in weeks. Three teams landed on it in the same week, and mobile-mcp could add terminal compatibility and screenshots at any time. The launch playbook itself has no expiry.

**What would show this read was wrong** : (1) terminal-phone gaining 1,000 stars within a month with no new large repost, which would mean iOS developers want this more than estimated and this path is underrated; (2) mobile-mcp adding App Store assets and full terminal compatibility while terminal-phone's stars keep climbing, which would mean its users value the details and later entrants can still win on polish; (3) someone starting from zero, with no sister project to ride, building a terminal simulator tool that reaches a few hundred stars or more, which would mean spillover matters less than argued here.

[GitHub repo ↗](https://github.com/govijr/terminal-phone)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| mobile-next/mobile-mcp(/mobile-mirror) | Open source | 2025-03; terminal mirror 2026-10-02 | 10.5k star | A Claude Code plugin that mirrors the device into the Ghostty/kitty sidebar and supports Android too; but it only works with kitty-protocol terminals and has no App Store assets, device frames or YAML flows |
| getsentry/MobileBuildMCP (formerly XcodeBuildMCP) | Open source | 2025-03 | 6.6k star | An MCP that lets agents build, run and test iOS apps with screenshots and UI actions, but no live terminal view for humans |
| joshuayoes/ios-simulator-mcp | Open source | 2025-03 | 2.2k star | MCP-only simulator control, no visual output |
| ZSeven-W/dsh-ios | Open source | 2026-08 | 460 star | A live simulator and USB real-device sidebar in the DeepSeek Harness chat (also via WDA), tied to DSH and not in the terminal |
| sethdeckard/deviceterm | Open source | 2026-08 | 2 star | The same idea, earlier: a built-in terminal that puts the simulator as a pane beside the shell; requires switching terminals and got no traction |
| Browser streaming such as jo-duchan/tapflow | Open source | 2026-05 | 1.9k star | Streams the simulator to a browser for teams; not terminal-first and not agent-first |
| Lakr233/vphone-cli | Open source | 2026-02 | 16.6k star | Runs a full virtual iPhone, aimed at security research rather than terminal or agent tooling |
| Maestro / idb / Appium WebDriverAgent | Open source | 2015-2022 | 16.4k / 5.4k / 2.0k star | Established iOS automation; its YAML flows are almost the same as Maestro's, with no live terminal view |
| fastlane snapshot/frameit and similar screenshot tools | Open source | 2014 | fastlane 42k star | Produces App Store screenshots and device frames, but has no live view and no agent support |
| Apple Xcode 27 Device Hub / Agent Skills | Big-company features | 2026-06 WWDC, official in the fall | All iOS developers | Official unification of simulators and real devices, with devicectl extended to simulators; the display lives in an Xcode window rather than the terminal |

Where users come from

- **Verified** **sister project terminal-mac's spillover** : both repos were created within the same minute; two terminal-mac articles on flaviocopes.com (11-04) say "There is a sibling project, terminal-phone"; the repo already had 134 stars before the launch post (repo_day 11-09)

- **Verified** **the author's own X launch video post** : x.com/kirtandopamine/status/2119814854660042975,2026-11-09 at 15:30 UTC, a 45-second video, 41.9k views, 811 likes, 792 bookmarks, 60 reposts, 66 replies; +89 stars over the following two days

- **Verified** **Instagram AI news reels with "Comment IPHONE for the link"** : @aiadventureryt reel DfmhlEktysK on 11-11; @tech.verse_daily the same day; voicebox-gpu PR #231 logs the terminal-mac reel at 69k views and sets terminal-phone as the next topic

- **Verified** **Claude Code plugin/MCP directories** : listed on ClaudePluginHub and forkfree.dev; README has a one-line /plugin install and mcp install

- **Verified** **Hacker News / Reddit / media** : no terminal-phone thread on HN Algolia; x-radar shows 0 posts; no press coverage found

## Why govijr/terminal-phone took off

> Research date 2026-11-11 (data card refreshed to 2026-11-12). Data card: /home/ljr/fanout/why/cards/gh_govijr__terminal-phone.json. Sibling project report: /home/ljr/fanout/why/out/gh_govijr__terminal-mac.md

### Bottom line

terminal-phone didn't take off on its own. It rode on terminal-mac's wake. The author, govi (@kirtandopamine)11-03, created both terminal-mac and terminal-phone repos on the same day. terminal-mac blew up on X first (700k views, 2.6k stars). terminal-phone leaned on its "sister project" angle to get to about 130 stars, then 11-09 posted the official launch on X. It got only 42k views and roughly 110 more stars. By stars, it's about 1/10 of terminal-mac's count. What it does is render the iOS Simulator or a real iPhone inside the terminal so agents can operate it. That's already covered by mobile-mcp (10.5k stars, and it had terminal-embedded mirroring by 10-02) plus a batch of others like dsh-ios, DeviceTerm, and rexsim. Where it really differs is that **it's a full toolkit for solo iOS developers** : one command produces App Store screenshots and preview videos, 12 device frame colors, and YAML test flows. But those differences only resonate with the narrow iOS dev crowd, and it never broke out beyond that.

### What it is

- On Apple silicon Macs (macOS 15+, requires Xcode 26+), it renders the iOS simulator or a real iPhone paired via WebDriverAgent into the terminal at 30fps. Ghostty and kitty use the kitty graphics protocol with shared memory; iTerm2, WezTerm, Warp, and VS Code use inline images; other terminals fall back to half-block characters. `--split` creates native splits in Ghostty, kitty, iTerm2, WezTerm, and tmux.

- Humans can tap, drag, and scroll. Agents operate it through a JSON CLI or MCP server (`phone_observe` / `phone_act` / `phone_wait`), working with accessibility element references. Actions are refused if the screen is stale, and inputs return receipts.

- Bundled dev tools: `run --watch` (rebuilds on save), `logs`, `record` (records a GIF and generates a replayable action flow), `appstore screenshot|record` (outputs screenshots at App Store Connect-accepted sizes and 886x1920 preview videos, with optional device frames, backgrounds, and captions), `test flows/ --junit` (runs YAML flows, CI-ready), and `sim` (sets the status bar to 9:41, location, permissions, push notifications).

- One-line install (curl | bash, SHA-256 verified). It's also a Claude Code plugin (`/plugin marketplace add govijr/terminal-phone`). `terminal-phone mcp install` automatically writes the config for Claude Code, Cursor, and Codex.

- Real devices are view-only by default and only become controllable after the device owner grants access.

- Only GitHub Sponsors and BuyMeACoffee accept money.

Source: GitHub README (https://github.com/govijr/terminal-phone).

### Data

| Timeline | star | fork | Source |
|---|---|---|---|
| 2026-11-03 03:21 UTC | Repo created (1 minutes before terminal-mac) |  | GitHub API |
| 2026-11-04 | Someone opened issue #1 (simulator scale detection failed) |  | github.com/govijr/terminal-phone/issues/1 |
| 2026-11-05 | 114 | 7 | our GitHub repo_day |
| 2026-11-06 | 131 | 8 | repo_day |
| 2026-11-07 to 11-09 | 132 → 134 | 8 → 9 | repo_day (barely moved) |
| 2026-11-09 15:30 UTC | **Author posts launch on X** |  | x.com/kirtandopamine/status/2119814854660042975 |
| 2026-11-10 | 170(+36) | 10 | repo_day |
| 2026-11-11 | 223 (+53, single-day high) | 15 | repo_day; same day, Instagram repost account @aiadventureryt posted a reel |
| 2026-11-12 | 244(+21) | 15 | repo_day; GitHub API live 245 |

- Release cadence: 11-05 released v0.3.0,11-05, then v0.3.1 (adding `mcp install` and the Claude Code plugin); 11-06 released v0.3.2 (one-line install script); 11-06 released v0.4.0. 11-07 merged PR #2 from external contributor lewcart, fixing a simulator issue under Xcode 27. Source: GitHub releases and commits.

- Comparison (our GitHub database, 11-12): terminal-mac 2,598 stars (7 days, +1,218); mobile-mcp 10,506 (7 days, +212); dsh-ios 460 (7 days, +101); tapflow 1,856 (7 days, +269). terminal-phone is at 7 days, +130, placing it in the lower-middle of this group.

### Competitors (doing the same thing)

"Give agents control of iOS devices" and "put the simulator screen where developers can see it" are both already crowded. Even "render it in the terminal" isn't original:

| Name | Where | Launched | Scale | How terminal-phone differs |
|---|---|---|---|---|
| mobile-next/mobile-mcp | Open source | 2025-03; `/mobile-mirror` terminal mirror 2026-10-02 launched | 10.5k star | The most direct competitor: also a Claude Code plugin, also mirrors the device screen in a sidebar in Ghostty and kitty with tap support, and **also supports Android** . But it only works in kitty-protocol terminals, and it lacks App Store assets and device frames. |
| getsentry/MobileBuildMCP (formerly XcodeBuildMCP) | Open source | 2025-03 | 6.6k star | MCP and CLI for agents to build, run, and test iOS, with screenshots and UI actions, but no live view a human can watch |
| joshuayoes/ios-simulator-mcp | Open source | 2025-03 | 2.2k star | MCP-only simulator control, no screen |
| ZSeven-W/dsh-ios | Open source | 2026-08 | 460 star | DeepSeek Harness plugin: live simulator in a chat sidebar plus USB real devices (also via WebDriverAgent), 22 tools; tied to DSH, not in the terminal |
| sethdeckard/deviceterm(deviceterm.com) | Open source plus a macOS app | 2026-08 | 2 star | **The same idea appeared earlier** : a native terminal with the simulator as a Metal-rendered pane beside the shell. Switching to that terminal is required, and it didn't spread. |
| Bethel-nz/rexsim | Open source | 2026-11-09 (16 minutes before terminal-phone's launch post) | 1 star | Rex terminal draws the simulator via the kitty protocol; it hit the same idea at nearly the same time and didn't spread |
| jo-duchan/tapflow, bmcreations/loupe, ToolingTools/SimView, and others | Open source | 2026-05 to 10 | tapflow 1.9k, the rest under a few dozen | Streams the simulator to a browser or MCP app, aimed at teams or web use |
| Lakr233/vphone-cli | Open source | 2026-02 | 16.6k star | Runs a full virtual iPhone using Virtualization (leaning toward security research), covered by InfoQ. Not a terminal, not an agent tool. |
| Maestro, facebook/idb, Appium WebDriverAgent | Open source | 2015 to 2022 | 16.4k / 5.4k / 2.0k | Established iOS automation. Maestro's YAML flows are nearly identical to terminal-phone's flows. |
| fastlane snapshot/frameit and other App Store screenshot tools | Open source vs. paid | From ¥2014 | fastlane 42k | Exports screenshots and adds device frames, but no live view and no agent integration |
| Apple Xcode 27 Device Hub, Agent Skills | Big-company features | Announced at WWDC 2026-06, shipping with Xcode 27 final in the fall | All iOS developers | Apple is merging simulators and real devices into Device Hub, extending `devicectl` to simulators, and adding Agent Skills. But the screen lives in an Xcode window, not in the terminal (source: slekens.dev 2026-09-19). |

Verdict: "agents operating an iPhone" and "viewing the simulator in the terminal" are both old ideas. mobile-mcp came out a month earlier, has 40x the stars, and is cross-platform. terminal-phone's only new pieces are a few things: broad terminal compatibility (with fallbacks), real devices gated by owner consent, and **App Store screenshots and preview videos in 12 device frame colors** .

### Growth tactics (evidence)

1. **More than half the stars came from the sibling project's afterglow (confirmed)** . terminal-phone and terminal-mac were created the same minute, and they sit side by side on the author's GitHub profile. After terminal-mac took off, two long-form pieces on flaviocopes.com (11-04) both wrote "There is a sibling project, terminal-phone"; a Vietnamese Facebook post also mentioned it. So before its launch post it already had 134 stars (11-09), and **that part wasn't driven by its own launch** . terminal-mac also brought the author X followers, now about 5,438 (from a Brave-indexed profile summary, date unverified). The author's GitHub followers also rose from 94 to 119.

2. **The author's own X launch video post reached an order of magnitude less (confirmed)** . Posted 2026-11-09 15:30 UTC, a 45-second video with the caption "Introducing terminal-phone. Your real iPhone or iOS simulator, inside your existing terminal." followed by 5 selling points (agents use your phone, scripted tests, App Store videos and screenshots, 12 device frame colors, free and open source). Metrics: 41.9k views, 811 likes, 792 bookmarks, 60 reposts, 66 replies (X page plus syndication endpoint). Follow-up replies showcased the screenshot (2.2K views), video (1.8K), and repo link (1.6K). Compared with terminal-mac's 702k views and 8.1K bookmarks, that's roughly 6% and 10%. Bookmarks and likes are similar, which suggests people who saw it still saved it as a tool; there were just far fewer of them. launchvideos.gallery added this post to its "launch videos" collection.

3. **Instagram AI-news accounts running "comment a keyword, get the link" reels (confirmed)** . @aiadventureryt 11-11 posted a reel: "This is a real iPhone, running inside a terminal window…Comment IPHONE and I'll send you the link"; @tech.verse_daily posted a related reel the same day. For terminal-mac, @tectalks.io also ran a "Comment MAC" reel at the time. A public repo, aspershupadhyay/voicebox-gpu, has PR #231 (11-05) saying that in their automated reel pipeline, the terminal-mac clip hit 69k views, 60 times their usual, and noting "govijr/terminal-phone is the natural follow-up". In other words, someone is already running a pipeline that batch-repackages **developer tool launch videos** , and terminal-phone was picked as the next topic. 11-11 was the single biggest day for stars (+53), matching the timing of the IG reel, but this can't prove causation.

4. **Claude Code plugin and MCP directories (confirmed)** . ClaudePluginHub lists its plugin, and forkfree.dev lists it too. Install is one line.

5. **No mentions on HN, Reddit, media, or x-radar (confirmed)** . HN Algolia has no terminal-phone posts; searching "Terminal Phone" only returns 2026-02, an unrelated Tor walkie-talkie Show HN (322 points), and **that project already owns the name** . Our x-radar local corpus finds nothing (0 hits). No press coverage found.

### Why it took off (relatively)

- **The author's distribution came from terminal-mac** : same README style, same X account, same ~40-second video format. After terminal-mac blew up, bloggers mentioned the sister project in passing, the author's X following grew, and it had 130+ stars before the launch post.

- **The video hook changed** : terminal-mac sold the security anxiety of "the agent gets its own Mac, keep yours." terminal-phone sells "the agent uses your phone," plus "polished App Store screenshots and videos," plus "12 device body colors." The last two are concrete for indie iOS devs, and the launch thread's replies specifically demoed them.

- **It rides the wave of Claude Code and Codex building iOS apps** : many people build apps with agents but get stuck because the agent can't tap through the app and verify the result itself. It offers a "build → install → tap → verify" loop, installed with one line.

- **The barrier caps the audience** : it only runs on Apple-silicon Macs with Xcode 26+, downloads a simulator runtime on first run, and only serves iOS devs. terminal-mac drew every agent user. That's the main reason it reached only 1/10 of terminal-mac's stars.

### Differentiation

| Dimension | terminal-phone | Nearest competitors |
|---|---|---|
| Live view inside the terminal | Ghostty, kitty, iTerm2, WezTerm, Warp, and VS Code render it clearly; other terminals use half-block characters; native split panes; shared memory at 30fps | mobile-mcp `/mobile-mirror` only supports kitty-protocol terminals; DeviceTerm requires switching to its own terminal |
| Real devices | WebDriverAgent, over USB or Wi-Fi; the device owner can only watch before granting access | dsh-ios and mobster also use WDA |
| Agent safety | Rejects element references when the screen is stale, returns receipts, and never replays uncertain inputs | Most MCPs only offer coordinate taps |
| Tools for indie devs | **App Store screenshots and preview videos (exact sizes, device frames, captions), 12 device body colors, YAML flows with JUnit output, 9:41 status bar** | Scattered across fastlane, Rotato, and Maestro |
| Platform | iOS only | mobile-mcp supports iOS and Android |

These differences are part of why it earned stars: the most visible and most demo-able parts of the launch post were the device colors and App Store assets, which no rival offers. The "pretty" factor is real. But it's **not the main reason it took off** . The main driver was the attention from terminal-mac; the differentiators only appeal to iOS devs and never produced terminal-mac's "this looks impossible" moment. Besides, viewers already know what a simulator in a terminal looks like, and mobile-mcp demoed it a month earlier.

### Visibility and copycats

- Visibility: **few people know it yet, it has only spread in small circles** . The X launch post got 42k views, an Instagram reel repost ran, a flaviocopes article mentioned it briefly, and a plugin directory listed it. No HN, Reddit, or media coverage, and x-radar has 0 hits. The name also collides with the Tor walkie-talkie project, which takes up the search results.

- Copycats: no clone of terminal-phone found yet (terminal-mac already has a verbatim copy at wijonja/terminal-mac). Several others were doing the same thing around the same time: rexsim (11-09, 16 minutes earlier), DeviceTerm (2026-08), dsh-ios (2026-08), and mobile-mcp `/mobile-mirror` (2026-10). Many people arrived at the same idea independently; this isn't someone copying it.

### Takeaways

- **After the first hit landed, a sister project was released on the same template** : the repo was created the same day, and once the first project blew up, bloggers were asked to "mention it in passing," which funneled the new followers over. The catch: if the second product's audience is narrow, its results end up at 1/10 of the first's.

- **Adding a "pretty, ready-to-ship" feature to a crowded niche** : App Store screenshots and preview videos plus device colors are both something indie devs genuinely need and the most photogenic part of the video.

- **Instagram already has automated reel accounts that repost dev-tool launch videos** ("Comment XXX for the link"). Launch videos made to run about 40 seconds and look good in vertical format are easy to repost.

- Search for name collisions before naming: "Terminal Phone" was already taken by a Show HN with 300+ points.

### Uncertain

- Of the 130 stars before the launch post, how many came from each channel (the GitHub stargazers API currently returns 404, so per-hour star timing can't be retrieved).

- The IG reel's view count, and whether it had a causal relationship with the +53 stars on 11-11.

- The exact timing of the author's X follower count; whether the launch post was reposted by big accounts (repost-attribution data wasn't obtained).

- Real usage: it requires Xcode 26+; issue #1 and PR #2 show coordinate and scaling bugs with Xcode 27 and on some devices. Stars don't equal active use.

- Whether Apple's Device Hub and Agent Skills will make third-party tools pointless; whether mobile-mcp will add App Store asset features like this.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.
