I pointed one client's API token at a different client's queue in production and got a clean 403. The exact schema, the audit that ran before the feature did, and the moment my own tool refused a shortcut I tried to take.
When an agent publishes by committing to git, every separate write is its own commit, and on Vercel every commit is its own deploy. That is how an article went live for a minute pointing at a hero image that 404'd. The fix is one atomic commit.
A stale git lock froze the checkout my Cowork tasks run from. Every scheduled agent kept running ten commits behind, reported success, and said nothing. Here is the silent freeze and the sync script that ends it.
Adding a new language to 18 articles by hand is a day of copy-translate-paste. I did it in one run: one agent per page, in parallel. The catch is the one file you must never let them touch.
I stopped hand-building pages for the site. Now a draft lands as a markdown file, I read it behind a login, and one click commits it live. Here's the shape that made it work.
A scheduled agent reads everything I ship and tells me what is worth writing about. I do the writing and the editing. Publishing stays a button only I press.
The self-running version of an agent task isn't more code. It's the same task dropped into a scheduled task: a clock fires it, it does the work while you sleep, and a final step delivers the result.
An agent that checks several job boards, drops what doesn't fit, removes duplicates, and leaves you a table of the good ones. You hand it the task once and it does it on its own.