seeing comments like "is this really reverse engineering?", so let me explain yes, changing wifi settings is regular admin stuff (which, for some reason, no one ever does) the reverse engineering is everything that came before that my router is a huawei from my ISP running their own firmware. There's no public API and no docs on how it works inside either, so Claude pulled the admin panel's code and figured out what actually happens when you press a button: how the login works, which internal endpoints it calls for devices, wifi and reboot, what each form sends It even found stuff that's in the code but hidden from the menu then it wrote its own controller on top of that, that's why I can just type "who's on my wifi" and everything works that's what REA is: you take a closed thing with no docs, figure out how it works from the inside and build your own tool for it. For this i used the skills from the official REA repo I also mentioned all this functionality in the post right away, hope it's clearer now why this is exactly reverse engineering! Thanks and try it!

prompt: "This is my own TV box on my own home network. I want it to work as an always-on home server for an AI agent. I will not connect to my Telegram bot, the box does the work, even when my computer is off and sends me the result, and the TV can work as a live terminal if I want. I'll turn on developer mode myself with the remote and approve the connection on the TV. I authorize you to connect to it with ADB, Android's official developer tool, and to install and configure what I want. Every change must be reversible. I've attached a photo of my TV box (or its Settings → About screen). Done means: when I send my bot /task , it answers that it started, an agent on the box does the task with the Claude API (model claude-opus-5-0) and sends me the result in Telegram, all with my laptop off. Record the run into a schedule. If I opt in, the TV becomes a live terminal that shows the agent's thinking and each line of code as it's written, and opens finished web pages. When a step doesn't need me, keep going. Identify the model from the photo. It must run Android TV, Google TV or Fire OS on Android 7 or newer. RoKu, Apple TV, Tizen, webOS and the new Vega OS Fire TVs can't run this, so tell me and stop. Warn me if it has less than 2 GB of RAM. Install adb from official sources if it's missing. Tell me exactly what to press on my remote to turn on Developer options and USB or Wireless debugging, and to find the box's IP. If adb connect is refused, use Wireless debugging pairing. On macOS, 'No route to host' usually means the terminal needs Local Network access. Install Termux and Termux:Boot from their official F-Droid releases (both from the same source), matching the CPU ABI the system reports; many boxes run a 32-bit system on a 64-bit CPU. If the box has no web browser, install TV Bro from its official GitHub releases. If Play Protect blocks an install, tell me what to press; never turn security settings off yourself. Keep Termux running with a wake lock and the battery-optimization whitelist, and try autostart with Termux:Boot. If the box blocks autostart, tell me what to open after a reboot. Before asking for any secret, create a small script that reads it with hidden input and stores it on the box readable only by Termux. Then tell me how to create a bot with @ BotFather and get an API key in the Claude Console with a monthly spend limit, and let me paste those into that script myself. Never print, log or commit a key. The bot obeys only the Telegram account that sends /start first. Use outbound long polling only and open no ports to the internet. Run the agent on the Messages API with streaming and tools to fetch a URL, write files, run Python and open a page on the TV. If the official SDK won't install on this box, call the API over HTTPS directly. Give it a short system prompt saying what it is and where it runs, ask for single-file web pages, and cap spend and steps per task. When I ask for something recurring (every hour, every morning), schedule it on the box with cron and send each result to Telegram. Ask me whether to turn the TV into a live terminal. If yes, Termux in full screen with 'waiting for a task', then the task, the model's thinking, each line of code as it's written, tool calls and a final DONE line with the cost. Run one short test task, tell me what it cost, and end. Ask me what sheet undo to send tasks, restart the agent and change a key and how everything. Never type passwords or sign in for me, never root or flash anything, no pirate sites."

link: dev.nebius.com/builders

full prompt: "This is my own TV on my own home network. It came full of preinstalled ads and apps I can't remove from the menu, and I want it clean, fast and controlled from this computer. I'll turn on developer mode myself with the remote and approve the connection on the TV. I authorize you to connect to it with ADB, Android's official developer tool, read its settings and make the changes below. Every change must be reversible. I've attached a photo of my TV or TV box (or its Settings → About screen). Done means: you're connected, the TV is cleaned of ads and bloat and runs faster, an open-source app of my choice is installed, and one command opens YouTube and plays a video I name while I watch each step on the TV. When a step doesn't need me, keep going. - Identify the model from the photo. If it isn't Android TV, Google TV or Fire TV, tell me what its official local-network control allows and do only that. - Install adb from official sources if it's missing. Tell me exactly what to press on my remote to turn on Developer options and USB or Wireless debugging, and to find the TV's IP. If adb connect is refused, use Wireless debugging pairing. On macOS, "No route to host" usually means the terminal needs Local Network access: allow it and retry. - Before changing anything, save the package list, every setting you'll touch and the undo commands. - Propose the cleanup and wait for my OK: disable (never uninstall) ad, recommendation, feedback and demo apps; never touch provider or live-TV apps, the launcher, Play Services, the keyboard or input services, or anything you can't identify; animations to 0.5; Private DNS dns.adguard-dns. com - Install apps only from their official GitHub releases, for example the TV Bro browser. - Use real key presses so I see every step, and check the screen (screenshot or uiautomator dump) before pressing OK. Screenshots of a playing video are blank because of DRM. Handle the "Who's watching?" screen. - Add a live monitor that prints each command with a timestamp and shows logcat only while a command runs. - End with a cheat sheet and the undo commands. Never type passwords or sign in for me, never root or flash anything, no pirate sites."