ERA OF MINDS

xj-scanner: how Claude Code reads a 1994 Jeep's engine computer for about $15 (and how to set it up)

Short answer

xj-scanner is the free GPLv3 repo behind the viral "Claude reverse engineered my 32-year-old Jeep" video. A $3 Arduino Nano and three wires connect a 1991-95 Jeep's diagnostic plug to a laptop, and Claude Code or Codex then reads fault codes, live engine data and drive logs, and can run the engine computer's built-in tests. The parts cost about $15. It was tested on one car, a 1994 Cherokee XJ 4.0L, so you must measure your own plug first: on that car, cavity 6 carries 12 volts and shares a wire color with ground. To try it, clone the repo, open it in Claude Code and say "Help me hook this up to my Jeep."

Era of Minds cover: xj-scanner, Claude Code reads a 1994 Jeep. A retyped copy of Muhammad Zulali's X post (1.67M views, 11.3K bookmarks): Claude reverse engineered my 32-year-old Jeep. Below, the tested wiring: Nano D10 to plug cavity 4 (PCM transmit), D11 to cavity 3 (PCM receive), GND to cavity 2 (ground), and cavity 6 is 12 volts with the key on, connect nothing.
Figure: Muhammad Zulali's X post retyped by us (not a screenshot), with the tested wiring from the xj-scanner repo docs, checked November 12, 2026.

Muhammad Zulali (@zulali) posted a nine-minute video on X at 17:19 UTC on November 10 (9:19 PM in Dubai): "Claude reverse engineered my 32-year-old Jeep. Then it started controlling it." By 10:25 Dubai time on November 12 it had 1,669,009 views, 18,349 likes, 11,274 bookmarks and 1,667 reposts, plus 597 replies and 595 quotes (X API). The bookmark count is the tell: more than 11,000 people saved it to try later. X logged 341 posts mentioning the Jeep or xj-scanner on November 10 and 1,249 on November 11.

The story, in his YouTube video description: his 1994 Jeep Cherokee has no OBD2 port and no scan tool that works on it, so he wired a $3 Arduino to the engine computer and had Claude Code and Codex figure it out. "Over about a week they read the computer live, logged my drives, copied its entire program, and ran their own code inside it." Sixteen minutes before the post he published the tool as MZULALI/xj-scanner on GitHub. It had 128 stars and 15 forks on the morning of November 12.

What is xj-scanner?

It is a small scanner for one family of old engine computers, written so that a coding agent can run it for you. The README sums it up: three wires go from the diagnostic plug under the hood to a Nano, the Nano plugs into your laptop over USB, and from there "Claude Code, Codex or any coding agent can read fault codes and live engine data, log a drive, and run the computer's built-in tests."

The repo has four parts:

  • arduino/: the Nano sketch (xj_bridge) that passes bytes between laptop and car, plus a wiring debug sketch.
  • pc/: xj_scan.py, a Python scanner for fault codes, live data, logging and actuator tests. Its only dependency is pyserial.
  • docs/: the plug cavity by cavity, the wiring, the protocol, every parameter and its scaling, and troubleshooting.
  • AGENTS.md and .claude/skills/: step-by-step playbooks (hookup, scan, first-contact) that tell the agent how to walk a beginner through it.

The last part is what makes it different from older hobby scanners. The protocol knowledge itself comes from ChryslerScanner by László Dániel, which the README credits for the parameter IDs, scaling and fault code text.

What can Claude Code do with the Jeep through xj-scanner?

JobWhat it sendsJust reading?
Read stored fault codes10Yes
Live data: rpm, coolant and intake temperature, throttle, MAP, O2, battery, spark advance and more14 <id>, about 12 values in half a secondYes
Log a drive to CSV in pc/logs/repeated 14 readsYes
Copy the computer's 32 KB program15 <hi> <lo>, about 18 minutesYes (read-only)
Actuator tests: fuel pump relay, an injector, a coil, a fan13 <id>No, switches real parts
Hold an idle speed (parked only)19 <rpm/8>No
Erase codes or reset learned fuel trim17, 23 02No, wipes learned values

Commands are from the repo's protocol doc. The line runs at 7,812.5 baud and is electrically inverted, and the computer echoes every byte, so the tools send one byte, wait for the echo, then send the next.

So "started controlling it" means actuator tests and idle control, not driving. Zulali has said in replies that he plans to try making the Jeep self-driving "on a track of course," but nothing like that is in the repo.

Which cars does xj-scanner work with?

Tested on exactly one: a 1994 Jeep Cherokee XJ, 4.0L, engine computer 56030117. The README says other 1991-95 Chrysler and Jeep computers of the same family (SBEC, OBD1) "should be close," and that you should measure your own plug before connecting anything. For a car that is not the test car, the repo includes tools/pid_sweep.py to list which parameters your computer answers.

