The Greatest Claude Code Workflow Is Just a Terminal — Alex Finn Discovers That Less Software Means More Speed, and the Sysadmins Were Right All Along

🤚 The Open-Palm Illumination

In the grand tradition of tech influencers discovering something obvious and presenting it as revelation, Alex Finn went live on May 14 to announce — with the breathless urgency of a man who has just seen fire for the first time — that the single greatest Claude Code workflow involves not using an IDE at all.

The answer, dear reader, is Ghostty. A terminal emulator. A program whose entire value proposition is that it displays text on your screen and does absolutely nothing else. According to Finn’s latest livestream, abandoning the bloated comfort of VS Code, Cursor, and every other electron-wrapped IDE in favor of a bare terminal running Claude Code CLI is “the fastest and most efficient workflow” available today. We are told this will 10x your speed, because in the AI productivity content ecosystem, all improvements must be expressed as multiples of ten.

The core thesis is this: open Ghostty, spawn 3 to 5 git worktrees, run a separate Claude Code session in each tab, and let your silicon colleagues build your application in parallel while you — presumably — sit back and contemplate the structural unemployment you’re creating for yourself.

👐 The Two-Handed Reality Check

Let’s talk numbers, because the numbers are actually interesting. Two VS Code windows with Claude Code extensions running simultaneously consume approximately 8 GB of RAM, along with the kind of input lag that makes you wonder if your laptop is processing keystrokes or filing them with a municipal clerk. The same two projects running in Ghostty terminal tabs use under 500 MB total, with instant response times. That’s not a marginal improvement — that’s a 16x reduction in memory consumption, which is the kind of number you’d reject as implausible if it appeared on a startup’s pitch deck.

The practical implication: developers can now run dozens of Claude Code instances simultaneously without their laptop fans achieving the acoustic profile of a regional airport. This matters more than it sounds. The emerging “vibe coding” workflow — a phrase we desperately wish someone had focus-grouped before releasing into the wild — depends on running multiple AI agents in parallel, each tackling a different feature branch or task. If your machine melts after two instances, you’re not vibe coding; you’re suffering.

There’s a second advantage Finn emphasized: feature parity arrives in the CLI first. The Claude Code terminal interface receives updates before the VS Code extension, the desktop app, or any other client. Extension users wait days or weeks for updates to propagate through their IDE’s marketplace. Terminal users get plan mode, subagents, and new capabilities the moment they land. In the AI tooling arms race, being a week behind is the equivalent of showing up to a sword fight with a polite letter of objection.

🌿 The Gentle Awakening

What’s quietly fascinating here is the regression. The entire history of software development has been a march toward richer, more visual, more graphical environments. We went from punch cards to terminals, terminals to GUIs, GUIs to IDEs with built-in debuggers and seventeen docked panels and a minimap that makes your code look like a chromosome under a microscope. And now the cutting edge is… opening a terminal and typing commands.

The Claude Code team itself has endorsed this approach. Multiple team members have expressed love for Ghostty’s synchronized rendering, 24-bit color, and proper Unicode support. They describe the workflow of spinning up 3-5 git worktrees, each running its own Claude session in parallel, as “the single biggest productivity unlock.” When the people who built the tool tell you to use it in a terminal, perhaps the graphical wrapper was always the compromise, not the destination.

This also explains the curious phenomenon of developers with $4,000 laptops and 64 GB of RAM complaining about performance. They don’t have a hardware problem. They have a thirty nested Electron processes problem. Ghostty, being a native application written in Zig, treats system resources with the respect of someone who actually has to pay the electricity bill.

👑 The Crown Verdict

Alex Finn has, in essence, rediscovered what grizzled systems administrators have known since 1987: terminals are fast because they don’t do anything unnecessary. The innovation is not the terminal. The innovation is that AI coding agents are so powerful that the IDE’s visual scaffolding — the syntax highlighting, the IntelliSense, the git blame gutter decorations — has become decorative. When an AI agent reads, understands, and modifies your entire codebase through a text interface, the graphical representation is no longer a tool. It’s a screensaver.

The workflow is simple, effective, and — most importantly — free. Ghostty is open source. Git worktrees have existed since 2015. Claude Code’s CLI is the primary interface. There is no premium plugin, no enterprise tier, no “unlock parallel sessions for $49/month.” This is perhaps the most subversive aspect of the whole thing: the optimal AI-powered development environment costs exactly zero additional dollars beyond your existing Claude subscription.

We at Slap of Wisdom have always maintained that luxury is not about acquisition. It is about elimination. And eliminating 7.5 GB of RAM overhead while gaining parallel AI agents is the most elegant subtraction we’ve seen since someone removed the headphone jack and called it courage.

Inspired by LIVE: The greatest Claude Code workflow ever by Alex Finn.

Your bloated IDE is showing. Compile wisely.