Command-line interface

David, David Blough.

You know, we had Cli- Gif- Cliff Kingsbury, you know, he was labeled as this spread-heavy offensive coordinator, always has been, and David Blough's kind of bringing that hybrid Shanahan, you know, outside zone.

I don't even know what you'd call it.

A mixture of Ben Johnson, a mixture of Shanahan.

One thing that we spoke about in 2022, that CRI-O, I'm not sure how you pronounce that, that was actively replacing Docker as a runtime.

So understand that when you're using Docker, right, so you're interacting with Docker CLI, It's not the whole thing that is being presented to you.

The CLI is using the socket to communicate with the Docker server, which in most cases would run locally on your host, but you can also connect to the remote Docker machine through that CLI.

So you can choose what you communicate with.

And...

What happens is that you could still use Docker CLI with something providing a server, which is not necessarily a Docker native runtime.

And like the runtime is, for instance, CRIO that runs containers.

There is container D that runs containers.

You either utilize the harness provided by LLM provider.

So that would be Kira CLI, Codex, Cloud Code, whatever.

Or you bring your own PyDev.

You can open code, maybe Hermes or OpenClose.

There is RTK tool, I think Rust Token Killer it's called.

That one is quite helpful, especially if you use your harness to run everything as Matthias does, for instance.

That one kind of understands most of the CLI commands and what's important there and can strip stuff like white spaces, unnecessary wording, and then just give the agent what matters.

Then you could also use hooks.

It is its own multiplexer of sorts here.

But it's specifically designed to provide additional data on coding agents that are running in your CLI.

And I've already, you know, one of the reasons this resonated with me when Yuji mentioned it was it definitely feels like I need that.

And I was trying to sort of hack something together a little bit before I even saw this.

There's definitely some cultural things around just kind of how things are done and how we see ourselves.

And I think some of that bleeds into identity, which is that for a long time, we've really conflated CLI proficiency with network engineering mastery.

And separating those two things out is an identity challenge, right? If I'd seen myself as the person who can jump into the CLI on this device and figure this problem out, and then you say, well, actually, we don't want you to use the CLI anymore, that can be really scary on an individual level, right? So I think there's lots of reasons kind of at the corporate level, at the team level, at the individual level that lead to the resistance.

Now, the one thing I will say is most of the resistance at this point, I don't think is actually technical, right? Like there are the tools, there are the protocols, there are the methodologies.

Like we know how to do this.

Right.

Yeah.

I mean, well, I mean, it comes full circle and there is some maturity involved and stuff, but, but I do think like a lot of network engineers to stay on that point just for a second, really, you know, while they're willing to maybe learn a vendor CLI or multiple vendor CLIs, like Python is a bridge too far.

Everything below lives in the repo and gets committed with it.

Kiro runs one agent across the IDE, the CLI, and the web, all reading the same config.

So the rig you set up here follows you to whichever surface you work in next.

1.

What this does not cover, and what is next.

This is the minimum, so it leaves things out on purpose.

It says nothing about custom agents, multi-repo work, or C, where the headless CLI is the right tool and the ID is not.

The config carries over to the CLI untouched, so there is nothing to migrate when you get there.

There's definitely some cultural things around just kind of how things are done and how we see ourselves.

And I think some of that bleeds into identity, which is that for a long time, we've really conflated CLI proficiency with network engineering mastery.

And separating those two things out is an identity challenge, right? If I'd seen myself as the person who can jump into the CLI on this device and figure this problem out, and then you say, well, actually, we don't want you to use the CLI anymore, that can be really scary on an individual level, right? So I think there's lots of reasons kind of at the corporate level, at the team level, at the individual level that lead to the resistance.

Now, the one thing I will say is most of the resistance at this point, I don't think is actually technical, right? Like there are the tools, there are the protocols, there are the methodologies.

Like we know how to do this.

Right.

Yeah.

I mean, well, I mean, it comes full circle and there is some maturity involved and stuff, but, but I do think like a lot of network engineers to stay on that point just for a second, really, you know, while they're willing to maybe learn a vendor CLI or multiple vendor CLIs, like Python is a bridge too far.

Let's see here.

Danny writes, you're over CLI.

This is my first time emailing in.

So I just wanted to say I'm 26 years old and I've been a fan of the show since I was five or six when I first heard my dad play RMG on the radio on the way to school, listening to the barefoot cactus soccer episode.