Isolate parallel Grok Bot projects when status beats mix

Official Bot FAQ: each Bot keeps its own conversation and learned role. Files, browser sessions, group messages, and direct handoffs still move across the roster because every Bot on the account shares one cloud computer. If two “bots” you opened are actually the same underlying agent id, durable memory and recurring status routines can refresh one project into the other chat.

Prefer two real Bots

1. Create a second Bot with Create your own / Create new agent. A second chat tab on the same Bot stays the same teammate. Get-started and Bots docs treat a Bot as one named teammate with its own conversation.
2. Name each Bot after its project. Put the project scope, folder path, and “answer only this project” rules in that Bot’s description.
3. Give each project its own disk folder under /workspace so files stay easy to tell apart even though the computer is shared.
4. Keep status-beat routines on the Bot that owns that project. High-frequency beats keep that project hot in memory; running them on a shared agent id makes cross-talk worse.

Creating another Bot does not create another computer or a security vault. See Do Grok Bots share one computer.

Clean a mix-up that already happened

1. In the contaminated Bot, ask it to list the preferences, role facts, and standing project summaries it is using.
2. Tell it to forget facts that belong to the other project, then confirm those lines are gone.
3. Edit the Bot description so standing instructions match only the project you want next.
4. Pause or delete the status-beat routine that keeps refreshing the wrong project.
5. For important decisions, ask the Bot to re-check the current source in addition to anything it remembers (Bot FAQ).

Full memory steps: Inspect and delete what a Grok Bot remembers.

When it still looks like one agent

If two separate Bot chats keep sharing progress and you can see the same agent id in both, treat that as a product bug report: include both Bot names, the shared agent id, OS, app version, and a short timeline. Forum reports of status-beat leaks describe that pattern. There is no documented user control that hard-partitions memory across chats that already share one agent id.

Pitfalls

• Two chats on one Bot are still one teammate. Isolation starts with two named Bots.
• Separate disk folders do not stop shared memory when the agent id is shared.
• Do not treat a second Bot as a security boundary for logins or secrets on the shared computer.