It is not for newer cars. Per the California Air Resources Board, all 1996 and newer gasoline passenger cars and trucks are required to have OBD II, which any cheap OBD-II adapter can read. When someone on X pointed out that OBD logging has been easy for years, Zulali replied: "OBD2 yes, not OBD1." That gap is the whole reason the project exists.

What do I need to build it?

PartNotes from the repo
Arduino Nano clone (5 V) and USB cableATmega328P with CH340 USB chip; the "$3" in the headline. Use a data cable, not charge-only
Small breadboard, jumper wires400-point board
Three long wiresThe test car used 15 ft each, enough to reach the passenger seat
Three 1/4" (6.3 mm) male spade terminalsInsulated; they push into the plug
MultimeterNot optional, see the 12 V warning below
Laptop with Python 3 and arduino-cliPlus Claude Code, Codex or another coding agent

The README puts the parts at about $15. That excludes the laptop and whatever plan your coding agent needs.

How do I set up xj-scanner with Claude Code?

The easy way is the one the author recommends: clone the repo, open it in Claude Code or Codex, and say "Help me hook this up to my Jeep." The agent reads AGENTS.md, which tells it to go one step at a time and wait for you to report what you see. These are the steps it follows, from the hookup skill:

  1. Prove the laptop side first. Create a virtual environment, install pyserial and run pc/xj_scan.py --cli DEMO. You should see "PCM is talking," two made-up fault codes and rows of live values from a simulated Jeep.
  2. Put the sketch on the Nano. Install arduino-cli and the arduino:avr core, then compile and upload arduino/xj_bridge. If upload fails with "not in sync," switch between cpu=atmega328old and cpu=atmega328. With nothing wired, the scanner should find "XJBRIDGE 1.0" and then stop with a "no echo" error, which is correct at this point.
  3. Build three wires (A to D10, B to D11, C to GND), label them, and check continuity end to end. No resistors.
  4. Measure every cavity with the key ON and write the table down with the agent. If your pattern does not match the test car, stop.
  5. Connect with the key OFF: ground (C) first, then B, then A, each spade pushed fully in. Then key ON, engine off.
  6. First contact: pc/xj_scan.py --cli auto --codes. Good looks like "line idles LOW: looks right for OBD1 with the key ON," then "PCM is talking. Battery 12.xx V," then your codes.
  7. Log something: --cli auto --seconds 20, then ask the agent to explain the values in plain words.

How do I wire the Arduino Nano to the Jeep diagnostic plug?

The plug is a 6-cavity connector under the hood near the engine computer. The repo numbers it down each column, looking into the plug, and warns that it found no factory map for the 1994 plug, so don't trust diagrams online. Measured on the test car:

CavityWire colorKey ONWhat it isConnect to
2 (bottom left)black/white0 VGroundNano GND
3 (top middle)greenabout 5 VPCM receiveNano D11
4 (bottom middle)pinkabout 0 VPCM transmitNano D10
6 (bottom right)black/white12 VSwitched 12 VNothing, ever
1 and 5noneEmptyNothing

Source: docs/connector.md. The Nano is powered from the laptop's USB, never from the car.

What can go wrong with xj-scanner?

  • The 12 V cavity looks like ground. Cavity 6 has the same black/white wire as ground, and it even beeps on a continuity test with the key off. Confirm ground as 0 V with the key ON. Since the tested wiring has no series resistor, a wire in cavity 6 goes straight into a Nano pin and can kill it.
  • A pull-up resistor stops it working. The first version had a 1 kΩ pull-up on D10, and nothing was ever received. Removing it fixed the problem (wiring doc).
  • Fuel trim reads wildly wrong in other tools. On this computer 128 means no correction and one count is about 0.26% of fuel. ChryslerScanner's formula turns raw 110 into "+21.6%" when it means about -4.7%, and the docs say that wrong number sent "a whole day of testing" after a fuel problem that didn't exist (parameters doc).
  • Speed reads double on the test car. Halve it.
  • Erasing codes resets learning. Both erase (17) and 23 02 put learned fuel trim back to neutral, so don't do either before a drive you want to compare.
  • "Idles HIGH" usually means the key is off, wires A and B are swapped, or a spade terminal backed out. Reseat and re-measure.

Is it safe and legal to let an AI agent poke my engine computer?

The repo's own rules for the agent are a good answer. Reading is safe. Erasing codes, resetting fuel trim and actuator tests are "not just reading," and the agent must ask before each one and say what will click or spray first. It must not guess at a diagnosis, and it must report what the data does and doesn't show.

