Wiki/When you get stuck
When you get stuck
When you get stuck
Getting stuck does not mean you are doing something wrong. It happens often, for everyone. Please remember just two things.
Do not clear the error message. When a wall of red text appears you will want to close it, but that text is the only clue to what went wrong. And you do not have to struggle with it alone for long. Just take a screenshot and send it.
Who to ask
Ask Joonhyung Bae directly. Send a screenshot on KakaoTalk. Late hours are fine. I will look at it and get back to you.
Sorting out where you are stuck is my job. It is fine to ask the same thing more than once, and fine if it seems minor.
You can also post in the group chat. Someone near you has probably run into it first. On the personal page you were given, the questions and answers pile up, so it is easy to look things up again later.
It is faster if you add one line with the screenshot about what you were doing when it happened.
Find it by symptom
| If you see this message | Look here |
|---|---|
command not found, 'git' is not recognized as an internal or external command… | command not found |
git push says Authentication failed, or no login window opens | git push login failure |
| You do not know how to start the practice web app again | Reopen |
| The practice web app is running but you do not know where to begin | One full round |
| You do not know where to get the APIFrame key | APIFrame key |
| You do not know what the exercise looks like as an artwork | Toward the exhibition |
Ask Cursor first
Copy the error message as it is, paste it into the Cursor chat and write "Fix this error". About half the time, that solves it.
If it still does not work, write down in order what you were doing when it happened. Cursor cannot see your screen, so the more context you give, the more accurate the answer.
When a fix made things worse
If you do not like what Cursor changed, undo it. So do not be afraid to ask it to try all sorts of things.
- Undo just the last change. Press Ctrl/⌘+Z in the editor.
- Undo a whole batch. Click Restore Checkpoint on that reply in the chat. This takes you back to a save point Cursor makes before each large change to your files. The conversation stays as it is.
- Throw away everything you changed today. Write
Throw away all my changes and go back to the last commitin the chat.
Checkpoints are not Git. They stay briefly on your computer only, they do not capture edits you made by hand, and old ones disappear on their own. The only place you can really rely on going back to is a commit, so commit whenever things are working (Uploading to GitHub). Checkpoints are explained in detail in the official Cursor docs.
Once you know you can always go back, you ask for bolder things. Trying all sorts of things like that is the fastest way to get better with this way of working.