Trace a check-engine code and a tank that won't fill to a stuck valve with Grok, and fix it for $120
- Posted
- by Christopher Wipper (X)
- Last checked
- Method:
- How we verify
Evidence: Screenshots or logsThe source shows screenshots, a transcript or the agent's output.
Outcome
Christopher Wipper's mechanic wanted $169 just to troubleshoot a check engine light. AutoZone's free OBD2 scanner gave code P0458 (purge control valve circuit low), and the car wouldn't take fuel: it backed up in the fill tube. With no YouTube videos for the problem, Wipper used Grok to troubleshoot step by step: the air drain case on top of the fill port was clear, but the canister close valve's solenoid was stuck closed. Wipper had the replacement part in hand in 20 minutes and fixed it for $120 in less than an hour.
Agent
Prompt Recreated prompt
The source didn't share its exact prompt, so we wrote this from what it describes.
Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to. Goal: Help me work out what's causing this fault code and symptom, starting with the cheapest and easiest checks. Fill in before running: - Car (year, make, model, engine): [DETAILS] - Fault code(s) from the scanner: [CODES] - Symptoms and when they happen: [DETAILS] Safety first: anything touching brakes, steering, airbags, fuel lines or lifting the car is a job for a qualified mechanic unless I confirm I have the tools and experience. Say so clearly. Rules: - Explain what the code means in plain words. - List the likely causes from most to least likely, with a quick check for each. - Walk me through one check at a time and wait for what I find before moving on. - Tell me which part to buy only once a check points to it, and roughly what it costs. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. Output: A step-by-step check list and, once found, the likely faulty part. You'll know it worked when: I find the faulty part and the light stays off after the fix.
Customize this prompt
Answer these questions and we'll put your answers into the prompt for you. You can leave any of them empty.
Your prompt
Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to. Goal: Help me work out what's causing this fault code and symptom, starting with the cheapest and easiest checks. Fill in before running: - Car (year, make, model, engine): [DETAILS] - Fault code(s) from the scanner: [CODES] - Symptoms and when they happen: [DETAILS] Safety first: anything touching brakes, steering, airbags, fuel lines or lifting the car is a job for a qualified mechanic unless I confirm I have the tools and experience. Say so clearly. Rules: - Explain what the code means in plain words. - List the likely causes from most to least likely, with a quick check for each. - Walk me through one check at a time and wait for what I find before moving on. - Tell me which part to buy only once a check points to it, and roughly what it costs. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. Output: A step-by-step check list and, once found, the likely faulty part. You'll know it worked when: I find the faulty part and the light stays off after the fix.
Scroll to see the whole prompt. Your answers show in green.
3 blanks are still empty: Car (year, make, model, engine); Fault code(s) from the scanner; Symptoms and when they happen. They'll stay in brackets in your prompt, so the chat tool may ask you about them.
What you type stays in this browser tab. We don't send it or save it, and it's gone when you leave the page. If you use a "Try this in" button, your answers go to that tool as part of the prompt.
Try this in:
This prompt has blanks to fill in, like [DETAILS]. We'll copy it instead of filling it in, so you can edit it before you send.
Opens in a new tab. We don't see what you send.
These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.
Optional stronger version
Our rewrite with extra checks. The poster didn't test it.
Run this task now, exactly as written below. Everything you need is here, so start straight away and only stop if something required is missing or a rule below tells you to. Goal: Help me work out what's causing this fault code and symptom, starting with the cheapest and easiest checks. Fill in before running: - Car (year, make, model, engine): [DETAILS] - Fault code(s) from the scanner: [CODES] - Symptoms and when they happen: [DETAILS] Safety first: anything touching brakes, steering, airbags, fuel lines or lifting the car is a job for a qualified mechanic unless I confirm I have the tools and experience. Say so clearly. Rules: - Explain what the code means in plain words. - List the likely causes from most to least likely, with a quick check for each. - Walk me through one check at a time and wait for what I find before moving on. - Tell me which part to buy only once a check points to it, and roughly what it costs. - Check facts that can change (prices, opening hours, dates, availability, rules) against the official source, and tell me anything you couldn't verify. - Tell me how to confirm the fix (clearing the code and what to watch for). Output: A step-by-step check list and, once found, the likely faulty part. You'll know it worked when: I find the faulty part and the light stays off after the fix. Before you finish: re-read my goal and constraints, check your answer against each one, and list anything you assumed or couldn't confirm.
Source
https://x.com/SGTWipper1Each/status/2093820992091005386
Related cases
- Fix check-engine lights on three vehicles by asking ChatGPT and Grok what forums say about the codesEvidence: Described by poster
The poster reads codes with a scanner, then runs them through Google, ChatGPT and Grok, asking for the most likely causes based on online forums and reviews, and works through each likely fix with YouTube. They say the top-ranked fix has been right each time, and that they've fixed check-engine lights on three vehicles this way in two months: a Toyota 4.7 and Ford 6.0 and 7.3 engines.
ChatGPT, Grok · Personal · Source date:
- Replace a car sensor with Grok's help (it pointed the wrong way for 40 minutes)Recreated promptEvidence: Described by posterPartial
A driver replacing a sensor to clear a check engine light says Grok led them astray for 40 minutes; they had to use Google to find where the sensor was. Once they found it the job was easy, and the light went off. The poster's conclusion: AI is not good at fixing cars.
Grok · Personal · Source date:
- Find a check-engine air leak a mechanic missed with Grok and ChatGPTRecreated promptEvidence: Described by poster
After their mechanic swapped 3 parts without fixing a check engine light and was about to replace another, a driver stopped the mechanic and used ChatGPT and Grok instead. The driver says they found the air leak on their own and fixed the light.
Grok, ChatGPT · Personal · Source date: