Your agents, under control
I build with AI agents and share how to get more out of them: give them autonomy, limit their access, and keep track of what they spend.
Each week, I share something I'm working on: what I learn, what goes wrong, and the decisions I make, so you can put it into practice yourself.
One email a week · Free
Getting it to work is just the start
You use agents to write code, automate tasks, or add features to your product. The more work you delegate to them, the more it matters what happens while you're doing something else.
Giving them autonomy means being clear about a few things:
- How do you know what they're doing and when they need you to step in?
- What's their budget, and what happens when they reach it?
- Which data and systems can they access, and with what permissions?
I ask myself these questions whether it's an agent writing code, a bot, or a process running in the background.
More autonomy, with clear boundaries
I want my agents to do useful work without having to approve every step. That means deciding what they can do on their own, when they should ask me, and how to spot when things are going off track.
That's where my experience in infrastructure and security comes in: where to run them, how to isolate them, what access to give them, and how to track their activity and spending. And how to reduce the risk of a malicious instruction leading them to do something they shouldn't.
I share how I'm working through this on my own infrastructure, from a homelab to a VPS or a cloud environment. The setups, the tools, and above all, the reasoning behind each decision.
From my work to the blog
The latest articles I've published.
- Don't let AI think for you
- Security for coding agents: remote, sandbox, and permissions
- Pensabot: how I manage my notes with Telegram and AI
Who’s behind it
I'm Alberto
I've spent more than ten years building software, leading teams, and taking systems to production.
Today I build products with AI agents. I want to give them autonomy while keeping track of what they can access, what they spend, and what happens when they fail. Pirobits is where I share what I learn along the way.
A little more about meA second opinion on your setup
If you need help with your project, I can take a look at how you've set it up with you.
We get to know your project, review infrastructure, access, and costs, and I suggest what to improve and where to start. If you then need me to design or implement it, we can discuss that separately.
Tell me about your project