Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Git was created as low-level commands for the Linux kernel team. A unified user interface was written by a volunteer and later absorbed into the core project, but it was never intentionally designed for broad usability, explaining many of its ergonomic issues today.

Related Insights

The enthusiastic reception for Google's Workspace CLI reveals a counter-intuitive trend: old-school Command-Line Interfaces are becoming the preferred way for AI agents to interact with software. Unlike humans, agents don't need GUIs and benefit from the CLI's deterministic, low-friction nature, avoiding the 'abstraction tax' of newer API layers.

The creative process with AI involves exploring many options, most of which are imperfect. This makes the collaboration a version control problem. Users need tools to easily branch, suggest, review, and merge ideas, much like developers use Git, to manage the AI's prolific but often flawed output.

Tools like Git were designed for human-paced development. AI agents, which can make thousands of changes in parallel, require a new infrastructure layer—real-time repositories, coordination mechanisms, and shared memory—that traditional systems cannot support.

v0 integrates core Git concepts like branching and pull requests into a chat-based UI. This allows non-engineers (e.g., marketers) to propose and collaborate on production-level changes using a familiar, safe engineering workflow without needing to use the command line.

While GUIs were built for humans, the terminal is more "empathetic to the machine." Coding agents are more effective using CLIs because it provides a direct, scriptable, and universal way to interact with a system's tools, leveraging vast amounts of pre-trained shell command data.

The terminal-first interface of Claude Code wasn't a deliberate design choice. It emerged organically from prototyping an API client in the terminal, which unexpectedly revealed the power of giving an AI model direct access to the same tools (like bash) that a developer uses.

AI agents are the fastest-growing users of command-line tools. They have unique behaviors, like running "status" after every command, and struggle with interactive flows. Tools must be designed with this new, non-human persona in mind, not just for human developers.

Instead of struggling with the command line, non-technical individuals learning to code should use the GitHub Desktop application. Its visual interface makes Git primitives like commits, diffs, and branches much easier to understand and internalize, accelerating the learning process.

Contrary to the stereotype of advanced developers preferring the command line (CLI), the emerging "vibe coding" community is shifting towards Graphical User Interfaces (GUIs). Proponents argue tools like Conductor make orchestrating AI agents more effective and that the CLI is now the "Stone Age" for this new workflow.

To encourage designers intimidated by Git and terminals to use a code playground, Notion created custom slash commands like `/create` and `/deploy`. These commands abstract complex processes, provide instructions if prerequisites are missing, and guide users through workflows like branching and deploying, lowering the barrier to entry.

Git's Command-Line Interface Was An Accidental Addition, Not A Deliberate Design | RiffOn