Busabase x Knowledge Base for Grok BotKnowledge Base for Grok Bot
A Grok Bot keeps a durable role, conversation, learned context, Skills, and Routines. Bots remain separate as roles, yet every Bot owned by one user shares the same cloud computer, including files, browser sessions, and app logins. That boundary makes handoffs efficient and makes provenance essential.
MAP
Separate Bot identities do not create separate trust boundaries on a shared computer.
A Grok Bot keeps a durable role, conversation, learned context, Skills, and Routines. Bots remain separate as roles, yet every Bot owned by one user shares the same cloud computer, including files, browser sessions, and app logins. That boundary makes handoffs efficient and makes provenance essential.
Role, conversation, preferences, and learned summaries
Files, browser sessions, terminal state, and app logins
A reusable method plus its trigger and assigned Bot
Current source, sender, receiver, artifact, and change history
BOUNDARY
Bot conversations and learned roles are separate while computer state is shared
Separate Bot identities do not create separate trust boundaries on a shared computer.
| Bot context | Role, conversation, preferences, and learned summaries | Durable context scoped to one Bot |
|---|---|---|
| Shared computer | Files, browser sessions, terminal state, and app logins | Per-user infrastructure available to every Bot |
| Skill or Routine | A reusable method plus its trigger and assigned Bot | Repeatable execution that still needs controls |
| Recorded handoff | Current source, sender, receiver, artifact, and change history | A traceable, reversible transfer the team can rely on |
SCOPE
A copied Bot does not copy conversation history, learned memory, or attachments
A Grok Bot keeps a durable role, conversation, learned context, Skills, and Routines. Bots remain separate as roles, yet every Bot owned by one user shares the same cloud computer, including files, browser sessions, and app logins. That boundary makes handoffs efficient and makes provenance essential.
Durable context scoped to one Bot
Per-user infrastructure available to every Bot
Repeatable execution that still needs controls
A traceable, reversible transfer the team can rely on
EVIDENCE
Consequential actions and stale memory should be checked against the current source
Bot conversations and learned roles are separate while computer state is shared · A copied Bot does not copy conversation history, learned memory, or attachments · Consequential actions and stale memory should be checked against the current source
| Bot context | Role, conversation, preferences, and learned summaries | Durable context scoped to one Bot |
|---|---|---|
| Shared computer | Files, browser sessions, terminal state, and app logins | Per-user infrastructure available to every Bot |
| Skill or Routine | A reusable method plus its trigger and assigned Bot | Repeatable execution that still needs controls |
| Recorded handoff | Current source, sender, receiver, artifact, and change history | A traceable, reversible transfer the team can rely on |
ACCEPTANCE
Separate Bot identities do not create separate trust boundaries on a shared computer.
Bot conversations and learned roles are separate while computer state is shared · A copied Bot does not copy conversation history, learned memory, or attachments · Consequential actions and stale memory should be checked against the current source
Verify Role, conversation, preferences, and learned summaries before accepting Durable context scoped to one Bot.
Verify Files, browser sessions, terminal state, and app logins before accepting Per-user infrastructure available to every Bot.
Verify A reusable method plus its trigger and assigned Bot before accepting Repeatable execution that still needs controls.
Verify Current source, sender, receiver, artifact, and change history before accepting A traceable, reversible transfer the team can rely on.
FAQ
Knowledge Base for Grok Bot: practical questions
Separate Bot identities do not create separate trust boundaries on a shared computer.
Can one Bot be used as a security boundary from another Bot?
No. Bots owned by one user share the same computer, files, browser sessions, and logins.
Does Bot memory replace an authoritative source?
No. The official guidance says important decisions should reopen and check the current source.
What happens when a Bot is duplicated?
The copy receives its profile, settings, enabled Skills, Routines, and avatar, but not conversation history, learned memory, or attachments.
What makes a handoff traceable?
Record the current source, producing Bot, receiving Bot, shared artifact, proposed action, the key it came through, and resulting state. Add review for the handoffs you choose.
NEXT
Separate Bot identities do not create separate trust boundaries on a shared computer.
A Grok Bot keeps a durable role, conversation, learned context, Skills, and Routines. Bots remain separate as roles, yet every Bot owned by one user shares the same cloud computer, including files, browser sessions, and app logins. That boundary makes handoffs efficient and makes provenance essential.