📚 Intermediate: Contents (4/8)
  1. Build your first web page with Codex
  2. How folders, files, and HTML fit together
  3. Change an existing page the way you want
  4. Read errors and fix them with Codex
  5. Connect Google Drive and search your first doc
  6. Connect GitHub and choose repository access
  7. Connect Notion and check which pages it can see
  8. Connect Slack and summarize a channel

🔁 Cuts repetitive work

New to AI? Start here → Start 1. ChatGPT vs. Codex: what's the difference?

Last checked: November 10, 2026

Read errors and fix them with Codex

In one line

Read errors and fix them with Codex
Turn “it doesn’t work” into a description you can check again.

The big picture

Illustration (may look a little different from the real screen)

If nothing happens when you click Add
Click the picture to see it larger.

Follow along

Write down what you expected and what actually happened

Example: you type a book title and click Add, but it doesn’t appear in the list. Figure out whether the button itself doesn’t respond, or the list updates but doesn’t save.

Check the browser’s error messages too

1. Open the page with the problem

Make sure you open the file where the error happened, and click through in the same order again. Check that you aren’t looking at a different example file by mistake.

2. Open the Console in developer tools

In Chrome, choose the ⋮ menu → More tools → Developer tools, then open the Console tab. Menu names can differ by version. Don’t type any code at first. Just read the errors shown.

3. Pass along the error message and where it happened

If there’s a red error, copy the message and the file name and line number. Hide anything in the log that contains personal information or API keys. If there’s no error, say that too.

Fix one cause at a time

Illustration (may look a little different from the real screen)

After fixing, check again in the same order
Click the picture to see it larger.

Don’t decide the cause ahead of time, like “It’s probably the browser.” What matters is that it failed before the fix, and works when you repeat the same steps after the fix.

Prompts you can copy

Ask it to look into an error

Please look into the following error. Don't decide the cause yet. File: [file path] Steps to reproduce: [open → type → click] What I expected: [what should happen] What actually happened: [what I saw] Error message and location: [or none] Look at the related code and explain the evidence for the cause and the smallest fix. After fixing, check with the same steps, and mark any checks you couldn't run.

Narrow it down when fixes keep failing

I've made several fixes, but the same problem is still there. Compare what's been changed so far with the last version that worked. Find and explain the smallest piece of code where the problem still happens. Don't do any unrelated refactoring. Focus on confirming why it fails.

Where people get stuck

Lots of people get stuck here. Find the one that matches your situation!

If it keeps happening, narrow it down

If several fixes have piled up, have it compare the current file with the last version that worked. Finding the smallest part where the problem happens helps more than rebuilding the whole project.

Quick check: What’s the most helpful information to give when reporting an error?

Answer: “Steps to reproduce, what you expected, what happened, and the error message”
Give specific details of what you saw, so the same problem can be checked again.

Official sources

Next tip

Connect Google Drive and search your first doc →

I'm stuck here

Stuck while following along? Tell me where. Only the site owner sees this. Leave your email only if you'd like a reply.