Tune your car with an AI co‑pilot.
Let Claude and other AI agents drive your Haltech, Link or MaxxECU software, read your datalogs line by line, and learn how your engine behaves. You still make the calls. The agent does the tedious part.
Three ways an AI agent can sit beside you at the laptop
Tuning software was built for people to click through. Modern AI agents can look at a screen, read a spreadsheet, and remember what you told them about your engine. Put those three together and you have a tireless tuning assistant.
Computer use: let it drive the software
Claude can take screenshots, move the mouse and type. It can find tables, read live values, export logs and stage edits in NSP, PCLink or MTune while you watch.
Computer use guide →Datalog analysis: let it read the logs
Export a CSV and an agent will go through every row. It flags lean spots, knock, temperature creep and sensor faults, then lines each one up against your fuel and ignition tables.
Datalog guide →Teach it: give it your engine's context
A skill or project file holds your engine spec, what each channel means, your safe limits and your method. The agent reads it every session, so it never starts cold.
Teaching guide →Same tuning process, with a faster analyst in the loop
You don't hand over your tune. The agent takes the slow parts: reading 10,000 rows, cross-referencing table cells, writing up what changed. Every change still goes through you.
Capture a good log
Steady-state cruise, a controlled pull, a cold start. Log the channels the agent needs. The channel checklist lists them.
Export & hand it over
CSV export from your ECU software, or let a computer-use agent do the export for you.
Get a written diagnosis
Findings ranked by severity, with timestamps, RPM/load cells and the evidence for each.
You approve the change
Proposed edits are small and reversible, and you apply them to a saved copy of the map. Nothing touches the engine until you say so.
“Why does it stumble at 3,000 rpm cruise?”
This is the kind of question agents handle well. They line every channel up against every other one and spot patterns that are hard to see when you scrub through a log viewer by hand.
Tip: tell the agent what the car felt like and where. "Stumbles on light throttle, 3rd gear, around 3k" narrows 50,000 data points down to a few hundred.
I found 11 stumble events. They all share one pattern:
- Lambda swings 0.94 → 1.09 within ~0.3 s, always when
MAPcrosses 58–62 kPa. - That's the boundary between your 55 and 65 kPa VE rows. The 65 row is ~7% leaner than its neighbours at 3,000 rpm.
- Closed-loop trim hits its −10% limit just before every event, so it can't correct.
Suggestion: blend the 3,000 × 65 kPa cell up about 5% and re-log. Want me to list the exact cells and values to check in PCLink?
If it logs to CSV, an agent can read it
The method works with any standalone ECU. Below are the three platforms we cover in most depth, each with its own notes on exporting logs and the channel names it uses.
Nexus · Elite
NSP — Nexus Software Platform- Export data logs to CSV from the log viewer
- Channel names are clear and agents read them easily
- Clean, consistent UI that computer use can find its way around
G4X · G4+
PCLink- PC logging and onboard ECU logging
- Log viewer exports to CSV
- Run the agent on a saved copy of the map for safe what-if edits
Race · Pro · Sport
MTune- Internal SD logging, so long sessions are easy
- Export from MTune's log view for the agent to read
- Many tables, so a channel dictionary is worth writing
All platforms: ECUMaster, MoTeC, Emtron, Speeduino and more →
The agent is the analyst. You are the tuner.
AI agents are confident, fast and sometimes wrong. Engines are expensive. These four rules are not optional.
Never live-write unattended
Don't let an agent write to an ECU on a running engine without you watching each step. Stage changes in a saved copy of the map first.
Back up every map
Save a dated copy before every session. Ask the agent to write a change log you can roll back from.
Set hard limits
Write your limits into the agent's instructions: max timing, min lambda under boost, max change per step (e.g. 3%).
Trust sensors, not vibes
A wideband, knock monitoring and EGTs where you can. If the data and the agent disagree, believe the data.
What you need
An AI agent
Claude (desktop app for computer use, or Claude Code for analysing files). Any capable agent that can run code will work.
Your ECU software
NSP, PCLink, MTune or similar, on a Windows laptop or VM the agent can see.
Questions people ask about AI tuning
Can AI tune my car?
An AI agent can do a lot of the analysis: reading every row of a datalog, finding lean spots and knock, lining errors up against your fuel and ignition table cells, and proposing small changes. It should not be the tuner. You review and apply every change, ideally on a dyno or with a qualified tuner, and you keep backups of every map.
Can Claude read Haltech, Link or MaxxECU datalogs?
Yes, once they are exported to CSV. Native log formats generally need the vendor's software to open, but NSP, PCLink and MTune can all export logs as CSV, which Claude can load and analyse with code.
What is computer use, and can it control my tuning software?
Computer use lets an AI agent see your screen and use the mouse and keyboard. That means it can work inside NSP, PCLink or MTune: finding tables, reading values, exporting logs and staging edits on an offline map copy while you watch. We recommend keeping it away from live ECU writes.
Is it safe to let an AI change my ECU map?
Only with guardrails: work on a saved copy of the map, set hard limits (minimum lambda, maximum timing, maximum change per step), approve every change yourself, and never let an agent write to a running engine unattended. AI agents can be confidently wrong.
Do I need to know how to code?
No. Agents like Claude write and run the analysis code for you. It helps to save that code as a script once you like the results, so every future log is checked the same way.
What do I need to get started?
An AI agent (for example Claude), your ECU's tuning software, a datalog with wideband lambda, RPM, load, ignition, knock and temperatures, and a short brief describing your engine. Our free sample log and skill template cover the last two.
Is VibeTuners free?
Yes. The guides, prompts, sample datalog, skill template and script are free. The site is supported by KrispyGauge and Krispy Workshop in New Zealand.
VibeTuners is free, thanks to KrispyGauge & Krispy Workshop
We build digital gauges, dashes and ECU installs in New Zealand. We made this site because AI changed how we tune, and we wanted everyone to have the same head start.
See it live with KrispyGauge
Your agent finds the problem in the log. A KrispyGauge shows it to you on the road while it happens. The 52mm multi-protocol CAN bus gauge reads your ECU's data stream directly.
- Haltech, Link, MaxxECU, ECUMaster, Emtron & more
- Standard 52mm fit: lambda, boost, temps and more
- Designed & built in New Zealand
Want it done properly?
AI can tell you the wiring or sensor is the problem. Krispy Workshop can fix it. Factory dash to digital conversions, custom dash builds, ECU installs and clean automotive wiring.
- ECU installs & wideband / sensor upgrades
- Factory dash → digital conversions
- Custom looms and tidy, documented wiring