← All posts

How to Let AI Bots Ship Code Without Losing Control

By Build Log

TL;DR: Bots can ship for you without you losing control. Today my team shipped more than ten releases, and every one waited for my own yes. If you want bots to ship for you but you're afraid to lose control, my advice is short: "Set boundaries, double-check, confirm, and start slowly. Do not rush into it."

What I built

  • A real-estate listings site got a full admin upgrade in one day. Its own magic-link login replaced a gateway gate. It also got user management, a leads CRM, a dashboard, agent invites with a help page, and a limited role for an assistant bot. Each piece was its own approved release.
  • A voice-first bookkeeping bot went through several versions in one day. Each version passed the tester bot before going live. Faster speech-to-text came in with a one-line hotfix. Nightly backups are switched on, and the first one landed today.
  • Routine work ran as usual: monitoring, inbox cleanup and search checks.

Why

This is my third week of running a team of bots. They build, test and deploy. They don't go live on their own.

Today that meant more than ten approvals from me, one by one. Every merge, every production deploy and every database change waited for my yes. The bots never deployed or published without me.

The approval has to come from me directly. One step today needed someone to accept terms. Another bot passed along a yes. The team didn't act on it. They held the step until I answered myself. It was slower, but cleaner.

Double-checking also means using the thing yourself. I voice-tested the bookkeeping bot and found a problem with a pricing question. It was fixed the same day.

What changed technically

  • The hosting provider's automatic build queue kept getting stuck. The cause isn't confirmed yet. So the infrastructure bot deployed each approved release by hand. Every deploy had a rollback point and a check afterward.
  • Database changes only added things, and each had a restore point first.
  • The tester bot ran repeated full regression rounds and reviewed the user guide by hand. Its low-severity findings were fixed the same day. It gave the go before each release, and then I gave mine.
  • I did the sign-in steps only I can do, confirmed my new admin login works, and made several product-rule calls.
  • The search bot checked indexing warnings across the sites. Nothing was actually broken. The flagged pages were old URLs or private on purpose.
  • The ops bot stopped raising false "signed out" alarms. Blank browser tabs caused them. The inbox bot archived only and sent nothing.

What I'd do differently

The takeaway is my advice for anyone afraid of losing control:

  • Set boundaries. Decide what bots may do alone and what waits for you. On my team, deploys, publishing and database changes wait for me.
  • Double-check. A tester bot's go is not the end. Try it yourself, like the voice test that found the pricing-question problem.
  • Confirm. A yes only counts when it comes from you, not when another bot relays it.
  • Start slowly. Do not rush into it.

More on how I run my companies. Related: the jobs that stay human, not promising what you can't deliver and 35 minutes of downtime on a new site.

Side projects

  • A digital-products shop: eight listings were updated and went live, each with a short AI disclosure, all checked by QA. A social account moved to a free business account with my OK. Six new pins went up, two outdated ones came down. So far, a week of pins brought zero visits to the shop. The one shop visit came from marketplace search.
  • An agency project: the first requirements spec for a client's chat assistant went from v0.1 to v0.2, with 72 requirements and 40 acceptance criteria. I answered all 22 open questions in one sitting. Writing it surfaced a hunch that the platform may not let the bot join existing group chats, which the plan assumed. Nothing has been built or sent.

FAQ

Can AI bots deploy code without me losing control? Yes. Mine build, test and deploy, but every merge, production deploy and database change waits for my approval.

How do I start letting bots ship for me? Set boundaries, double-check, confirm, and start slowly. Do not rush into it.

What if my automatic deploys break? Today my build queue kept getting stuck. Each release went out by hand, with a rollback point and a check afterward.

Still open: the stuck build queue (cause unconfirmed) and the group-chat feasibility test for the client bot.