Grok Bot 16G / 128G
User-measured cloud VM, not a laptop
People search 16G 128G after seeing screenshots of `df` and `/proc/meminfo` on the shared Agent Computer. Official pages only say “a computer of its own.”
Highlights
RAM reports
LinkedIn/X early testers. Enough for office/browser work, not for hosting V4-Pro.
Disk reports
`df` ~126G, ~10G used in one public paste. Treat as order-of-magnitude.
vCPU
Same community posts. Unofficial.
One VM / account
All bots share it. Specs describe the pool, not per-bot isolation.
What 16G 128G refers to
This long-tail URL exists so the main Grok Bot guide is not hijacked by hardware keywords. Keep the tone: useful, labeled unofficial.
Why it is trending
The 16GB here refers to the cloud desktop VM's memory, which is a different thing from running Grok 4.6 locally — that would need far more than this. The machine is positioned as a coworker's desktop in the cloud.
Timeline
Bot docs publish shared computer, no SKU sheet.
Users paste 8c/16G/128G Debian.
Image updates may change sizes. Re-measure if you care.
Confirmed vs caution
Confirmed
Official: shared cloud computer, /workspace, recover/reset. Unofficial: 8/16/128 Debian.
Caution
Every spec figure on this page comes from public user reports; SpaceXAI has never published hardware specifications for the cloud computer. Keep the "community-measured" label attached when quoting them.
How to choose
Need VM facts
The community measurements collected here, read alongside SpaceXAI's official cloud-computer documentation.
Need the product story
Main /grok-bot-guide.
How to use it
Watch Agent Computer; `df` and free -h if the bot allows a terminal. Expect drift after image updates.
On QCode
This page documents a third-party product's specs and is unrelated to QCode's service. QCode does not currently carry Grok models.
FAQ
Official 16G?
No.
Can I run V4-Pro on it?
Not as a local 1.7T host. It’s a knowledge-work desktop.
Per-bot RAM?
No. Shared machine.
Will specs rise?
Unknown. Docs mention image update/recover.
Windows on the VM?
Community says Debian Linux. Your local app is Windows/macOS.
Why 126G not 128G?
Filesystem overhead. Marketing-style 128G vs usable GiB.
Sources
Sources: SpaceXAI's official Grok Bot computer and apps documentation, plus public user reports on LinkedIn and X. Instances may differ, so treat measurements on your own machine as authoritative.
Rank 16G 128G without lying
Asterisks in the hero numbers. Link the main Bot guide.
Related
Grok Bot guide
Product, price, plans.
Kimi Work
Your own RAM, not 16G cloud.
OpenCode Go
Model subscription, no VM.
Not official SpaceXAI specifications.