What each Bot remembers
Grok Bot is xAI's agent product. It is different from the Grok chat assistant and from Grok Build, xAI's coding CLI, covered in our Grok Build guide. In Grok Bot, each Bot has its own memory. It keeps your preferences, the rules you ask it to follow, and a dated log of its work, as described in xAI's overview.
A Bot retains stable preferences, important facts, and summaries from its work, which lets it keep a role over time without replaying every prior message (xAI). To check what it pulled, ask the Bot what it used from memory, and it shows you (xAI).
Start a new Bot with its job, sources, and boundaries
In your first message, give the Bot its job, sources, and approval boundaries, and ask it to remember them (xAI). The Bot keeps lasting rules in its memory, so this first message shapes all later work.
When you discover a durable preference, boundary, or responsibility that should shape future work, tell the Bot and ask it to remember (xAI). In xAI's example, an expenses Bot fills in missing details from memory. Its work log has last year's 2-day pass, and you gave it a rule to use the work card for conferences.
Remember, fix, and forget
A Bot decides on its own what to remember. You can also ask it to remember something, fix it, or forget it (xAI). Use that freely: ask the Bot to fix anything wrong and to forget anything you no longer want kept.
Memories can go out of date, so for numbers that change, like prices, ask the Bot to look them up again (xAI).
Keep logins and cards in Vault
Keep logins and cards out of memory and in Vault (xAI). Vault keeps your logins, cards, and contact info so your Bots can sign in to websites and check out for you without seeing the secret values, and a Bot never sees a saved password, card number, or security code (xAI).
Vault covers your whole account: everything you save is available to every Bot on your account, and you cannot limit an item to one Bot (xAI). Entries can carry a hint, such as 'Use for work purchases', and a Bot follows the hint when it chooses between entries. When you give a Bot a name, address, phone number, or email in chat, it saves it as contact info once the task is done and tells you what it saved (xAI).
Deleting, hiding, and duplicating a Bot
Deleting a Bot erases its profile, conversations, memory, routines, and attachments, including the shared facts it saved for your other Bots (xAI). If you may need the work later, or want to keep the Bot's memory, choose Hide from sidebar instead.
A duplicated Bot carries the profile, settings, enabled skills, routines, and avatar, but not conversation history, learned memory, or attachments (xAI). Duplication copies the setup, not what the Bot learned.
Add a long-term knowledge base through MCP
Bots can use other services through plugins and custom MCP servers (xAI). A Bot can add an MCP server that is not in the catalog, by URL or by a command that runs on its computer, and a server started by a command is available to your other Bots too (xAI).
KnowMan runs a hosted remote MCP server at https://api.knowman.io/mcp that accepts OAuth sign-in or an API key sent as an Authorization: Bearer header (KnowMan MCP). For clients with MCP OAuth, the documented setup is to add the server URL, sign in, and approve (KnowMan MCP). The server exposes kb_search, kb_ask, kb_get_item, kb_save, kb_recent, and kb_memories (KnowMan MCP).
Where KnowMan fits
Bot memory is built for preferences, rules, and a running log of work. It is not a place for the articles, specs, and links you want to find again months later. KnowMan is a knowledge base for that: its MCP server can save a link, search saved items, return the readable content of one item, answer questions with citations, and keep memories such as claims, decisions, and playbooks (KnowMan MCP).
For clients with MCP OAuth, the documented setup is to add the server URL https://api.knowman.io/mcp, sign in, and approve (KnowMan MCP). A Bot can add an MCP server that is not in the catalog, by URL or by a command that runs on its computer (xAI). Once the server is added, kb_search searches your library and kb_ask returns a cited answer (KnowMan MCP). For more, see knowledge bases for AI agents and persistent memory for AI agents.
Questions people ask
How do I ask a Grok Bot to remember something?
Say it plainly and ask the Bot to remember. When you discover a durable preference, boundary, or responsibility that should shape future work, tell the Bot and ask it to remember (xAI). You can also ask it to fix or forget something later (xAI).
Do all my Bots share one memory?
No. Each Bot has its own memory, but a few facts about you, like your name and time zone, are shared by all your Bots (xAI). Tell any Bot your time zone, and all your Bots know it, while Bot-specific facts stay with that Bot alone.
What happens to a Bot's memory when I delete it?
Deleting a Bot erases its profile, conversations, memory, routines, and attachments, including the shared facts it saved for your other Bots (xAI). If you may need the work later, or want to keep the Bot's memory, choose Hide from sidebar instead.
Can a Grok Bot read my saved articles?
Bots can use other services through plugins and custom MCP servers (xAI). KnowMan runs a hosted MCP server at https://api.knowman.io/mcp, and its tools include kb_search, kb_ask, kb_get_item, and kb_save (KnowMan MCP).