// 26 tips tagged "shortcuts"
When typing feels slow — describing a complex bug, explaining architecture, or thinking through a problem out loud — press Option+V to switch to voice input. Speak naturally and Claude Code transcribes your words into a prompt, so you can describe what you need at the speed of thought.
Not every task needs deep reasoning. Type /fast to switch Claude Code into fast mode — same model, faster output — for quick edits, simple questions, and routine changes. Toggle it off when you need Claude to think harder on complex problems.
When Claude is heading down the wrong path — editing the wrong file, writing code you don't want, or giving a long explanation you don't need — press Escape to stop it immediately. You keep everything it did up to that point and can redirect with a new prompt.
Closed a session and realized you weren't done? Pass --continue (or -c) when launching Claude Code to pick up exactly where you left off — same context, same files, same conversation history — without re-explaining what you were working on.
The -p (print) flag runs Claude Code as a one-shot command — ask a question, get an answer, and return to your shell. Perfect for quick lookups, scripting, piping output, and integrating Claude into shell workflows without starting a full interactive session.
Claude Code's input supports multiline prompts — press Enter to start a new line without sending. Structure complex prompts with line breaks for readability, paste multi-paragraph instructions, or write detailed specs that Claude can follow step by step.
When typing file paths or slash commands in Claude Code, press Tab to autocomplete — it suggests matching files from your project and available commands, saving you from typing full paths or remembering exact command names.
Press the up arrow key to cycle through your previous prompts — find the one you want, edit it, and send it again. Perfect for tweaking a prompt that almost worked, retrying with different constraints, or repeating a command you use often.
When you hit a bug in Claude Code itself — a tool that fails, a wrong edit, or unexpected behavior — type /bug to file a report without leaving your session. It captures the context automatically so the team can reproduce and fix it.
Not sure what Claude Code can do? Type /help to see the full list of slash commands, keyboard shortcuts, CLI flags, and built-in features — it's the fastest way to discover capabilities you didn't know existed without leaving your session.
While --continue picks up the last session automatically, --resume shows you a list of all recent conversations so you can choose which one to reopen — jump back into that debugging session from Tuesday or the refactor you paused last week.
Prefix any shell command with ! in a Claude Code session to run it directly — the output appears in the conversation, giving Claude immediate context without you switching to another terminal or asking Claude to run it for you.