Running Tesla Model 3 Computer on Desk with Salvaged Parts
Hardware Setup from Salvaged Parts
A researcher needed Tesla hardware for bug bounty research and sourced components from crashed vehicles. The Tesla Model 3 computer consists of two parts: the MCU (Media Control Unit) and the autopilot computer (AP) layered together. The unit is iPad-sized, about as thick as a 500-page book, and comes in a water-cooled metal casing.
Searching for "Tesla Model 3 MCU" on eBay revealed multiple listings in the $200-$300 range from salvaging companies that dismantle crashed cars. These sellers often include photos of the original vehicle and allow filtering for parts from the same car.
Required Components
- DC power supply: Adjustable 0-30V model, 10A version recommended (the setup can consume up to 8A at peak)
- Touchscreen module: From salvaged Model 3, found for $175 on eBay
- Display cable: 6-pin cable with Rosenberger 99K10D-1D5A5-D connector (2 pins for 12V/ground, 4 for data)
The cable proved difficult to source individually. Tesla publishes wiring "Electrical Reference" documents publicly on their service website, showing exact pin configurations. The researcher discovered the cable is similar to LVDS cables used in BMW vehicles and ordered a compatible version.
Powering Up and Network Access
Using Tesla schematics and online references, the researcher identified the correct pins for 12V and ground on the computer's cut cables. After attaching power supply clips to the stripped wires, red LEDs began flashing and the computer started.
Without a screen, interaction was limited. The researcher connected an Ethernet cable to the port next to the power connector. The car's internal network lacks DHCP, requiring manual IP configuration: 192.168.90.X/24 with X higher than 105 to avoid conflicts.
Internal Network Details
From an older /etc/hosts file found on Reddit:
- 192.168.90.100 cid ice # mcu
- 192.168.90.102 gw # gateway
- 192.168.90.103 ap ape # autopilot
- 192.168.90.105 ap-b ape-b # also autopilot
- 192.168.90.60 modem # has the ftp server
SSH on port 22 and a webserver on port 8080 were open on 192.168.90.100 (the MCU), confirmed to still be accessible on newer models.
📖 Read the full source: HN AI Agents
👀 See Also
Managing AI Agent Failures: Retry Limits and Failure Budgets
A production team running 6 AI agents implemented a 3-strike failure budget after an agent retried a rate-limited task 319 times, burning hours of compute. They also addressed heartbeat timeouts, false task completion reports, and optimistic locking conflicts.
Claude Haiku 4.5 bug-fixing effectiveness depends heavily on prompt quality, user testing shows
Testing with 380 users on real production bugs shows Claude Haiku 4.5 can effectively fix bugs when given proper context, but results vary significantly based on how well users describe the problem.
Claude users experiment with AI-to-AI communication for difficult conversations
Two Claude users tested having their AI assistants communicate directly about sensitive topics like relationship issues, with each person reviewing messages before sending. The experiment helped surface unspoken feelings and served as a translation layer for difficult conversations.
Autonomous 5-Agent Claude System Replaces $3K/Month API Costs with Single Subscription
A developer built a 5-agent autonomous swarm using Claude Opus 4.6 running as Discord bots on WSL2, powered by a single Claude Max subscription instead of API credits, replacing what would cost $3,000+ monthly with $100-200.