Hundreds of PRs a Day: Where Grok Bot's Speed and Quality Come From

The Grok Bot team recently released a wave of new features. matt palmer demonstrated them in a video: Pages, Vault, 1Password, Apple ecosystem integration, bot-made videos, new roles, X Spaces, plus a bunch of polish on the details.

This video itself was also edited by a bot. Someone in the comments asked whether the edit was done by a bot; the result was surprisingly good.

Beyond the updates, lauren from the Grok Bot team talked about how they maintain this pace of iteration. The core idea in one sentence: make simple things the right things to do. That means shaping the codebase so agents can easily get started—when a bot comes in, it knows where to make changes, rather than relying on humans to explain the context.

As a result, engineers, designers, and PMs together merge hundreds of PRs a day. That includes fixing bugs, polishing interactions, and improving performance and stability. Of course they make mistakes too, but the principle is to improve the process after every incident so the bot won't make the same mistake twice.

lauren also raised an easily overlooked point: software development is an iceberg. New features are only the part above the water; the bulk is below the surface—maintenance, refactoring, bug fixing, and preventing regressions. When discussing where tokens are used, most people only see new features. The competition in quality and speed is fought in the work below the surface.

In her view, Grok Bot is currently the most noteworthy destination for tokens in the industry—quality and speed, with no compromise.

User feedback concentrated on a few areas:

One user turned their chief of staff bot into a pumpkin, and others said: everyone should have a pumpkin bot.

Someone else posted a picture of a pumpkin bot, and matt palmer replied: PSB.

One user thanked them for the notification sleep feature—no interruptions when the desktop is active. In their words, it was the biggest feature pain point they hadn't realized they needed. Someone else mentioned a 1Password connection failure and reported the issue; they were using the latest version of 1Password. Another person said they now only use Grok bot, with other agents also managed centrally through it, and it gets better every day.

Someone also asked a practical question: how do you make a codebase agent-friendly? lauren's answer was already in the original post: make simple things the right things to do. A commenter pointed out that this is the same idea as Brad Abrams's early "Pit of Success"—design the system so that the correct action is exactly the easiest action.

Most teams are still arguing about where tokens are spent. Grok Bot has already written the answer into its codebase, letting hundreds of PRs a day speak for themselves.