Migrating from iTerm2 to Warp

If you use a Mac and develop software, there’s a good chance iTerm2 has been your faithful terminal for years. It was the go-to terminal for over a decade: stable, customizable, reliable. But the world of terminals has evolved, and Warp arrived proposing something different: a terminal designed for the way we work today.

This post isn’t meant to convince anyone to abandon iTerm2. It’s an honest account of the differences, advantages, and things to watch out for if you’re considering (or have already decided) to make the switch.

What is Warp, anyway?

Warp is a modern terminal written in Rust, with direct GPU rendering. Unlike traditional terminals that inherited the experience of the ’80s, it was built from scratch with the idea that the terminal can (and should) offer the same experience as a modern code editor.

It sounds like an exaggeration, but after using it, it makes sense.

The differences you’ll feel day to day

Command blocks

This is probably the most visible change. In iTerm2, the output of all commands blends into a continuous stream of text. In Warp, each command becomes an independent block: with a beginning, an end, and the ability to copy the entire output with one click.

It seems like a detail, but in practice it completely changes how you interact with the terminal. Ran a huge git log and want to copy just the output? Click the block. Want to share it with a colleague? Warp generates a permanent link to that specific block.

Text editing like a code editor

In iTerm2, the command line is… a command line. No mouse-positionable cursor, no Cmd + Z to undo, no selecting text with Shift + arrow.

In Warp, the input field works like a mini editor:

These are shortcuts you already use in any text editor, but that simply didn’t exist in the traditional terminal.

Smart autocomplete

iTerm2 delegates autocomplete to the shell. It works, but depends on you configuring plugins like zsh-autosuggestions.

Warp brings over 400 native completions for CLI tools like git, docker, npm, kubectl, aws, and many more. Without installing anything. It shows a visual interface with descriptions of each option, parameters, and flags.

Search and history

In iTerm2, searching for an old command involves Ctrl + R or relying on the shell. In Warp, search is integrated, with fuzzy search via Ctrl + R and the ability to filter by directory, date, or text.

Performance: Rust makes a difference

Warp was written in Rust with Metal (GPU) rendering. In benchmarks using VTEbench, the numbers are impressive:

In practice, this means that when you cat a huge file, or run a build that spits out thousands of lines per second, Warp doesn’t choke. iTerm2, even with GPU rendering enabled, falls behind in these scenarios.

A word of caution: Warp tends to consume more memory (600MB to 2GB in typical use). If you work on a machine with limited RAM, it’s worth considering.

Integrated AI: the most notable differentiator

In Warp

Warp comes with built-in AI, powered by models from OpenAI and Anthropic. Press Ctrl + Space and write in natural language:

• “how to find all .log files larger than 100MB?”
• “what does this permission error mean?”
• “how do I do an interactive rebase in git?”

The AI generates a ready-to-run command, explains errors, suggests fixes, and even has an Agent Mode that executes multi-step tasks automatically. You get 40 free requests per month and more on the Pro plan.

In iTerm2

iTerm2 added basic AI support in beta, but requires you to provide your own OpenAI API key. The functionality is limited to generating commands from natural language text: it doesn’t answer conceptual questions, doesn’t explain errors, and doesn’t debug terminal output.

For those just starting to program, Warp’s AI works practically as an integrated tutor in the terminal.

Collaboration

This is a territory where iTerm2 simply doesn’t compete.

Warp offers Warp Drive, which lets you:

• Share command blocks with permanent links
• Create and share workflows with your team
• Sync settings across machines

If you work on a team and need to share commands, scripts, or debug sessions, Warp turns the terminal into a collaborative tool. In iTerm2, the alternative is copying and pasting text into Slack.

Customization: different philosophies

This is where the two terminals diverge in philosophy.

iTerm2 is a Swiss army knife of configuration. Hundreds of options: status bar with 13 components, Toolbelt sidebar, Instant Replay (a kind of “time travel” through terminal frames), 325+ community themes, advanced font control, and a full Python API for automation.

