What you'll learn
- The difference between
--continueand--resume, and when to use each - How to name a conversation so it's easy to find again
- When to start fresh with
/clear, and when to shrink with/compact - How to undo with Esc Esc and
/rewind - What the permission modes mean, and how to switch between them
- Where settings live, and the few you might want to change
Do the try-it steps in a fresh conversation, not in the middle of real work. Any project folder is fine, for example this one: piy-projects\learn-it-yourself.
Two places to type commands
There are two moments when you can type a command, and they look different:
Before Claude starts
Typed at the plain PowerShell line (the one ending in >). These start with claude and decide how Claude Code opens.
While Claude is running
Typed in Claude's typing box. These start with a slash / and are called slash commands. They change what Claude is doing right now.
You don't have to remember the slash commands. Type just / and a list appears. Keep typing and the list narrows down. Use ↑ ↓ to pick one and Enter to run it.
One more symbol is handy: type @ followed by part of a file name to point Claude at a specific file, for example @index.html.
- Start Claude Code as usual.
- In the empty typing box, type only
/. A list of commands appears. - Type
he. The list shrinks to/helpand a few others. - Press Esc to close the list without running anything.
Continue: pick up exactly where you left off
claude --continue (short: claude -c) opens your most recent conversation in this folder, with everything you and Claude said. There's no list and nothing to choose: it simply carries on.
Use it when:
- you closed Claude Code by accident (for example, Ctrl+C twice),
- you restarted your computer, or
- you took a break and want to carry on with the same task.
Claude Code remembers conversations per folder. --continue picks the latest conversation in the folder your terminal is in right now. If you're in the wrong folder, you'll get a different conversation, or the message No conversation found to continue. Check the folder name in the line before the >.
- In Claude Code, send a short message:
Remember the word pancake. - Quit by typing
/exitand pressing Enter. You're back at the PowerShell line. - Type
claude --continueand press Enter. - Ask:
What word did I ask you to remember?Claude knows, because it's the same conversation.
Resume: choose an older conversation
claude --resume (short: claude -r) shows a list of your past conversations in this folder so you can pick one. Use it when the conversation you want is not the latest one, for example last week's chat about colours.
Already inside Claude Code? Type /resume to switch to another conversation without quitting.
- 1The list. Your conversations in this folder, newest first. Unnamed ones get an automatic title based on what you talked about.
- 2The pointer. Same as any menu: ↑ ↓ to move, Enter to open. Press Space to peek inside before opening.
- 3Searching. Just start typing a word to filter the list. Ctrl+A shows conversations from all your projects, not just this folder. Esc leaves.
Type /rename followed by a short name, like /rename budget-colours. It then stands out in the list, and you can even skip the list: claude --resume budget-colours opens it directly. (In the list itself, Ctrl+R renames the highlighted conversation.)
By default, Claude Code keeps conversations for 30 days. Anything important should live in your project files and GitHub, not only in a chat.
- Inside Claude Code, type
/rename practice-chatand press Enter. - Type
/exitto quit. - Type
claude --resumeand press Enter. The list appears. - Find practice-chat with ↑ ↓, press Space to peek, then Enter to open it.
- Bonus: quit again and try the shortcut
claude --resume practice-chat.
Which one do I use?
| Situation | Use |
|---|---|
| Carry on with the conversation I just had | claude --continue |
| Go back to an older conversation | claude --resume, then pick from the list |
| Switch conversations without quitting | /resume |
| Start a brand new conversation | just claude, or /clear if it's already running |
Pick the best answer for each situation.
Starting fresh: clear and compact
Claude can only keep a certain amount of conversation in mind at once. This is called its context: think of it as Claude's desk. Long conversations fill the desk, and Claude can start to lose track of details. Two commands help:
/clear: a clean desk
Starts a new, empty conversation. Use it when you finish one task and start something unrelated. The old conversation isn't deleted: you can still get it back with /resume.
/compact: a tidy desk
Keeps the same conversation but replaces the long history with a summary, which frees up space. Use it when you're in the middle of a long task and want to keep going.
Curious how full the desk is? /context shows it as a coloured grid.
- In your practice conversation, type
/contextand press Enter to see how full it is. - Type
/clearand press Enter. - Ask:
What word did I ask you to remember?Claude doesn't know any more: this is a new conversation. - Type
/resume. Your old practice-chat is still in the list. Press Esc to close it.
Undo with rewind
Went down the wrong path? Rewind takes you back to an earlier message in the conversation. Depending on what you choose, it can undo the conversation, the changes Claude made to your files, or both. Then you can try a different instruction.
- With an empty typing box, press Esc twice quickly. (If there's text in the box, the first double-press clears it.)
- Or type
/rewind. (/undodoes the same.) - A list of your earlier messages appears. Pick the point you want to go back to, then choose what to restore.
Rewind is a quick undo within a conversation. Save points on GitHub are your long-term safety net that lasts forever (see the GitHub Basics course). Use rewind for “oops, not like that”, and GitHub for “go back to last week's version”.
- Send:
Write a one-line poem about bread. - Send:
Now one about coffee. - With the typing box empty, press Esc Esc. A list of your messages appears.
- Choose the coffee message and go back to before it, restoring the conversation.
- The coffee poem is gone. You are back at the point before you asked for it.
Permission modes: how much Claude asks first
A permission mode decides how often Claude stops to ask “Do you want to proceed?”. The current mode is shown on the line under the typing box. Press Shift+Tab to move to the next mode.
| Mode | What it means for you |
|---|---|
| Manual (the default) | Claude may read files freely, but asks before changing files or running commands. The safest choice while you learn. |
| Accept edits | Claude changes files in your project without asking, but still asks before most commands. |
| Plan | Claude only looks and makes a plan. Nothing changes until you approve the plan. Great for bigger jobs. |
| Auto (some accounts) | Claude works without asking, while a separate safety check reviews each action in the background. Depending on your account, Claude Code may start in this mode. |
You may see “bypass permissions” mentioned online. It lets Claude do anything without any checks, and is meant only for sealed-off test computers. You don't need it.
Practise here first. Click the box below and press Shift+Tab on your keyboard, or use the button.
- Look at the line under the typing box and note which mode you're in now.
- Press Shift+Tab and watch the label change.
- Keep pressing until you see
plan mode on. - Keep pressing until you're back in the mode you started in.
Settings, model and status
You never need to edit settings files by hand. These commands open friendly screens instead:
| Type | What it does |
|---|---|
/config | Opens the settings screen: colour theme, editor mode and other preferences. (/settings does the same.) |
/model | Choose which Claude model you talk to. Your choice is remembered for new conversations too. |
/permissions | Shows the actions you've allowed or blocked. When you answer “Yes, and don't ask again”, that is saved here, and you can remove it later. |
/status | Shows your version, model and account. Handy when something seems off. |
/usage | Shows how much you've used Claude: cost, plan limits and activity. (/cost does the same.) |
/theme | Change the colours of Claude Code. |
Most settings you change are saved for you personally, across all your projects. That file lives in a hidden .claude folder in your Windows user folder. A project can also have its own .claude folder with settings just for that project, which win over your personal ones. Claude Code takes care of these files; you just use the screens above.
- Type
/configand press Enter. Move through the settings with ↑ ↓. Just look; don't change anything you're unsure about. - Press Esc to close it.
- Type
/statusand read your version and model. Esc closes it.
Teaching Claude about you
Claude starts every conversation without remembering the last one, unless you resume it. To give it lasting instructions, Claude Code reads files called CLAUDE.md at the start of every conversation:
- Your personal file applies to every project. It's where your “About me” and “How to explain things to me” notes live, which is why Claude already knows to use plain language with you.
- A project file sits inside one project folder and holds notes about that project only.
| Type | What it does |
|---|---|
/memory | Opens your CLAUDE.md files so you can read or edit them, and lets you turn Claude's automatic memory on or off. |
/init | Has Claude look at the current project and write a CLAUDE.md for it. If one already exists, it suggests improvements instead. |
You can tell Claude: “Remember that I prefer short answers.” It will save the note in the right place for you.
- Type
/memoryand press Enter. - Look at the list: it shows which memory files Claude reads, including your personal one.
- Press Esc to close without changing anything. (If you open a file, it appears in a text editor. Close it without saving.)
Help, checkups and updates
| Type | Where | What it does |
|---|---|---|
| ? | inside Claude, empty box | Shows the keyboard shortcuts. Press again to hide. |
/help | inside Claude | Shows help and the available commands. |
/doctor | inside Claude | A checkup. Looks for problems with your installation and settings, and offers to fix them. |
/exit | inside Claude | Quits Claude Code. (Ctrl+C or Ctrl+D twice on an empty box does the same.) |
claude --version | PowerShell | Shows which version you have. |
claude update | PowerShell | Updates Claude Code to the latest version. |
- With an empty typing box, press ?. Read a few shortcuts, then press ? again to hide them.
- Type
/helpand press Enter. Look around, then press Esc.
Cheat sheet and common questions
Starting Claude (PowerShell)
claude- new conversation
claude -c- continue the latest one
claude -r- pick from the list
claude -r name- open a named one
claude update- update Claude Code
Conversations
/resume- switch conversation
/rename- name this conversation
/clear- start fresh
/compact- shrink, keep going
/context- how full it is
Control and undo
- Shift+Tab
- change permission mode
- Esc
- stop Claude / close a menu
- Esc Esc
- rewind (empty box)
/rewind- go back to an earlier point
/permissions- allowed and blocked actions
Settings and help
/config- settings screen
/model- choose the model
/memory- your instruction files
/status/usage- version, account, usage
?/help/doctor- shortcuts, help, checkup
I typed claude --continue and got the wrong conversation.
Conversations are stored per folder, so your terminal was probably in a different folder. Check the folder name before the >. Or use claude --resume and press Ctrl+A to see conversations from all projects.
It says “No conversation found to continue”.
There's no earlier conversation in this folder. You're probably in a different folder from usual. Use claude --resume and Ctrl+A to look across all projects.
Does /clear delete my work?
No. It only starts a new conversation. Your files are untouched, and the old conversation stays in the /resume list (for 30 days by default).
I typed a slash command and nothing happened, or Claude just replied to it.
Check the spelling, and make sure the / is the very first character. Typing only / shows the list of real commands.
The mode under the typing box changed and I don't know why.
Shift+Tab was pressed. Press it again until you see the mode you want (Lesson 07).
I read about a /vim command or a # shortcut online.
Older guides mention these. /vim has been replaced by a setting inside /config, and the current official docs don't list a # shortcut. To add a memory, just tell Claude in plain words.