Interactive mode ↗

Documentation Index#

Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt Use this file to discover all available pages before exploring further.

Complete reference for keyboard shortcuts, input modes, and interactive features in Claude Code sessions.

Keyboard shortcuts#

Keyboard shortcuts may vary by platform and terminal. Press ? to see available shortcuts for your environment.

macOS users: Option/Alt key shortcuts (Alt+B, Alt+F, Alt+Y, Alt+M, Alt+P) require configuring Option as Meta in your terminal:

• iTerm2: settings → Profiles → Keys → set Left/Right Option key to “Esc+”
• Terminal.app: settings → Profiles → Keyboard → check “Use Option as Meta Key”
• VS Code: settings → Profiles → Keys → set Left/Right Option key to “Esc+”

See Terminal configuration for details.

General controls#

Text editing#

Theme and display#

Syntax highlighting is only available in the native build of Claude Code.

Multiline input#

Shift+Enter works without configuration in iTerm2, WezTerm, Ghostty, and Kitty. For other terminals (VS Code, Alacritty, Zed, Warp), run /terminal-setup to install the binding.

Quick commands#

Built-in commands#

Type / in Claude Code to see all available commands, or type / followed by any letters to filter. Not all commands are visible to every user. Some depend on your platform, plan, or environment. For example, /desktop only appears on macOS and Windows, /upgrade and /privacy-settings are only available on Pro and Max plans, and /terminal-setup is hidden when your terminal natively supports its keybindings.

Claude Code also ships with bundled skills like /simplify, /batch, and /debug that appear alongside built-in commands when you type /. To create your own commands, see skills.

In the table below, <arg> indicates a required argument and [arg] indicates an optional one.

MCP prompts#

MCP servers can expose prompts that appear as commands. These use the format /mcp__<server>__<prompt> and are dynamically discovered from connected servers. See MCP prompts for details.

Vim editor mode#

Enable vim-style editing with /vim command or configure permanently via /config.

Mode switching#

Navigation (NORMAL mode)#

In vim normal mode, if the cursor is at the beginning or end of input and cannot move further, the arrow keys navigate command history instead.

Editing (NORMAL mode)#

Text objects (NORMAL mode)#

Text objects work with operators like d, c, and y:

Command history#

Claude Code maintains command history for the current session:

• Input history is stored per working directory
• Input history resets when you run /clear to start a new session. The previous session’s conversation is preserved and can be resumed.
• Use Up/Down arrows to navigate (see keyboard shortcuts above)
• Note: history expansion (!) is disabled by default

Reverse search with Ctrl+R#

Press Ctrl+R to interactively search through your command history:

1. Start search: press Ctrl+R to activate reverse history search
2. Type query: enter text to search for in previous commands. The search term is highlighted in matching results
3. Navigate matches: press Ctrl+R again to cycle through older matches
4. Accept match:
   • Press Tab or Esc to accept the current match and continue editing
   • Press Enter to accept and execute the command immediately
5. Cancel search:
   • Press Ctrl+C to cancel and restore your original input
   • Press Backspace on empty search to cancel

The search displays matching commands with the search term highlighted, so you can find and reuse previous inputs.

Background bash commands#

Claude Code supports running bash commands in the background, allowing you to continue working while long-running processes execute.

How backgrounding works#

When Claude Code runs a command in the background, it runs the command asynchronously and immediately returns a background task ID. Claude Code can respond to new prompts while the command continues executing in the background.

To run commands in the background, you can either:

• Prompt Claude Code to run a command in the background
• Press Ctrl+B to move a regular Bash tool invocation to the background. (Tmux users must press Ctrl+B twice due to tmux’s prefix key.)

Key features:

• Output is buffered and Claude can retrieve it using the TaskOutput tool
• Background tasks have unique IDs for tracking and output retrieval
• Background tasks are automatically cleaned up when Claude Code exits

To disable all background task functionality, set the CLAUDE_CODE_DISABLE_BACKGROUND_TASKS environment variable to 1. See Environment variables for details.

Common backgrounded commands:

• Build tools (webpack, vite, make)
• Package managers (npm, yarn, pnpm)
• Test runners (jest, pytest)
• Development servers
• Long-running processes (docker, terraform)

Bash mode with ! prefix#

Run bash commands directly without going through Claude by prefixing your input with !:

! npm test
! git status
! ls -la

Bash mode:

• Adds the command and its output to the conversation context
• Shows real-time progress and output
• Supports the same Ctrl+B backgrounding for long-running commands
• Does not require Claude to interpret or approve the command
• Supports history-based autocomplete: type a partial command and press Tab to complete from previous ! commands in the current project

This is useful for quick shell operations while maintaining conversation context.

Prompt suggestions#

When you first open a session, a grayed-out example command appears in the prompt input to help you get started. Claude Code picks this from your project’s git history, so it reflects files you’ve been working on recently.

After Claude responds, suggestions continue to appear based on your conversation history, such as a follow-up step from a multi-part request or a natural continuation of your workflow.

• Press Tab to accept the suggestion, or press Enter to accept and submit
• Start typing to dismiss it

The suggestion runs as a background request that reuses the parent conversation’s prompt cache, so the additional cost is minimal. Claude Code skips suggestion generation when the cache is cold to avoid unnecessary cost.

Suggestions are automatically skipped after the first turn of a conversation, in non-interactive mode, and in plan mode.

To disable prompt suggestions entirely, set the environment variable or toggle the setting in /config:

export CLAUDE_CODE_ENABLE_PROMPT_SUGGESTION=false

Task list#

When working on complex, multi-step work, Claude creates a task list to track progress. Tasks appear in the status area of your terminal with indicators showing what’s pending, in progress, or complete.

• Press Ctrl+T to toggle the task list view. The display shows up to 10 tasks at a time
• To see all tasks or clear them, ask Claude directly: “show me all tasks” or “clear all tasks”
• Tasks persist across context compactions, helping Claude stay organized on larger projects
• To share a task list across sessions, set CLAUDE_CODE_TASK_LIST_ID to use a named directory in ~/.claude/tasks/: CLAUDE_CODE_TASK_LIST_ID=my-project claude
• To revert to the previous TODO list, set CLAUDE_CODE_ENABLE_TASKS=false.

PR review status#

When working on a branch with an open pull request, Claude Code displays a clickable PR link in the footer (for example, “PR #446”). The link has a colored underline indicating the review state:

• Green: approved
• Yellow: pending review
• Red: changes requested
• Gray: draft
• Purple: merged

Cmd+click (Mac) or Ctrl+click (Windows/Linux) the link to open the pull request in your browser. The status updates automatically every 60 seconds.

PR status requires the gh CLI to be installed and authenticated (gh auth login).

See also#

• Skills - Custom prompts and workflows
• Checkpointing - Rewind Claude’s edits and restore previous states
• CLI reference - Command-line flags and options
• Settings - Configuration options
• Memory management - Managing CLAUDE.md files