<- all tokdocs

Debloating an Android TV With Claude Code: How It Works and the Risks

By , founder of Mavric and Apso

View on TikTok ->

The "Claude Code can now hack your TV" trend uses Claude Code's ordinary Bash tool to run Android Debug Bridge (ADB) commands against an Android or Google TV over port 5555. A TikTok from @chase_ai_ calls it a new capability and says you simply point Claude Code at your TV. In practice you must enable developer options and approve a debugging prompt with the remote, apps are disabled rather than removed, and the video skips the security cost.

Can Claude Code really hack your TV?

No new capability shipped. Anthropic's tools reference lists 45 built-in tools, and the strings "adb", "android" and "television" appear nowhere on the page. The work is done by Bash, which Anthropic describes as "Executes shell commands in your environment."

ADB over TCP is also old. Android's adb documentation covers adb tcpip 5555 and adb connect <device_ip>:5555, and 5555 has been the default ADB-over-TCP port for about fifteen years. The project's tools/find-tv.sh script "scans the local /24 for ADB (5555) and Cast (8008)."

"Hack" overstates it. There is no exploit. The owner turns on a documented developer setting and approves a computer's RSA key on screen. Android's documentation says that dialog ensures "adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog."

How to set up the Claude Code TV debloat

The video says to just be on the same Wi-Fi. The prompt card it shows, posted by Mihir Gupta (@0900mihir) on X, starts with manual steps:

  1. On the TV: Settings → About → tap "Build" 7 times → Developer options → turn on USB debugging
  2. Open Claude Code on a laptop on the same Wi-Fi and paste:

"My Android TV is slow and full of ads. Find it on my Wi-Fi, connect over ADB, and debloat it: disable the manufacturer's ads, telemetry and junk (reversibly, never uninstall), asking me first about apps and features I might use. Then build and install a fast, minimal Apple TV-style home screen with a dock of my favourite apps and rotating nature wallpapers. Back up before changing anything, check every step with screenshots from the TV, and give me a restore script."

Gupta's README at mihirgupta0900/tv-home adds a step the post leaves out: "Accept 'Allow USB debugging?' on the TV when asked." An agent on a laptop cannot click that dialog.

No cable is needed on many Android TV sets. Android's pairing-code Wireless debugging needs Android 13 or later on TV, and the tested set was a "TCL Google TV (Android 11)." It's FOSS notes that on some sets, Xiaomi among them, USB debugging alone "opens network ADB on port 5555."

The README supports Android TV and Google TV only (TCL, Xiaomi/Redmi, Hisense, Sony, OnePlus, Realme, Nvidia Shield, Chromecast with Google TV). It excludes Samsung (Tizen), LG (webOS) and Fire TV.

Does it remove bloatware?

It disables it. The prompt says "(reversibly, never uninstall)," and the post continues "Nothing gets uninstalled." The repo's tools/disable.sh says "Packages are disabled for user 0, never uninstalled" and runs pm disable-user --user 0 on each package.

So no storage is freed, tools/restore.sh undoes it with one re-enable call, and the change does not survive a factory reset.

The list for the tested TCL set has exactly 25 packages, matching the "25 bloat apps disabled" claim. Most are TCL promo and telemetry packages such as com.tcl.ttvs ("TCL core service: BI analytics, Alexa bridge, account sync"), com.tcl.messagebox and com.tcl.esticker.

Does it make the TV faster?

The video says the TV runs "infinitely faster." No source measures speed. The only number is from Gupta's README, which says the custom launcher "cut the home screen's memory use from 192 MB to 83 MB" on "a 2 GB TCL Google TV," roughly a 57 percent drop for one process. That is a memory figure with no stated method, not a frame rate or latency test.

Who started the Claude Code TV trend?

The video shows only Gupta, but he was not first. Decoding X post IDs (which embed a timestamp) gives this order:

Time (UTC) Account Post
Oct 16, 20:44 Ryan Doyle (@doooyle) "Hacked my TV with Claude Code today"
Oct 17, 08:51 Gathin (@gathint) "Vibe coded my parents' TV this afternoon"
Oct 18, 09:07 Mihir Gupta (@0900mihir) "Saw people vibe coding their TVs"

Gupta's post came about 36 hours after Doyle's, and his README credits "Gathin23/tv-vibehack." TechCrunch's October 19 piece by Sarah Perez says Gupta "tested the approach independently." It's FOSS credits Doyle with starting the trend.

Is it safe to turn on ADB on your TV?

The TV keeps listening on port 5555 until you turn debugging off. Android warns that "not all access points are suitable." The RSA dialog blocks strangers, but "always allow from this computer" keeps a key trusted until revoked. It's FOSS advises you to "turn off USB or wireless debugging when you are done" to avoid "an open ADB port sitting on your home network."

The agent is the second exposure. Anthropic's sandboxing docs state "The sandbox is off by default." A stock Claude Code session can reach every host on your LAN, which is how the script scans for the TV. You can turn on sandbox.enabled in ~/.claude/settings.json and set network.allowedDomains to limit that.

TechCrunch also reports bricked devices and failed installs.

Bottom line

This is a legitimate, reversible way to strip TCL-style promos off an Android TV, and Gupta's project backs up first and ships a restore script. It is not a new Claude Code feature, it disables apps rather than deleting them, and the speed claim has no measurement behind it. Turn debugging off when you finish.

Sources

Published October 19, 2026. Based on a TikTok by @chase_ai_. Full video notes (markdown)