Skip to content
Back to writing

Why CLI-First Still Matters

When AI tooling gets too polished too early, it often hides the exact parts that need to stay visible.

March 18, 20262 min read

Most AI tools want to become invisible as fast as possible.

That is a reasonable instinct. Good interfaces reduce friction. But there is a real tradeoff: when a workflow becomes too smooth too early, it often hides the exact system boundaries you still need to understand.

That is why I keep coming back to terminal-first workflows.

The CLI is not better because it looks technical. It is better when the work itself benefits from clarity, composability, and explicitness. You can see what is being called, what depends on what, what failed, what state is being carried, and what can be automated cleanly.

That matters even more with agents.

A recent paper, Terminal Agents Suffice for Enterprise Automation, makes the same case from another angle: simple terminal-based coding agents using direct programmatic interfaces can match or outperform more elaborate GUI and tool-augmented setups on real enterprise tasks. That feels directionally right to me. The terminal is often not the fallback interface. It is the cleanest one.

Once a system starts using tools, files, prompts, context windows, retries, and background processes, a glossy surface can create a false sense of legibility. Everything appears simpler than it is. Then the workflow breaks and you realize you do not have enough visibility into what actually happened.

A CLI-first setup forces a healthier relationship with the stack:

  • the inputs are clearer
  • the outputs are inspectable
  • automation becomes easier to compose
  • failure is easier to reason about

It also changes the way I think.

The terminal keeps me closer to verbs than views. I am not asking what screen I should click next. I am asking what should run, what should be saved, what should be passed forward, and what should happen when this step fails.

That does not mean everything should stay in a terminal forever. Some workflows deserve a better interface. Some should become calmer and more visual over time.

But when I am still learning the shape of a system, the CLI keeps me honest.

That is usually the environment where the useful ideas show up first.