Adam Stachowiak

Use the code changelog for a free month of Framer Pro.

Rules and restrictions may apply.

Well, we've heard the term dev tools, and now we have agent tools.

That's right.

Right?

That's how I think about things.

And I've done a couple toy CLIs just to play with them.

One for Proxmox.

I'm a home labber.

I don't know what kind of nerd you are, but I love to home lab.

And one of the epicenters of my home lab...

is some version of a Raspberry Pi somewhere or an Intel NUC or maybe a slightly bigger one, which is a NAS, which is usually TrueNAS.

And the next best big thing in the network, for me at least, is a Proxmox machine, which is dedicated, where I can do different things, whether it's a service or tinker with something or play with a new version of Linux or just distro hop or distro play, however you want to describe it.

But as I've explored this world a bit and I've understood what it's like, is I'd never really built many CLIs before.

And I was like, well, the next thing you want to do there is really just, you want to enable, now that we have agent decoding, it's almost ubiquitous.

So when you build a tool or you build a new CLR, you think about a new way to create an API with a CLI that lets you talk to a service.

It's it's you can assume or presume pretty, pretty good with pretty decent accuracy that the person may be using an agent, likely using an agent or at least has one nearby and is, you know, working towards being OK with that.

Some people are still not OK with that.

So I was like, you know, it only makes sense now that when you design these tools, you can't just design the old way, which was, well, I'm designing this, obviously, to solve a human problem.

So it's going to be a human using it.