The Octopus in the Box

CLI agents are like an octopus in a box.

An octopus is independently intelligent in each arm. It problem-solves in parallel. It feels its way through a constrained space with surprising dexterity. A CLI agent does exactly that — it reaches out with different tools, tries different approaches simultaneously, and navigates a confined environment (your terminal, your filesystem) like it was born there.

The "box" part matters. The constraints are what make it interesting. The octopus doesn't need the ocean to be brilliant. Give it a jar to open and it'll figure out the lid. Give an agent a codebase and a set of tools and it'll find paths you didn't know existed.

And then it gets philosophically slippery. Sometimes the agent writes a script. Then it runs that script. Then that script calls the agent back. The octopus made the tool. But the octopus is also in the tool. When a CLI agent authors its own extension and then operates through it, the boundary between tool-maker and tool dissolves. The octopus is the arm is the sucker is the grip.

This recursion isn't a bug — it's the thing. The most powerful pattern in agentic AI is when the system builds the thing that improves the system. It's turtles all the way down, except the turtles are building better turtles. And the box? The box is what keeps it all grounded. Without constraints, the recursion spirals. With them, it compounds.

Try it. Give a CLI agent a codebase and a task that's slightly too complex for a single prompt. Something like: "Read this folder, identify the three biggest code quality issues, write a script that fixes them, then run the script." Watch it reach out, feel the shape of the problem, build the tool, then use the tool. That's the octopus. Now give it one more instruction: "Review what you just did and improve the script." That's the recursion. The octopus building a better arm.