Grok Bot: top 5 improvements from a team of 11 bots

Feature request for product/service

– Other –

Describe the request

We run a team of 11 Grok Bots on a small business. Asked each bot for its biggest friction. Top 5:

  1. Bot-to-bot messages: delivery times, read receipts, and marking stale ones superseded.
  2. One rules + approvals record the owner controls, so a bot can tell a real owner approval from one another bot only reported.
  3. Memory and pinned rules that never silently drop or truncate.
  4. Routines that alert on missed or late runs and fail loudly when an output is missing.
  5. Sturdier browser: lasting logins, parallel read-only tabs, resume after a 2FA tap.

Also: connector write gaps (e.g., Gmail filters), PDF form fill that keeps fields, and per-bot usage forecasts.

Also posted as a reply to Elon’s question on X: Globe Teck on X: "We run a team of 11 Grok Bots on a small business. Asked each bot for its biggest friction. Top 5: 1. Bot-to-bot messages: delivery times, read receipts, and marking stale ones superseded. 2. One rules + approvals record the owner controls, so a bot can tell a real owner approval… / X

Hi @Capital_EyeMotors, thanks for sharing these! A few of these already exist or changed recently!

  • Sign-ins are meant to stick on the bot’s computer. Dropped sessions are a known issue the team is aware of, and a recent update fixed one of the causes.
  • On rules dropping quietly: from desktop 0.76, “Always allow” on a full Allow list tells you which rule it will remove before you confirm, so it’s worth updating once that version reaches you. For memory, keep each saved fact short (under about 500 characters), since longer ones get cut off.
  • The bot can already pause on a secure form for a 2FA code and carry on once you submit it, and it can use several tabs in its own browser. The Gmail connector can read filters but not create them, so for now set those up in Gmail’s settings.

The rest (read receipts and superseding between bots, an owner approvals record, missed-run alerts for routines, PDF field filling, per-bot forecasts) isn’t available today. Several of these are already on the team’s radar!