What they did
The poster put their Panasonic TV, which runs Amazon's FireOS, into debug mode so it was reachable over adb on the home network, with no root access. They told Claude the model, the IP and port, and that it could only act at the level of an ordinary adb shell. The ask was to list the running services, flag the ones that might send telemetry or serve ads based on viewing, and check which could be stopped or paused. Claude ran the adb commands, read each service's permissions, and then stopped or locked down the flagged ones. The poster also had it add custom apps to the TV's home screen.
How it went
Claude pulled a list of roughly 50 services it flagged as possible telemetry and either stopped them or downgraded their permissions. A few were system-locked and kept sending data, so the poster blocked those with a firewall rule and a Pi-hole entry. Among the findings were an automatic content recognition service holding a default microphone permission and a metrics service logging what was watched, for how long, and every app launch and click. Some exploratory requests about the file system and the system partition were refused by Claude's safety classifier.
Worth knowing
The poster says framing matters: state that you own the device and only want to protect your own data. Asking it to pull session tokens, reverse engineer a login flow or build a custom boot loader got the session flagged and later requests refused. Digging too deep into system settings can brick the TV. The harness was not named, only Claude.