Grok Bot roles split solo dev work, Devin writes code

The setup is a response to a concrete problem: as personal repositories multiplied — a Chrome extension, a Python library, a VS Code extension, a portal site, and Zenn drafts — running everything through a single chat mixed context and blurred who was responsible for what. The fix was organizational as much as technical, assigning exactly one responsibility per bot and routing shared rule changes from a master bot to each one.

Implementation moved to Devin after Cursor's cloud agent and Grok Bot turned out to share a usage quota, so running the agent drained capacity from the bot side. Sessions use a mode chosen by workload — normal by default, fusion for heavy work, and ultra only with approval — and review always runs in a separate session from the one that wrote the code. Completion is reported through a Webhook, with an hourly watch as a backstop for missed posts.

The merge policy draws a line between light PRs, which the responsible bot can merge once CI passes, and fatal PRs, which a human approves; AI review comments are read but not treated as a merge condition. The developer notes that working through bots has shifted the center of the development environment from a local IDE to the cloud.