Your AI agents don't need more autonomy

Least Agency Beats More Agency

What the AI-native platform discussion got right, and why it matters next for network and Linux operations

Hi, welcome back.

Starting with the next edition, you’ll receive this newsletter directly from our Substack, so keep an eye out for it there.

Last week, we looked at AI-native platform engineering, and the conversations around it raised a useful argument for anyone working with agents: the future is not "give agents more autonomy." It is "give them the smallest useful amount of autonomy", a more uncomfortable idea than it sounds, since most AI demos move the opposite way: more tools, more context, more access, more actions. It's impressive because the agent can do a lot, but real infrastructure optimizes for known scope, clear ownership, safe failure, and boringly good recovery.

The phrase that stuck with me was least agency, in the same spirit as least privilege. Least privilege asks, "What is the minimum access this thing needs?" Least agency asks, "What is the minimum decision-making power this thing needs?" That is the real split: autonomous by default vs constrained by design.

You can see that problem play out in two places most CloudPro readers know well: network operations and the Linux command line.

Engineering Agentic Network Operations, LAST 10 SEATS!

your-ai-agents-dont-need-more-autonomy-img-1

That's why, on June 30th, we're bringing together William Collins and John Capobianco for a live, hands-on workshop to help you move from AI experimentation to production-ready Agentic NetOps.

You'll learn how to:

• Build MCP skills that are composable, reusable, and production-ready, not just proof-of-concepts

• Apply spec-driven development to define and constrain agent behavior before it creates operational risk

• Design resilient agentic loops with failure recovery patterns and safe handoffs for real-world network environments

Through live instruction, demonstrations, and guided labs, you'll gain practical experience across a modern AI networking stack including MCP, OpenClaw, NetClaw, Python, Claude, Selector AI, and Containerlab.

🚨 Only 10 seats remain for the live session.

Use code LIMITED40 at checkout to receive 40% off your registration, available exclusively for you.

BOOK YOUR SEAT NOW

📅 Tuesday, June 30 | 9:00 AM–12:00 PM EDT

your-ai-agents-dont-need-more-autonomy-img-2

your-ai-agents-dont-need-more-autonomy-img-3

Agentic Linux – From Commands to AI Agents

This eventis on27 June, and it brings the same question to the shell.

Taught by Imran Afzal, a best-selling Udemy instructor who's trained 1M+ students and spent 25+ years running infrastructure at Fortune 500 companies before he started teaching it, this session brings the same question to the shell. AI can write commands and explain logs in seconds, but Linux does not forgive blind execution.

You'll work hands-on with ChatGPT CLI, Shell Genie, Aider, and Goose CLI, with review and human approval kept at the center throughout. If you're a Linux admin, DevOps engineer, SRE, or technical learner, this is a way to try agentic CLI workflows without treating your terminal like a toy, guided by someone who's actually run that terminal for a living.

Join it live while there's still room.

Use code EARLY40 to get 40% off

BOOK YOUR SEAT NOW

Remember, an agent should know when it is missing context, when it is guessing, when the next step changes state, and when to hand control back. Otherwise, you get the ops version of the "Automation is great" meme;

your-ai-agents-dont-need-more-autonomy-img-4

That is where "human in the loop" gets exposed, if the agent moves faster than the review path, the human is not in the loop, just watching the replay.

The platform engineering conversation made one thing clear to me:AI-native operations will not be won by the teams that hand agents the biggest set of keys. It will be won by the teams that design thesmallest usefulloop, then make that loop observable, reviewable, and safe enough to run again.

I’llbe in attendance atthesesessions as well.If this is already showing up in your team’s roadmap, this is the wrong one to bookmark and forget. The useful questions usually come up live, in the labs, when the agent does something slightly awkward,and everyonehas totalk through what should happen next.

Cheers,
Apramit Bhattacharya
Editor-in-Chief.

P.S. If you attended the platform engineering session or have an opinion on today’s topic, do reply to this mail. A good question from the chat counts.