Skip to main content
Devin CLI works across a wide range of terminal emulators, but some terminals offer a better experience than others. This page covers compatibility levels, recommendations, and configuration tips.

​
Compatibility Overview

Terminals are grouped into three tiers based on their feature support:

​
Fully Supported (all features work)

These terminals support the Kitty keyboard protocol, which enables reliable detection of key combinations like Shift+Enter for multi-line input.

​
Supported (some features limited)

These terminals work with Devin CLI but are not ideal because they do not support the Kitty keyboard protocol. For example, Shift+Enter will not insert a newline — use Alt+Enter or Ctrl+J instead. † On macOS, we recommend configuring Option as Meta for the best experience with Alt-based shortcuts.
On macOS terminals that have not been configured for Option-as-Meta, Alt (Option) shortcuts like Alt+Enter for multi-line input won’t work. See Configuring Option-as-Meta on macOS below.

​
Unsupported

These terminals are not supported and may exhibit significant issues. We highly recommend switching to a supported terminal.

​
Recommendations

​
Configuring Option-as-Meta on macOS

On macOS, the Option key is used as a compose key by default in most terminals, which means Alt-based shortcuts (like Alt+Enter for multi-line input or Alt+T for cycling thinking level) won’t work until you configure the terminal to treat Option as Meta/Alt.
  1. Open iTerm2 > Settings (or press Cmd+,)
  2. Go to Profiles > Keys > General
  3. Set Left Option Key to Esc+
  4. Optionally set Right Option Key to Esc+ as well
iTerm2 documentation
  1. Open Terminal > Settings (or press Cmd+,)
  2. Go to Profiles and select your active profile
  3. Click the Keyboard tab
  4. Check Use Option as Meta Key
Apple documentation
Add the following to your alacritty.toml configuration file:
Alacritty configuration reference
Add the following to your kitty.conf configuration file:
Restart Kitty after making this change.Kitty documentation
Add the following to your Ghostty configuration file:
Restart Ghostty after making this change.Ghostty documentation
Add the following to your ~/.wezterm.lua configuration file:
WezTerm documentation