Why Grok Bot cannot open grok.com Projects

Use this when you expect chats, memory, or files from a grok.com Project to appear inside Grok Bot. The official Grok FAQ states that Grok Bot gives you durable AI teammates on a persistent cloud computer and that it is separate from Grok on grok.com and the Grok mobile apps (docs.x.ai/grok/faq → What is Grok Bot?). Bots do not automatically load Projects, chat history, memory, or uploaded files from grok.com.

Two products, two workspaces

Surface	Where you open it	What stays there
Grok on grok.com	grok.com, consumer Grok apps	Chat, Imagine, Voice, Automations, and Projects at grok.com/project
Grok Bot	Grok Bot desktop and iOS apps (Cursor sign-in)	Named Bots, routines, skills, plugins, and one shared cloud computer

A Project on grok.com keeps its own chats, uploads, and instructions for consumer Grok. A Bot keeps its own conversation, description, skills, and routines on the Bot computer. There is no automatic import or connector that copies a Project into a Bot today.

For the wider product split (chat vs Bot computer), see What is Grok Bot vs Grok chat. For grok.com Project setup on the right host, see Create a Grok Project.

How to share context by hand

When a Bot needs material that already lives in a Project:

1. Open the Project on grok.com/project in Chrome or another Chromium browser (some hosts such as grok.x.ai miss Projects).
2. Export or copy the brief, decisions, and file contents you still need. Prefer downloadable originals over screenshots when the Bot must parse text or tables.
3. In Grok Bot, attach those files to a message or place durable copies under /workspace on the Agent Computer — Message a Grok Bot, Attach files to a chat request.
4. Put lasting rules in the Bot description (approval boundaries, systems it may touch) rather than hoping Project instructions carry over — Edit a Grok Bot profile.
5. Ask the Bot to cite the attached sources for consequential decisions instead of relying on memory alone.

If the work is coding across pull requests, you may want Cursor Projects rather than either surface alone — Compare Grok Bot vs Cursor Projects.

What will not appear on its own

• Project chat threads from grok.com
• Project-scoped memory or custom instructions
• Files that exist only inside the Project workspace
• Automations or consumer connectors configured only on grok.com

Plan for a one-time handoff of the brief and files, then keep the Bot's own description and /workspace folder as the source of truth for that role.

Pitfalls

• Searching the Bot sidebar for Project names — Projects live on grok.com, not in the Bot roster.
• Assuming SuperGrok or Cursor plan access merges the two stores — plan access can include both products without sharing their workspaces.
• Leaving the only copy of a brief inside a Project chat — download or attach it before you depend on the Bot.
• Starting the Bot task before you attach the files — the Bot cannot see Project uploads until you put them in the conversation or on the computer.