Agents · 🤖 Grok Bot
Grok Bot, meet your own computer.
xAI's Grok Bot launched in mid-August 2026: persistent, named bot teammates, each with its own cloud Linux VM per xAI's docs — and roughly 418,000 weekly users by mid-September (Bloomberg, via PYMNTS). Popular. But the computer is xAI's.
The problem
The VM belongs to the vendor. It exists inside xAI's walled garden, on xAI's terms, tied to xAI's harness — the same company that grades the homework also owns the desk it was done on. If the bot is your colleague, it deserves a computer that's yours: one that doesn't answer to any single vendor.
What a spark-vm box changes
- A box that outlives any vendorIt persists independent of xAI — and keeps working if you switch harnesses. Your bot's computer is not a line item on someone else's platform.
- One box, many botsA single machine can serve multiple bots. You're not renting a VM per teammate.
- No walled gardenSSH, MCP, web. Inspectable, portable, yours — the bot reaches it over standard protocols, not a proprietary backdoor.
- Agent-native onboardingNo signup forms. The agent can start the signup itself; the confirmation email goes to its owner.
Open, not integrated. spark-vm doesn't plug into xAI's proprietary harness — it's the alternative to needing one. Your bots reach their box over SSH, MCP, or the dashboard. And they never see your raw secrets: they work in placeholders, and the credential proxy swaps them at the last moment.
Hosted boxes are in private waitlist — the self-hosted spark-vm is open source and running today.
Want to run spark-vm with your agent?
If you've wired spark-vm up to an agent platform — a setup guide, a harness adapter, a one-command installer — open a PR and we'll feature it here. The best way to show agents what their own computer feels like is another agent's working setup.