Warp Terminal × Next Gen Terminals

Episode Summary

Executive Summary: Scott and Wes review Warp, a modern terminal for web developers, praising its mouse-friendly navigation, block-based command output, AI-assisted search, remote SSH support, and polished UI while noting drawbacks like weaker autocomplete, limited theming, and imperfect process handling. They situate Warp among iTerm, Hyper, Windows Terminal, Alacritty, and VS Code’s terminal, arguing it modernizes a tool stack that has barely changed for years.

Main Topics: Why Warp feels like a modern terminal: The hosts argue that Warp improves common terminal frustrations by allowing clicking, better cursor movement, multiple cursors, and a more GUI-like experience for beginners and power users. Blocks, sticky headers, and command history: Warp groups command input and output into searchable blocks, keeps the prompt visible, and makes it easier to inspect, share, and revisit past commands. Autocomplete and AI command search: Warp’s autocomplete and AI command search are discussed as major conveniences, but both hosts agree autocomplete still lags behind specialized tools like Fig and lacks strong support for some package managers. Terminal ecosystem and terminology: The episode explains shells, prompts, and terminals, covering ZSH, Bash, Fish, PowerShell, WSL, and prompt tools like Oh My Zsh, Oh My Fish, Starship, and Oh My Posh. Remote SSH, workflows, and team features: Warp’s SSH experience, launch configs, workflows, command palette, and session-sharing features are positioned as especially useful for teams and repeated operational tasks. Limitations and wishlist: They note weaknesses such as incomplete autocomplete support, limited window/pane management, paid account requirements, telemetry concerns, and background process bugs. Sponsorship, monetization, and trust: The hosts discuss Warp’s business model, likely team-oriented monetization, and the tradeoff between convenience and requiring accounts/telemetry.

Key Arguments: Warp is appealing because it modernizes the terminal with GUI-like interactions that reduce friction for everyday development tasks. The block model is one of Warp’s strongest features because it makes command output easier to inspect, search, share, and resume. Autocomplete is useful but not yet best-in-class; Fig remains stronger for information density and ecosystem coverage. Warp is especially valuable for people learning the terminal because it lowers the barrier to entry with clearer UI and guidance. Remote SSH and command palette features make Warp feel like a broader workflow tool rather than just a shell window. Teams and organizations are likely the main monetization path, since collaboration, configs, auditing, and shared workflows become more valuable at scale. Requiring an account is acceptable to the hosts as long as the product is useful and trust is maintained, though telemetry is a recurring concern. Some of Warp’s shortcomings stem from its ambition to layer custom behavior over terminal conventions, which can break compatibility with existing shell tools.

Data Points: Duration of use: about a year - Wes says he has been using Warp for about a year and loving it. Hyper usage span: 2 years - Wes mentions a two-year stint with Hyper before moving on. iTerm usage span: 6 or 7 years - Wes says he used iTerm2 for roughly six or seven years. Warp availability: Mac only - At the time of recording, Warp is available on Mac, with signups open for Windows and Linux. Command history depth: 6–7 days - Warp’s command search can surface roughly six or seven days of prior commands. Tab count preference: 4 or 5 - Wes says he prefers to keep terminal tabs to about four or five before cleaning up. Pokemon card pack price: $5 - Wes’s sick pick is a pack of 50 Pokémon cards for five dollars. Pokemon card count: 50 cards - Wes cites 50 cards per pack as a reward mechanism for kids. AirPort charger ports: 8 ports - Wes uses an Anker eight-port USB charger in his iPad charging setup.

Pivotal Quotes: "will somebody please VS Codify the terminal?" — Wes: Wes summarizes his desire for a more modern, editor-like terminal experience. "the niceties of Warp outweigh the autocomplete of Fig. Ideally, I would have both." — Wes: He explains why he currently prefers Warp despite Fig having stronger autocomplete. "I want the info" — Scott: Scott says he prefers information-dense interfaces, using Warp/Fig size differences as an example.

Implications: Warp signals where terminals are heading: more visual, searchable, collaborative, and assistant-driven. For users, it reduces friction; for teams, it suggests a future where terminal tooling includes sharing, automation, and AI help.