Two more lines worth knowing. The README calls it "a hobby project" that you use at your own risk. And the computer's program is the manufacturer's code, so the docs say to keep your copy to yourself. On emissions, Zulali said on X the computer has hidden dealer and factory controls, and that he didn't touch them for the smog test "since that's legally questionable." Tampering with emission controls is illegal in many places, so use this for diagnosis, then take real repairs to a mechanic.

What can I copy from xj-scanner for my own projects?

You don't need a 1994 Jeep to use the idea. The pattern is a repo where the hard knowledge lives in plain docs, and an AGENTS.md plus skills folder turns that into a patient, step-by-step guide with safety rules the agent has to follow. The same trick works for any old device with a serial port: write down what you measured, mark the dangerous commands, and make the agent prove the laptop side with a DEMO mode before touching hardware.

We have covered other ways people package know-how for agents: book-to-skill turns technical books into Claude Code skills, and Anatomy is a skill for drawing machines as interactive diagrams. If you like weekend builds with an agent, Karpathy's TristanTube is another one you can copy. And for the other side of "Claude reverse engineered it," read our take on the Supabase 12 Claude agents joke. A one-line audit prompt like the implicit state machines prompt is a good thing to run on the scanner code before you trust it with your car.

FAQ: xj-scanner and the Claude Jeep

What is xj-scanner?

xj-scanner is a free, open-source (GPLv3) GitHub project by Muhammad Zulali (@zulali on X). It lets a laptop read the engine computer of a 1991-95 Jeep through a $3 Arduino Nano and three wires, so Claude Code, Codex or another coding agent can read fault codes, watch live engine data, log a drive and run the computer's built-in tests. It is the repo behind his viral video 'Claude reverse engineered my 32-year-old Jeep.'

Which cars does xj-scanner work with?

It was built and tested on one car: a 1994 Jeep Cherokee XJ with the 4.0L engine and engine computer 56030117. The README says other 1991-95 Chrysler and Jeep computers of the same family (SBEC, OBD1) should be close, but you have to measure your own diagnostic plug before connecting anything. It is not meant for 1996 and newer cars, which have OBD-II and work with ordinary OBD-II scan tools.

How much does the xj-scanner setup cost?

About $15 in parts, per the README: an Arduino Nano clone and USB cable, a small breadboard and jumper wires, three long wires, three 1/4 inch male spade terminals and a multimeter. The $3 in the viral headline is only the Nano. You also need a laptop and a coding agent such as Claude Code or Codex, which may need a paid plan.

How do I set up xj-scanner with Claude Code?

Clone the repo, open it in Claude Code (or Codex) and say 'Help me hook this up to my Jeep.' The agent reads AGENTS.md and follows the hookup skill one step at a time: run the scanner in DEMO mode, upload the xj_bridge sketch to the Nano, build three labelled wires, measure every cavity of the plug with the key on, connect ground first, then run the first scan with the key on and the engine off.

Which pins go where on the Jeep diagnostic plug?

On the test car: Nano D10 to cavity 4 (PCM transmit, about 0 V with the key on), Nano D11 to cavity 3 (PCM receive, about 5 V) and Nano GND to cavity 2 (ground). Cavity 6 is switched 12 V and must never be connected. Its wire is the same black and white as the ground wire, so measure every cavity instead of going by color.

Can Claude really control the Jeep?

Partly. Besides reading data, the scanner can run the engine computer's actuator tests, which switch real parts such as the fuel pump relay, injectors, coils and fans, and it can ask the computer to hold an idle speed while parked. In his video description Zulali says Claude Code and Codex also copied the computer's entire program and ran their own code inside it. Driving the car is not part of the repo; he has only said he plans a self-driving experiment on a track.

Is xj-scanner safe to use on my car?

The author calls it a hobby project that you use at your own risk. Reading codes and live data is safe; erasing codes or resetting fuel trim also wipes what the computer has learned, and actuator tests switch real hardware, so the repo tells the agent to ask before each one. Since the tested wiring has no resistors, a wire pushed into the 12 V cavity can kill the Nano, which is why measuring first matters.

Does xj-scanner work on OBD2 cars?

No. It talks the SCI protocol of Chrysler's early-1990s SBEC computers. US cars and light trucks from the 1996 model year on have OBD-II, which standard OBD-II adapters and apps already read. Asked about this on X, Zulali replied 'OBD2 yes, not OBD1,' meaning plug-in OBD logging is the easy road on newer cars, while this project exists because his 1994 Jeep has no such port.

Sources

FREE WEEKLY AI BRIEF

Free. Unsubscribe anytime. Free gift: 50 AI prompts that actually work, sent the moment you join. More about Decoded