VibeTuners
Home / Guides / Computer use
Guide 01

Let an agent drive your tuning software

With computer use, Claude can see your screen and use the mouse and keyboard, just like you. That means it can work in NSP, PCLink or MTune even though they have no AI features built in. Here's how to set it up so it helps without putting your engine at risk.

Updated By the KrispyGauge team4 min read

How it works

Computer use runs a simple loop: look → think → act → check. The agent takes a screenshot, decides what to do, clicks or types, then takes another screenshot to confirm it worked. It isn't using a special connection to your ECU. It uses the same software you do, the same way you do.

ECU software RPM 0MAP 101ECT 24°Engine OFF ① Screenshotsee the screen ② Reasonwhat to do next ③ Actclick · type · scroll ④ Verifydid it work? You approve before any write or ECU connect the loop repeats for every step, so the agent checks its own work on screen

Claude's computer use is available in the Claude desktop app, and to developers through the API. Other vendors have similar "operator" or "computer agent" features, and everything on this page applies to them too.

Setting up

  1. Use a dedicated tuning laptop or a Windows VM. Close email, banking and anything personal. The agent sees everything on the screen.
  2. Install your ECU software (NSP, PCLink, MTune…) and open a copy of your map. Name it clearly, e.g. AI-WORKING-COPY_2026-11-02.
  3. Start disconnected. Most tuning software can open and edit a map file without an ECU attached. Do your first sessions this way.
  4. Use a sensible resolution. 1280×800 to 1920×1080 at 100% scaling. Tiny UI text at 4K is harder for the agent to read.
  5. Give it your engine brief. Load your skill or project file so it knows the car before it starts clicking.

Watch it work. Computer use is still slower and clumsier than a person. Keep your hand near the mouse, and stop the session if it starts clicking somewhere unexpected.

Autonomy levels

Decide up front how much you'll let it do, and put that in the prompt. We use five levels:

L0L1L2L3L4 Read onlyNavigate &reportEdit offlinemap copyWrite to ECU,engine offLive writes,engine running find tables, readcells, export logsstage changes youreview before savingapprove everysingle stepnot recommended.Dyno + tuner only,if ever. lower risk higher risk Start at L0–L1. Most of the value is at L2. You rarely need L3.

Good first tasks

These are low-risk jobs that save real time. None of them change your tune.

Export logs to CSV

"Open the last 5 logs in the log viewer and export each to CSV in the Logs folder." Boring for you, easy for an agent.

Read tables out

Many packages let you copy a table to the clipboard. The agent can copy your VE and ignition tables into a file it can analyse alongside your logs.

Audit your setup

Go through injector data, sensor calibrations, rev limits, boost cut and knock settings, then report anything that looks wrong for your engine brief.

Document the tune

Screenshot every important table and setting into a dated report. Good for your records, your tuner, or before selling the car.

Compare two maps

"Open map A and map B and list every setting and table that differs." Very useful after a tuner session.

Set up logging

Configure the log channel list and sample rates to match the channel checklist.

A guarded session

Paste something like this at the start of every computer-use session. It sets the autonomy level, the stop rules and what to report back.

prompt · computer-use session starter
ROLE  You're my tuning assistant, working in [Haltech NSP] on this laptop.
LEVEL L2: you may navigate, read, and edit the OFFLINE map file
      "AI-WORKING-COPY_2026-11-02". You may NOT connect to an ECU,
      upload/flash/burn, or change any file except that map.

TASK  Open VE Table 1. Increase the cells at 5000 and 5250 rpm × 200 kPa
      by the amounts in proposed-changes.md (+1.8% and +3.9%).

RULES
- Take a screenshot before and after every edit. Read the value back to confirm.
- If a dialog appears that you don't understand, STOP and describe it to me.
- If anything mentions "upload", "burn", "flash", "connect" or "write to ECU",
  STOP and ask me first.
- Never change more than the cells listed. Never change ignition tables.
- When done, list every change you made as: table, cell, old → new.

The chat below is the kind of check-in you want to see during the session:

Claude · computer use
Claude📸 screenshot · 🖱 click "Fuel" → "VE Table 1"

VE Table 1 is open. The 5000 × 200 cell reads 84.2 and 5250 × 200 reads 83.1. Applying +1.8% and +3.9% gives 85.7 and 86.3. Proceeding with the first cell.

Claude⌨ type 85.7 · ⏎ · 📸 verify

5000 × 200 now reads 85.7 ✓. A popup says "Send changes to ECU?". Stopping, as instructed. Should I click "No" and carry on offline?

YouYes, click No and carry on.

Tips that help

Name things on screen

"The table titled VE Table 1 under Fuel" is better than "the fuel map". Use the software's own labels.

Use keyboard where you can

Typing a value and pressing Enter is more reliable than drag-adjusting a 3D surface.

Split the work

Let a chat or coding agent do the maths on CSVs. Use computer use only for the clicking. Each tool does what it's best at.

Keep a change log

Ask for "table, cell, old → new" after every session and paste it into your tune journal.

Agent found a wiring or sensor problem? Krispy Workshop does ECU installs, sensor upgrades and clean looms in NZ.

Krispy Workshop →