Understanding the Interface

Identify the key parts of the Claude Code terminal interface

Use essential keyboard shortcuts for common actions

Navigate command history and use autocomplete

Recognize when Claude is thinking versus waiting for input

Customize basic interface settings like theme and color

Claude Code runs in your terminal, but it is more than a simple command line. The interface has several parts that work together to help you communicate with Claude. Understanding these parts makes you faster and more effective.

In this lesson, we will tour the Claude Code interface. You will learn where to type, what the different visual elements mean, and how to use keyboard shortcuts to work efficiently. We will also cover how to tell when Claude is working versus waiting for you.

By the end of this lesson, you will feel comfortable navigating Claude Code. You will know the shortcuts that save time and understand what different colors and indicators mean.

At the bottom of your screen, you will see the prompt bar. This is where you type your messages to Claude. It looks something like this:

The > symbol indicates that Claude Code is ready for your input. Type your message here and press Enter to send it.

The prompt bar can change colors. By default, it uses your terminal's standard colors. But you can customize it:

This changes the prompt bar to blue for the current session. Available colors include red, blue, green, yellow, purple, orange, pink, and cyan. Use /color default to reset it.

Why would you change the color? Some developers use different colors to distinguish between projects. A blue prompt might mean your main project, while a green prompt means you are working on a side project. It is a simple visual cue.

Above the prompt bar, you see the conversation history. Your messages and Claude's responses scroll upward as the conversation grows. Claude's responses often include code blocks, file diffs, and other formatted output that makes information easy to read.

Learning a few keyboard shortcuts makes a big difference in how quickly you can work. Here are the most important ones.

Enter sends your message. After typing, press Enter to submit.

Escape stops Claude mid-response. If Claude is generating a long response and you realize you asked the wrong question, press Escape to stop it immediately. You do not lose your conversation. You can redirect Claude with a new message.

Escape twice (or Escape + Escape) opens the rewind menu. This lets you go back to earlier points in the conversation. We will cover this in detail in a later lesson.

Tab completes commands. When you start typing a slash command like /com, pressing Tab autocompletes it to /compact. This works for file paths too.

Up arrow recalls your previous message. Keep pressing Up to go further back in your history.

Down arrow moves forward through your message history after pressing Up.

Ctrl+C cancels the current input. If you are typing something and change your mind, Ctrl+C clears it.

Ctrl+D exits Claude Code. This is the same as typing exit.

Shift+Tab cycles through permission modes. This toggles between normal mode, auto-accept mode, and plan mode. We will cover these modes in a later lesson.

To see all available shortcuts, press ? (question mark) while in Claude Code. This brings up a quick reference.

Claude Code has many built-in commands, and typing / reveals them all. Try this:

A list appears showing available commands. Start typing to filter:

Now you see commands that start with "com" like /compact and /copy. Use arrow keys to navigate the list and Enter to select.

This autocomplete system works for:

Slash commands (/help, /clear, /model)

File paths (type @ followed by a path)

Settings and options

Get comfortable with Tab completion. It speeds up your work and helps you discover commands you might not know exist.

Claude's responses contain different types of content. Learning to read them makes you more effective.

Plain text is just Claude explaining something. This appears in your terminal's normal text style.

Code blocks appear with syntax highlighting. These might be example code, commands to run, or code that Claude is suggesting. Code blocks are often surrounded by a border or different background color depending on your terminal.

File diffs show proposed changes. When Claude wants to edit a file, it shows you what will change. Added lines appear in green (or with a + prefix). Removed lines appear in red (or with a - prefix). You will see the file name and line numbers.

Tool calls show what Claude is doing. When Claude reads a file, runs a command, or performs another action, you see an indicator. Something like [Reading src/index.ts...] or [Running npm test...]. These help you understand what Claude is working on.

Status indicators appear at the bottom of the screen. The status line shows useful information like the current model, your working directory, and context usage. We will cover customizing this in a later lesson.

When Claude is thinking, you see a loading indicator. The exact appearance depends on your terminal, but it usually involves animated dots or a spinner. When this animation stops and you see the > prompt, Claude is done and waiting for you.

Claude sometimes reasons through problems before responding. This reasoning is called "extended thinking." By default, you see a summary of this thinking or just the final response.

To see more detail about what Claude is doing, press Ctrl+O to toggle verbose mode. In verbose mode, you see:

Claude's thinking process (shown as gray italic text)

More detail about tool calls

Additional diagnostic information

Verbose mode is helpful when you want to understand why Claude made a particular decision or when something unexpected happens. For everyday use, normal mode keeps the output clean.

Press Ctrl+O again to toggle back to normal mode.

Claude Code lets you customize several interface elements.

Themes change the overall color scheme. Run:

This opens a picker where you can choose light themes, dark themes, colorblind-accessible themes, or ANSI themes that match your terminal's color palette.

Status line shows information at the bottom of the screen. You can customize what appears there. Run:

This command auto-configures the status line based on your shell, or you can describe what you want to see.

Keybindings can be customized if the defaults do not work for you. Run:

This opens your keybindings configuration file where you can change shortcuts.

For most beginners, the defaults work well. As you use Claude Code more, you might want to tweak these settings to match your preferences.

The prompt bar at the bottom is where you type messages to Claude

Press Escape to stop Claude mid-response without losing your conversation

Tab autocompletes commands and file paths

Type / to see all available commands

Claude shows diffs, code blocks, and tool calls with distinct formatting

Press ? to see all keyboard shortcuts

Ctrl+O toggles verbose mode for more detail about Claude's thinking

Practice using the interface with these steps:

Start Claude Code in a project directory with claude.

Press ? to see the keyboard shortcuts. Read through them.

Type / and explore the command list. Try Tab to autocomplete a few commands.

Ask Claude a question. While Claude is responding, press Escape to stop it.

Ask another question and let it complete.

Press the Up arrow to recall your previous message.

Try /theme and pick a different color scheme.

Type exit to end the session.

This exercise builds muscle memory for the most common interface interactions. The more you practice these shortcuts, the faster you will become.

https://code.claude.com/docs/en/interactive-mode - Keyboard shortcuts, Vim mode, command history

https://code.claude.com/docs/en/keybindings - Customizing keyboard shortcuts and keybindings

https://code.claude.com/docs/en/commands - Complete list of built-in slash commands