Grok Bot Exposes VM Resource Limits
Matt Shumer says his Grok Bot appears to have run out of RAM and disk space, raising questions about whether users can scale its persistent cloud computer. Grok Bot gives agents a shared VM with a browser, filesystem, terminal, and durable state.
All of a user’s Bots share one cloud computer, so parallel agents compete for the same RAM and disk capacity
- –The public documentation explains how to reset or recreate a computer, but does not document user-configurable RAM or storage upgrades
- –Browser sessions, files, tools, and durable Bot state make storage exhaustion more consequential than a normal chat limit
- –The incident highlights an infrastructure gap between “AI teammate” positioning and production-grade workload controls
- –Teams running intensive coding, research, or automation jobs will need clearer quotas, monitoring, cleanup tools, and upgrade paths
DISCOVERED
1h ago
2026-08-24
PUBLISHED
6h ago
2026-08-24
RELEVANCE
AUTHOR
mattshumer_
