Claude going off track, a broken project, a session that crawls, a hook that never fires, usage creeping up: the same things go wrong for almost everyone. Here are the 12 most common situations, what causes them, and the exact move that gets you out.
Free to read, taken from the SOS module of Koneetiv Academy.
When Claude Code goes off track, the cause is rarely mysterious: an instruction that faded, a saturated context, a setting changed without restarting the session. Each situation below is fixed with a single move. And each one is prevented by a simple habit, listed at the end of the card.
/rewind restores the code and/or the conversation./rewind, or a double press on Esc, restores an earlier state. If you had asked for a commit before starting, simply say "go back to the last commit".CLAUDE.md, which you open with /memory: they are read again at every session. For something that must apply 100 % of the time, use a hook rather than a written instruction.CLAUDE.md instead of repeating it./compact summarises the exchange and lightens it while keeping the thread. If you are moving to a new subject, use /clear and start fresh.PreToolUse is not PostToolUse; 2) the matcher targets the right tool, for example Write; 3) the session was restarted after the settings were changed./mcp to see the connector status. In most cases the authentication has expired: reconnect. Also check that access has not been revoked on the service side./mcp before looking anywhere else./compact to lighten the conversation, or move simple tasks to a lighter model./clear between tasks./model./clear between tasks, conversations focused on a single subject, and the right model for the right job. /cost shows you where the usage goes./cost now and then: you will quickly see which habits weigh the most.None of them require particular technical skill. They become second nature quickly and cover the vast majority of what goes wrong.
/clear when you change subject, /compact when the session gets heavy.CLAUDE.md, not a message. Anything that must be automatic goes into a hook.Koneetiv Academy is our training platform, free to access. It includes an SOS module that walks through these situations one by one: you describe what is happening, the module gives you the move to make and prepares a ready formatted request, which you paste into your own Claude account to unblock the situation in your own context.
It is one of the surfaces of Claude, the one that works in your terminal and directly on the files of your project. It sits alongside other surfaces, such as the Claude app and the developer platform. So it is not a separate product, but a way of using Claude as close as possible to your working environment.
No. You write your requests in plain language and Claude handles the technical side. What matters is describing precisely what you want, and knowing the few safety habits on this page: ask for a commit before a large change, interrupt with Esc, go back with /rewind.
Yes. You can phrase your requests and write your lasting instructions in CLAUDE.md in your own language. Only the command names stay as they are: /rewind, /compact, /clear, /mcp, /model, /cost, /memory.
Start with a real project that carries no risk, and one task at a time: it is the fastest way to see what Claude actually does with your requests. Ask for a commit before anything important, keep conversations short, and use /clear as soon as you change subject. Two or three working rules written into CLAUDE.md are enough to begin with, and you will add to them as you go. Koneetiv Academy takes you through that path step by step, free of charge.
The SOS module handles the emergency. The rest of the training keeps you out of it. Free, with no technical prerequisites.
Talk to a Koneetiv expert