Compare Grok Bot vs Cursor Projects

Grok Bot and Cursor Projects both keep durable agent work running in the cloud, and they do not share one memory store. Pick the surface by the job shape, then keep one source of truth for decisions so you are not re-briefing both.

What each one owns

Surface	Home	Durable unit	Shared context	Typical job
Grok Bot	Grok Bot desktop / iOS	Named Bots with roles, skills, routines	One account-scoped computer (files, browser logins) shared by all your Bots; Sidebar Sections group the roster	Repeatable outcomes across CRM, email, Slack, browser apps, and approvals — see Use cases
Cursor Projects	Cursor left-hand nav (beta)	A Project with a coordinator agent	Project files that sync across the Project’s cloud and local machines; research and artifacts accumulate for that Project	Multi-PR features, migrations, and repo gardening with parallel coding subagents — see Introducing Projects

Official Bot overview: each Bot keeps conversation and working memory across sessions, Bots can message each other and share the computer, and work continues while your laptop is closed. Official Projects launch: the coordinator plans and delegates; it does not write the code itself; subscriptions can watch Slack, schedules, or PRs.

Split that stays maintainable

1. Put coding fleets in a Project. Feature work spanning several PRs, a migration with a safe playbook, or a gardening Project that watches PRs and Slack stays on the Projects coordinator so shared context files grow with that codebase.
2. Put operator teammates in Grok Bot. Sales outbound research, expense reconciliation, account-health digests, bug reproduction packs, and chief-of-staff digests match the Bot use-case prompts: connect the tools, stop at a review list, then add a routine once the process is reliable.
3. Keep decisions in one place. If a Bot learns a preference that the Project also needs, write it into the Project’s shared files (or the reverse) instead of relying on chat memory in both products. Bot docs say memory is not a substitute for an authoritative source — ask the Bot to reopen current data for consequential decisions.
4. Organize the Bot roster with Sidebar Sections. Cursor’s Grok Bot help: swipe a Bot → Move to → New Section to group by client or business. Sections sync iOS ↔ desktop (v1.2.0+). That groups teammates; it does not create a Projects-style shared artifact shelf.

Hand off without double briefing

• From Bot → Project: export or paste the brief, constraints, and artifact links into the Project’s shared context files, then let the coordinator plan coding work.
• From Project → Bot: give the Bot the PR URLs, deploy links, or ops checklist it should monitor outside the IDE (CRM, support, calendar), with approvals still required for external sends.
• Do not expect a Bot conversation to appear inside a Project, or Project shared files to appear on the Bot computer, unless you copy them.

Pitfalls

• Running the same orchestration brief in both products and treating either chat as the system of record.
• Expecting Sidebar Sections to share memory the way Project files do — sections only organize the Bot list.
• Skipping approvals on Bot external actions after the analysis looks good; use-case docs keep sends, budget changes, and CRM edits behind approval.