Grok Bot
Grok Bot
One-line summary: xAI teammate on Cursor infrastructure with its own persistent cloud computer; can hand a coding step to a Cursor Cloud Agent; for repo-backed coding it sees git contents, not the operator’s Mac ~/.cursor/rules.
Vintage: 2026-08-23. First-party session log plus the log’s own provenance note pointing at xAI “Introducing Grok Bot.” One data point.
What it is
An xAI teammate that runs on Cursor infrastructure. The session log distinguishes it from grok-app-builder (chat + preview sandbox) and from local cursor (this Mac). It can hand a coding step to a Cloud Agent. For that repo-backed coding path it sees the same things Cloud Agents see: git contents, repo .cursor/rules and .cursor/skills — not this Mac’s ~/.cursor/rules.
Why it matters to this thread
It is one of four surfaces the session refuses to collapse into “Grok on Cursor.” Skill packs that live only in .grok/skills or in machine-local ~/.cursor/rules will not follow it unless they are committed as .cursor/skills. See agent-skill-discovery.
Key facts (from 2026-08-23-session-cursor-paper-grok-app-builder-workflow)
- “xAI teammate on Cursor infrastructure; persistent cloud computer; can hand a coding step to a Cloud Agent.”
- Same as Cloud Agents for repo-backed coding: git contents, not this Mac’s
~/.cursor/rules. - After a repo symlink
.cursor/skills→.grok/skillsis committed and pushed, “Cloud / Grok Bot coding agents on that repo auto-list Grok skills.” - Provenance in the same source: xAI “Introducing Grok Bot” (teammate, own cloud computer, Cursor Pro+/Ultra among access paths). That is the log’s citation, not a fetched xAI page.
Strengths (from this session)
- Persistent cloud computer; can hand off a coding step without the operator’s Mac.
Weaknesses / concerns
- Does not inherit machine-local
~/.cursor/rules. - Does not auto-list
.grok/skillsunless those skills are exposed via repo.cursor/skills. - Single session log; the “Introducing Grok Bot” page was not fetched here.
Open questions
- How much of the teammate surface (chat, computer, handoff) is distinct from a Cloud Agent versus a thin wrapper around one.
Moonshots consumer-agent datapoint (Aug 2026)
From 2026-08-28-moonshots-sam-altman-singularity-slow-down-emad-runs-18 (pubdate 2026-08-27): peter-diamandis positions Grokbot after OpenClaw and Hermes as "the most genuinely useful consumer AI product" he's seen in 2026 — dedicated cloud computer per bot, parallel specialists, chief-of-staff orchestration (his implementation). emad-mostaque reports running 18 Grokbots in a swarm with Tailscale control of an M4 Max, 5090, and subscriptions. Host hype; not an independent product review.
Sources
- 2026-08-23-session-cursor-paper-grok-app-builder-workflow
- 2026-08-28-moonshots-sam-altman-singularity-slow-down-emad-runs-18 — consumer Grokbot / swarm datapoint (Diamandis/Emad)