cmd

For better or worse, I'm going to spend the rest of my working life in terminals. That's where most of my work happens, and it won't change anytime soon. What's increasingly silly is how ineffective my workflow around them has become.

I'm an engineer and designer with 15 years of experience, and yet I found myself shortcut-switching between tabs like a lunatic, trying to remember which session was doing what. Occasionally, I'd stumble across one that had been waiting for my feedback for 30 minutes. I'm objectively a power user, but I didn't feel like one anymore.

Looking at newer terminal emulators and agent tools didn't help much either. Agent orchestrators often impose their own workflows, with crazy levels of engineering and UI complexity.

I started building cmd, a software workbench that embraces very normal workflows (you know... where people do things) and brings my tools together in one place.

A workspace per project holds everything I'm working on: terminals, browsers, text editors, and more. There are a few view modes, but the Strip, inspired by PaperWM, is by far my favorite. Windows sit side by side in a row you scroll through, making it easy to keep multiple terminals, agents, and a browser in view.

Enable AI in the settings and cmd starts understanding what's happening across your workspaces. It recognizes terminals running agents, helps you keep track of what they're doing, surfaces sessions that need your attention, and suggests smart actions.

Most of what I open stays inside cmd, too. Open a file from your shell and it appears in the current workspace, whether it's a folder, text or code, Markdown, JSON, a PDF, an image, a SQLite database, a Strudel pattern, or a URL in the browser.

With Magic Widgets, you can prompt new widgets into existence on the spot: open merge requests, queue depth, recent CI runs, or whatever else you need. The built-in agent builds them on top of tools already on your machine, from gh and kubectl to your own scripts.

cmd deliberately stays unopinionated. It bets on terminals and the tools you already know, and on the idea that they'll still matter when the next model arrives.

I'm building cmd mostly for myself, in the open. But I'm hoping it fits your workflow, too.