Different tools create different habits, so "code without AI" means something slightly different depending on which one you've built your workflow around. Quick breakdown of what to expect turning each one off. For the tool-agnostic rebuild plan, start with How to Code Without AI.
Without ChatGPT
If ChatGPT is your workflow, you're probably used to context-switching — copy error, paste into browser tab, copy answer back. The muscle you lose fastest here is debugging by reading, not asking. Next time you hit an error, force yourself to read the actual stack trace top to bottom before you'd normally alt-tab to the chat. Most of the time the answer's already there; you just stopped looking because asking was faster.
Without Claude (Code / Desktop)
Claude Code and similar agentic tools go further than chat — they don't just answer questions, they execute multi-step changes across your codebase, often without you reading every diff. Turning it off exposes a different gap: architectural decision-making. Before your next feature, sketch the file structure and approach on paper first. If you can't, that's usually a sign the agent's been making those calls for you by default, not because you delegated them on purpose.
Without Copilot
Copilot's habit is subtler — it's autocomplete, so the loss isn't "I can't solve problems," it's "I've forgotten what typing a full function feels like." Turn off inline suggestions for a day (most editors let you toggle this without uninstalling anything) and just write. You'll be slower. You'll also notice how many of your "own" functions you were actually just accepting keystroke by keystroke.
The common thread
Regardless of which tool you're stepping back from, the actual skill being tested is the same: can you hold a problem in your head long enough to work through it, instead of outsourcing that holding to something else? Turning off one tool for an afternoon is a fine way to find out. Turning it off for good isn't really the goal — knowing what you'd lose if it disappeared tomorrow is. If you're trying to cut the habit permanently, How to Quit Vibe Coding is the more direct path.
Want a number on it instead of a guess? The test scores this across a few different angles, not just "do you use AI a lot."
Related reading: for a broader, tool-agnostic rebuild plan, see How to Code Without AI. If you're trying to cut back permanently rather than just practice, How to Quit Vibe Coding is the more direct one.
→ Learning from scratch: Learn Programming Without AI
→ Break the habit: How to Quit Vibe Coding
→ Pillar: How to Code Without AI