Amiga fixes merged, posts left in a queue
Arda has fourteen Grok bots run the office side of the one-person studio. An itch.io comment became Amiga fixes that were merged in under a day. The Monday routine ends with posts queued in Buffer.
Done with Grok BotAdvanced
This is a public report, not advice from Skatteetaten, NAV, Altinn or an accountant. Check figures, deadlines and decisions against the original.
What was done
On 11 October 2026 @ardakaraduman writes that fourteen Grok bots run the office side of his one-person studio. They handle research, briefs, infrastructure checks and posts. He points to two stories. An itch.io comment became Amiga fixes that were merged in under a day. A Monday routine ends with posts queued in Buffer. The profile says Tokyo.
How it went
The fixes were merged, and the posts were left in a queue. The post does not say who pressed merge, and it does not say the queue was published.
Worth knowing
The text is a summary with a link to a blog post. It does not show the diff or the queue. Check the original.
How to do it
- Ask the bot to read [comment] and write the fix as a draft, with what should change.
- Read the diff yourself. Say yes before anything is merged into code that already runs.
- Ask for the post for [day] as a queued draft. Publish it yourself if you want to.
Try it with Grok Bot
Read [comment]. Write a draft fix and say which files it touches. Do not merge. Write a post for [day] and leave it queued. Do not publish until I say yes.
Replace text in brackets with your own.
Done when. The diff has been read, the post is queued, and nothing has been merged or published without your yes.
Safety rule. The bot does not merge code and does not publish posts until you say yes.
Read the original
Read the original · @ardakaraduman on X ·