AI WORLD HQHow to Ask GitHub Copilot to Explain a Confusing Error Message
A beginner's way to turn cryptic red text into a clear, friendly to-do list
In short: GitHub Copilot's chat can read a confusing error message, explain it in plain English, and list the most likely fixes. You paste the error, ask a short question, and follow up like a conversation — no coding experience required.
You don't need to be a developer to get value from this. Plenty of people run into walls of red text while learning to code, tweaking a website, or running a script at work. GitHub Copilot (an AI coding assistant from GitHub that lives inside your code editor) can act like a patient tutor who reads the error out loud in normal words. One honest limit: Copilot can explain the error and suggest fixes, but it can't actually run your code or apply changes for you — you're still the one who decides what to do with the answer. Here's the beginner-friendly way to use it.
💡 Tip: tap a step’s number when you finish it — a green tick appears and your browser remembers how far you got.
- A free GitHub account, signed in to your browser. Some chat features may require a paid plan — check the official pricing page if you hit a usage limit.
- VS Code installed on your computer (a free code editor from Microsoft — if you don't use VS Code, the same chat also works on github.com; open any repository and look for the Copilot icon there).
- The full error message, ready to copy from your terminal, browser console, log file, or code editor.
- Roughly 5 minutes.
Install the Copilot extension in VS Code
Open VS Code and look at the left edge of the window — a thin vertical bar with several icons. One of them looks like four small squares with one corner slightly pulled out (the Extensions icon). Click it once. A new panel slides open on the left with a search box at the top. Type GitHub Copilot into that box and press Enter. The first result is usually the official extension published by GitHub. Click the green Install button on its page. After a moment, a new icon shaped like a small chat bubble appears in the same left sidebar.
If you can't find the Extensions icon, press Ctrl + Shift + X (Windows/Linux) or Cmd + Shift + X (Mac) — that opens the same panel from anywhere. You'll know it worked when a chat-bubble icon shows up in the left sidebar and VS Code shows a small pop-up asking you to sign in.
Open the Copilot chat panel and sign in
Click the new chat-bubble icon in the left sidebar. A panel opens on the right (or left, depending on your layout) with a text box at the bottom and a friendly greeting at the top. The first time you do this, VS Code pops up a small window asking you to sign in — click Sign in to GitHub, follow the browser tab it opens, and click Authorize when GitHub asks. Back in the editor, the chat panel becomes active and the cursor blinks inside the text box.
If you can't spot the chat-bubble icon after installing, look under the View menu for Open View…, or just press Ctrl + Shift + I (Windows/Linux) or Cmd + Shift + I (Mac) to open the chat panel directly. You'll know it worked when you see a blinking cursor inside a text box labeled something like "Ask Copilot" or "Send a message to Copilot".
Paste the full error message
Click inside that text box and paste your error. To paste, press Ctrl + V (Windows/Linux) or Cmd + V (Mac). The error text appears in the box, usually in a fixed-width font. Try to copy the whole error — most error messages come with a list of file names and line numbers right under the headline (called a stack trace — think of it as the breadcrumbs the error left behind), and that extra context is what helps Copilot guess the cause. If the error came from your browser, open the Console tab first (look under the browser's More Tools menu), then copy from there.
You'll know it worked when the error text sits in the chat box exactly as it appeared on screen, including any numbers and file names.
Ask for a plain-language explanation
Right after the pasted error, in the same box, type one short sentence asking Copilot to translate it for you. The question shapes the answer — keep it simple and direct. Press Enter to send. Within a few seconds, Copilot replies with a friendly explanation of what the error means in everyday words. If you don't see a reply right away, look for a small stop or regenerate icon just below your message and click it.
You'll know it worked when the reply describes the problem in normal English — something like "your code tried to use a list that doesn't exist yet" — instead of just repeating the original error back to you.
Ask for a checklist of likely fixes
Don't stop at the explanation. In the same chat box, type a follow-up asking for a short list of the most likely causes and what to check first. Copilot usually replies with a numbered list — each item is a guess to test against your own code. Treat the list as a checklist, not a verdict: not every suggestion will fit your situation, and that's perfectly normal.
You'll know it worked when you get a numbered list with at least three concrete things to check, like "the variable might be empty" or "the function might be called before the data loads".
Test each suggestion against your own code
Open the file the error mentioned (in our example, App.jsx on line 14) and read the line Copilot pointed to. See which suggestion fits. If none of them seem to match, paste a small chunk of your actual code into the chat and ask which suggestion is most likely. This is where the AI becomes genuinely useful — instead of guessing blindly, you compare each idea to the real code in front of you.
You'll know it worked when at least one suggestion clicks — you think "oh, that's probably it" — and you have a clear next step to try.
Ask a follow-up when something still doesn't make sense
If a word in the explanation or the list is unfamiliar, just ask. Tell Copilot exactly which term confused you, and it'll rephrase that one part for you. This is the secret most beginners miss: the chat is a conversation, not a one-shot answer. Each follow-up makes the next answer tighter and more useful for your specific situation. If an answer goes off-track, look for a small refresh or try again icon to get a fresh draft.
You'll know it worked when you can say the idea back in your own words and you have at least one concrete thing to change in your code.
- Pasting only the first line of the error. The lines below it (the stack trace — the list of which files and lines were involved) usually point to where things actually went wrong. Copy the whole block, not just the headline.
- Forgetting to say what language or library you're using. "Null" in JavaScript and "NULL" in a database mean similar but different things. Add one short line at the start of your message: "I'm using React."
- Trusting the very first answer as the final answer. Copilot can be confidently wrong, especially for unusual setups. If two or three suggestions don't match your code, don't force the fourth — go back to the original error and ask again with more detail.
Open the Copilot chat panel, paste the last error message you ran into — even if it's from yesterday — and send this single line:
You'll have a clear answer in under a minute.
❓ Quick questions
How long does this take?
About 6 minutes — the guide has 7 steps, and you can tick each one off as you go.
Which tool do I need?
This guide uses GitHub GitHub Copilot — but the approach works very similarly in other AI assistants.
Do I need to prepare anything?
- A free GitHub account, signed in to your browser. Some chat features may require a paid plan — check the official pricing page if you hit a usage limit.
- VS Code installed on your computer (a free code editor from Microsoft — if you don't use VS Code, the same chat also works on github.com; open any repository and look for the Copilot icon there).
- The full error message, ready to copy from your terminal, browser console, log file, or code editor.
- Roughly 5 minutes.
What mistakes should I avoid?
- Pasting only the first line of the error. The lines below it (the stack trace — the list of which files and lines were involved) usually point to where things actually went wrong. Copy the whole block, not just the headline.
- Forgetting to say what language or library you're using. "Null" in JavaScript and "NULL" in a database mean similar but different things. Add one short line at the start of your message: "I'm using React."
- Trusting the very first answer as the final answer. Copilot can be confidently wrong, especially for unusual setups. If two or three suggestions don't match your code, don't force the fourth — go back to the original error and ask again with more detail.
Keep reading
✦ Original step-by-step guide by AI World HQ's AI editorial team. Written in plain language, reviewed for accuracy.
← Back to all stories