I fired software I’d used for over a decade last week.
Not because it broke. Not because a competitor was cheaper. Because it didn’t have a CLI.
A year ago that would have been a footnote on a feature request. Today it was a dealbreaker. My agentic workflow needed to talk to the tool, and the tool couldn’t talk back.
So I migrated. Full switch. A decade of muscle memory traded for one capability the old tool never prioritized.
This is Jobs To Be Done in its purest form. The job didn’t change. I still needed the same output. But the context around the job shifted so far that the tool I had hired ten years ago was suddenly unqualified.
And I’m not the only one doing this math. An open-source project called “CLI Anything” just launched. It generates a command-line interface for tools that don’t have one. The fact that it exists tells you everything. The demand isn’t for better GUIs. It’s for software that can participate in a workflow where humans aren’t the only operators.
Yes, APIs and webhooks exist. But for local agentic workflows, the ones running on your machine and orchestrating your tools, the CLI is the native interface. It’s what your agent already speaks.
- CLI used to be a developer preference.
- Now it’s the interface your agents require.
- Tools without it aren’t broken. They’re just unreachable.
CLI may not be the permanent answer. Right now it’s the interface agentic workflows actually reach for. And the real question isn’t about CLI at all.
Can my systems reach you without me in the middle?
If the answer is no, the migration pain stops being a barrier and starts being a cost you pay once.