Warp follows the philosophy of working well with minimal configuration. It has a built-in theme editor with automatic palette generation, font and custom background support, and a Spotlight-style command palette to access everything quickly. Settings are in YAML.

If you enjoy spending hours tweaking every pixel, iTerm2 is still unbeatable. If you prefer something that works well right out of the box, Warp has the edge.

Things to consider before migrating

Not everything is perfect. Before making the switch, consider:

Mandatory account

Warp requires creating an account to use. iTerm2 doesn’t ask for anything: just install and use. If privacy is a top priority for you, know that Warp claims to have zero data retention and that cloud features (AI, Drive, sharing) are opt-in. But the account is mandatory.

Proprietary code

iTerm2 is open source (GPL v2) with over 15 years of community development. Warp is proprietary, backed by $73M in funding. For many this makes no difference, but if open source is a principle for you, it’s something to consider.

tmux

If you rely heavily on tmux, pay attention: Warp has limited tmux support. Warp’s block system conflicts with how tmux renders the screen. iTerm2, on the other hand, has native tmux integration that works very well.

If tmux is essential to your workflow, this might be the reason not to migrate, or to reconsider whether Warp’s own panes and windows can replace what you used tmux for.

Secrets redaction

A unique positive point for Warp: it does automatic secrets redaction in terminal output. If a command accidentally prints an API key or token, Warp detects and masks it. iTerm2 doesn’t have this feature.

The migration in practice

The good news is that migrating is simple. Warp respects your existing shell configurations.

Step 1: install Warp

brew install --cask warp

Or download directly from the official website.

Step 2: open and authenticate

On first launch, create your account (you can use GitHub or Google). It’s free.

Step 3: your configs are already there

Warp automatically recognizes your ~/.zshrc, ~/.bashrc, or whatever shell configuration you already have. Your aliases, environment variables, Oh My Zsh plugins, Powerlevel10k theme: everything works.

# Your aliases keep working
alias ll='ls -la'
alias gs='git status'
alias gp='git push'

# Your Oh My Zsh and plugins too
plugins=(git zsh-autosuggestions zsh-syntax-highlighting z)

Step 4: adjust preferences

A few things worth configuring right away:

1. Theme: go to Settings > Appearance and choose a theme (or create your own)
2. Font: if you use a Nerd Font (like MesloLGS NF), configure it in Settings > Appearance > Font
3. Input position: Warp lets you place the input field at the top or bottom of the screen. Try both options in Settings > Features
4. Keybindings: if you have custom shortcuts in iTerm2, configure the equivalents in Settings > Keybindings

Step 5: live with both (optional)

Nobody said you have to uninstall iTerm2. A healthy approach is to use both for a few weeks. Warp as your main terminal and iTerm2 as a fallback for specific situations (like heavy tmux sessions). When you realize you haven’t opened iTerm2 in a while, the migration happened naturally.

Who Warp makes the most sense for

• Those just starting to program: the integrated AI, visual blocks, and friendly interface lower the terminal’s barrier to entry
• Those who work on a team: Warp Drive and block sharing are a real differentiator
• Those who want quick productivity: native autocomplete for 400+ tools, without configuring anything
• Those who work across multiple platforms: Warp runs on Mac, Linux, and Windows

Who iTerm2 still makes sense for

• Those who use tmux intensively: iTerm2’s native integration is superior
• Those who prioritize open source: GPL v2 vs proprietary
• Those who enjoy extreme customization: hundreds of options that Warp doesn’t offer
• Those who don’t want to create an account: iTerm2 doesn’t ask for anything

Final comparison

Conclusion

iTerm2 is not a bad terminal. Far from it: it served incredibly well for over a decade. But Warp represents a new generation of terminals that understands developers deserve the same experience we already have in code editors and IDEs.

The migration is painless: your shell configurations work without changes, and in a few minutes you’re already productive. The learning curve is practically zero because Warp doesn’t try to reinvent the terminal: it improves what already exists.

If you’re curious, install it and test it for a week. The worst that can happen is you go back to iTerm2 knowing exactly what each terminal offers.

Made the switch or thinking about it? Send me a shout on twitter @lauralesteves