Skip to content

Keyboard

Shortcuts

Everyone learns Esc. These are the rest — all checked against Claude Code itself, not copied off a blog.

The three to learn first

If you remember nothing else.

  • Esc Esc
    Stop Claude mid-action The moment Claude starts doing something you did not intend.
  • Esc thenEsc Esc thenEsc
    Clear the input box Your half-written prompt has turned into a mess and you want a clean line.
  • Shift +Tab Shift +Tab
    Cycle permission mode Starting an exploration (plan) or letting an agreed plan run (accept edits). On older Windows setups without VT mode, this is Meta+M instead.

Writing the prompt

Composing, searching, pasting.

  • Ctrl +J Ctrl +J
    Start a new line without sending Any prompt longer than one sentence.
  • Ctrl +R Ctrl +R
    Search your prompt history "What did I type last week that worked?" Inside the search, Ctrl+S cycles the scope: this session → this project → everywhere.
  • Ctrl +S Ctrl +S
    Park the half-written prompt You are three sentences into a prompt and need to go check something.
  • Ctrl +G Ctrl +G
    Edit the prompt in your real editor Writing anything long or carefully structured.
  • Ctrl +V Alt +V
    Paste an image Anything visual. Annotate the screenshot first and it works even better. Ctrl+V, not Cmd+V — macOS keeps Cmd+V for its own paste. Windows and WSL use Alt+V. On WSL both Ctrl+V and Alt+V work.
  • Option +T Alt +T
    Toggle thinking for the next turn One hard question in the middle of otherwise simple work.
  • Ctrl +_ Ctrl +_
    Undo in the input box You deleted half a prompt by accident.

Seeing what happened

What Claude did and what it plans to do.

  • Ctrl +O Ctrl +O
    Toggle the full transcript You want to know what it actually did, not the summary.
  • Ctrl +T Ctrl +T
    Toggle the task checklist Any multi-step task, before it gets far.

Running the session

Long jobs, models, the terminal.

  • Ctrl +B Ctrl +B
    Send the running job to the background A long build, test run, or search you do not want to sit and watch.
  • Option +P Alt +P
    Switch model Between tasks — rarely a good idea mid-task.
  • Option +O Alt +O
    Toggle fast mode Straightforward work where you would rather have speed than depth.
  • Ctrl +Z Ctrl +Z
    Step out to the shell without quitting You need the terminal for one command and do not want to lose the session. Terminal-level shortcut (Unix SIGTSTP), not a Claude Code binding. Windows has no direct equivalent.

The keys are the same on both systems — only the modifier's name changes (macOS calls Alt Option). Run /keybindings in any session to see exactly what is bound on your machine.

Prompt in Greek (or any language) — Claude understands

← Tips Prompting

Prompt in Greek (or any language) — Claude understands

Claude is multilingual. in Greek when it's the language you can think in most clearly. The replies in the language you wrote — and code/identifiers stay in English, which is exactly what you want.

beginner

The site is in English, but you don’t have to think in English to use . The is multilingual. in Greek (or in any language you’re more comfortable with) works, and for most non-developers it gives you better results — the prompt comes out cleaner when you’re not also fighting a translation in your head.

Here’s a real example.

Greek prompt:

Δες το αρχείο Q3-portfolio.pdf στο φάκελο. Φτιάξε μια σύνοψη σε απλή γλώσσα για την επιτροπή κινδύνου της Τρίτης. Χωρίς τεχνικούς όρους, κάτω από 300 λέξεις. Ξεκίνα με τις τρεις μεγαλύτερες αλλαγές σε σχέση με το Q2.

What you’ll get back: a 300-word summary in Greek, leading with the three biggest changes vs Q2, in plain language. Claude reads the PDF, writes the answer, and respects every constraint you stated — same as it would in English.

A few practical notes for prompting in Greek:

  • Code stays in English. Function names, variable names, file paths — those don’t translate. Mention them in their original form (Q3-portfolio.pdf, customer_id, npm run dev) even when the surrounding prose is Greek. Claude will read them correctly.
  • Mixed-language prompts work. Write the framing in Greek, paste an English error message verbatim, ask the question in Greek. Claude handles the switch silently.
  • Bank-specific terminology in Greek is fine. “επιτροπή κινδύνου”, “πελάτης λιανικής”, “ταμείο” — Claude knows financial vocabulary in Greek as well as in English. If you’re explaining the business context to Claude in a prompt, do it in the language you actually use at work.
  • The output language follows the prompt language. Greek prompt → Greek reply. English prompt → English reply. If you want the reply in a specific language regardless of the prompt, say so: “απάντησε στα ελληνικά” or “reply in English”.

If you’ve been quietly translating your prompts before typing them — stop. You’re losing precision in the translation. The “what I wish I knew a year ago” line on this hub applies here too: write your prompt in the language you can think most clearly in.

The hub UI is in English for now — that’s a separate decision (see SCOPE.md). The bilingual UI question is open. The prompt-in-Greek answer is “yes, always, just do it”.

Next tip →

"Report and stop" — tell Claude where the work ends

Claude will happily turn a question into a . Add an explicit boundary — "report findings and stop" for questions, "go ahead and implement" for work — and you stop getting changes you didn't ask for.