Claude Code and Codex read a 1994 Jeep’s engine computer with a $3 Arduino
A hobbyist connected an Arduino Nano to an old Jeep’s diagnostic connector. Through it, coding agents read fault codes and driving data, switched on the fuel pump and ran their own code on the engine computer. The wiring and the agent instructions are openly available.
In a YouTube video, GitHub user MZULALI describes how Anthropic’s Claude Code and OpenAI’s Codex spent about a week examining the engine computer of MZULALI’s 1994 Jeep Cherokee. The video scored 351 points on Hacker News.
The car lacks the OBD2 port used to read newer cars. The author said Claude worked out that the engine computer communicates over SCI, an old, slow protocol with an inverted signal. An Arduino Nano microcontroller board costing about $3 relays the signal. It connects with three wires to the diagnostic connector under the bonnet and to a laptop over USB.
It all began when the car failed California’s emissions test at 25 mph because of excessive nitrogen oxide (NOx) emissions. These form when the engine runs lean, the author said.
From reading to control
The agents read fault codes and driving data. Claude also switched on the fuel pump through the engine computer. The pump ran for about ten seconds until the author asked Claude to stop.
With the scaling used by László Dániel’s ChryslerScanner program, the engine computer’s fuel correction appeared to add 22 per cent more fuel to the mixture. From logs of a night drive, Claude concluded that the computer was in fact removing fuel. The mixture had been fine all along, the author said. The repository states that the correct scale came from disassembled code for the SBEC engine computer, published in the AR1972/jeep_2.5L repository.
Claude copied the engine computer’s entire program to the laptop. The author said the program revealed that the unit is the California version, which removes more fuel under test loads than the federal version. An hour of driving put the difference at about a quarter of a per cent of fuel. The author sees this as a possible reason for the failed test. Figures in the video’s machine transcript may have been misheard, and the author says they are not a mechanic.
The agents’ own code on the engine computer
Reprogramming the engine computer failed. The author said the unit was made in December 1993, about four months before these units gained the parts needed for programming.
Codex found another way. The same three wires can carry a small program to the unit, which runs it as part of its own loop about 90 times a second. Within a few seconds the unit’s own code overwrote the program loaded into RAM, so Codex stored the program in EEPROM, which keeps its contents when the power is off.
The car eventually passed the emissions test. The video does not say what the agents’ code did or whether it caused the pass.
Availability and risks
The wiring instructions, programs and agent instructions are on GitHub under the GPLv3 licence, and the parts cost about $15. The tool has been tested only on the author’s car (4.0-litre engine, engine computer 56030117). Other Chrysler and Jeep engine computers in the same SBEC family made in 1991–95 should be similar, the author said.
Cavity 6 of the connector carries 12 volts when the key is on, and nothing must be connected to it, because the voltage can damage the Arduino. On the test car its wire is the same colour as the earth wire, so every cavity must be checked with a multimeter before connecting anything. The author describes the tool as a hobby project to be used at one’s own risk. The repository’s AGENTS.md file directs the coding agent to guide the user through the wiring step by step.
Read more: How an agent works · Agent map