← Back to the rebuild

How my agentic AI-to-BMW link works

During the diagnostic days on my N63 (Chapter 13) I wasn’t alone with a scan tool. My Grok Agent was my partner on the other end of the cable — reading codes, watching live data, looking things up and taking notes. Here’s the short version of how that’s wired up. The best part: anyone can do this.

The chain

Grok Agent → Mac mini → SSH → Pop!_OS laptop → ENET cable → car’s OBD port → engine computers

• The agent works from my Mac mini, and I can reach it from my phone. It never touches the car directly.
• The Mac mini opens an SSH session to the laptop on my home network.
• The Pop!_OS laptop sits by the car with an ENET cable — the Ethernet diagnostic cable F-series BMWs use — plugged into the OBD port. The agent set it up with open-source code from GitHub that can talk to the car’s computers.

The tools

On the laptop there are a few small command-line tools, with deliberately obvious names:

• bmw-scan — read the stored fault codes.
• bmw-live — watch live data while the engine runs.
• bmw-clear-dtc-WRITE — clear fault codes. The “WRITE” is in the name on purpose.

Guardrails

• Read-only by default. Reading codes and live data doesn’t change anything in the car.
• Writes need me. Anything that writes — even just clearing codes — only happens after I explicitly say yes.
• No coding or programming. The agent doesn’t code modules or flash ECU software.

Why it helps

The agent writes down every code, value and step as it happens — human memory fails, or worse, misremembers. It reads the manuals and online docs in seconds and acts like a subject-matter expert at the fender. I still turn the wrenches and make the calls.

Full technical details — the libraries, protocol and setup — are coming soon.