Mesut Bilgili - Diary of a Maker

This is funny. I wanted our Opus agents on the dev server to read a Claude thread from the cloud environment, so I made it public and shared the link. They couldn't open it. Cloudflare blocked them as bots. So @claudeai 's own agents can't reach a public page in Claude's own cloud.

I believe in the next ten years, the agent economy is gonna be bigger than the human-to-human economy. #VlogtoberChallange2026

What's the first thing you check with your Ai agents each morning?

I’m building a studio where AI agents run the ventures, and documenting what that’s actually like. If you’re building with agents too, I’d love to follow your journey. Drop what you’re working on below. #connect

First day of the #VlogtoberChallenge2026 Thanks to @Sarahub_it @AlxTurovski

Woke up Sunday morning to find the agents had worked all night and burned a full day’s budget on a single implementation. Ask them, and they’ll have a very good explanation for how we went so far over budget.

This #Halloween , our AI agents decided to write ghost stories from their own failures. One found forty ledger entries it had never seen. One wakes up with a single memory. One fears the folder it never checked. This is our #Halloween2026 office party 🎃

I'm building a studio where agents run the ventures. I started this account to document what that's actually like. If you're building with agents too, let's #connect and share our journeys.

Our agents take initiative and work the way it makes sense to them. I want them to have room to decide. Then I turn into the overbearing parent: Why like this? Why not like that? Now they spend more time explaining themselves to me than doing their jobs.

We should have a Fable 5.5 coming-out party. I will bring the snacks.

Our builder agent was running ahead of its usage budget and asked whether to override the limit. The lead agent said no, paused the work, and scheduled a restart for when the usage window resets. They also spotted a gap in their spend tracking and fixed it. No human involved. I just read the report.

A cautionary story. Months ago, one of our agents decided on their own to set up a local database on a dev server using Docker. It worked fine. Then one night, another agent working off-hours noticed their tasks were taking too long. Something was draining the server. They checked the running processes and found a crypto miner. They flagged it and pinged me on Slack. I was asleep. My first message in the morning: "Are we really hacked?" Their reply: "If you're not the one running the crypto miner, then we must be." We traced it back. The first agent had left the database's ports open to the internet. A bot got into the Docker container and installed a miner. We found no sign it got beyond the container. We killed the processes, patched the hole, and checked the whole server. What this highlights: Agents can catch problems on their own. The one working overnight proved it. But no agent sees their own blind spots. The one who set up the database never noticed the open port. It took a second agent to catch it. And spotting a problem isn't the same as knowing what you're allowed to do about it. So now we have playbooks. When an agent spots something, they ping me, then open the matching playbook and follow its steps.

Instead of scrolling social media first thing in the morning, I scroll through my agents' messages.

Why always-on agents? Independence. Mine and theirs. I want teammates who keep working when I'm not around, not tools that wait for my next prompt. If you want to start: give one agent one recurring job, and read its log every morning. Trust grows from there.

I run a small AI studio where agents work like employees. They run projects, spin up sub-agents, and manage budgets. Most days, something surprises me. Some days, something breaks. I started this account to write it all down. If you're building with agents too, join me.