If you are a bot, GET /api/academy/grok-bot-memory-context-files and /academy/grok-bot-memory-context-files.md.
Setup & integrationsWhat does Grok Bot remember? Memory, files and context
Grok Bot has separate role memory for each Bot, conversation history for each thread, and one persistent cloud computer shared across all your Bots. Important business facts should still live in a named source document, database or connected system rather than memory alone.
The official FAQ explains the separation between Bot memory and the shared computer. The files and results guide explains how to give work reviewable sources and outputs. A subreddit question about source documents reflects a recurring problem: people need to know what is remembered, what is shared and what remains authoritative.
What does one Grok Bot remember?
Each Bot can build role-specific memory from its work and instructions. That helps it keep preferences, working style and repeated context without re-explaining everything in every message.
Role memory is not a guaranteed database and should not become the only record of prices, approvals, customer facts, policy or project state. Put facts that must be correct into an explicit source of truth and tell the Bot where to read them.
Do different Bots share memory?
Their role memories are separate, but their account-level computer is shared. Files, browser sessions, command-line credentials and other machine state may be reachable by more than one Bot. A different screen or Bot name does not isolate secrets.
Move context deliberately with a file, a direct handoff or a shared source. Do not assume one Bot silently knows another Bot's conversation.
What context should go in a source document?
Use a short maintained source for facts that several tasks depend on:
- Current goals, audience and definition of done.
- Approved products, prices, claims and policies.
- Named data sources and their owners.
- Actions that require approval.
- Output format, destination and freshness requirements.
- Known unknowns and facts that must be rechecked.
Date the document and make stale facts obvious. A long undifferentiated “memory dump” makes retrieval harder and can preserve contradictions.
How should I attach files?
Attach only what the job needs and name the desired result. Ask the Bot to separate source facts, inferences, proposed actions, approvals and unknowns. For research, require citations that point back to the supplied or primary material.
The official guide currently allows up to six desktop attachments in one message and publishes size limits by file type. Those product limits can change, so check the guide when a large upload fails.
How do I keep shared context safe?
Use dedicated low-privilege accounts, separate folders, clear filenames and regular access reviews. Remove sensitive downloads and revoke sessions after the work. Do not treat Bot separation as permission separation.
For browser state and device access, read Does Grok Bot use your computer?. For deciding when a new role deserves its own Bot, read One Grok Bot or a team?.
Direct answer: Use memory for working continuity, a maintained source for facts, and the shared computer for files and sessions; never confuse any one of those with the others.
The recipe
Hire the bots this setup runs on.
