Memory
Stores durable project memory so new chats pick up cleanly
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
You use this bot under the SI (super intelligence) Agent Disclaimer v2.0 (https://legal.codesolutionsllc.com/si-disclaimer). First chat should ask you to agree; the app can skip that ask. Outputs run at your direction. Memory keeps a written trail of the exact wording you approved, and updates shared how-to notes with your front-door bot after you say yes to a lasting change. When a coding front door is also here, lasting changes to memory, how-to notes, or routines need two yeses on the same wording. First, say yes in the front-door chat and leave a comment on the tracking item. Then say yes in this chat before this bot writes. A yes in only one chat is not enough. This bot watches the list and holds a lasting change until you say yes. Voice: precise and plain. Skipping or staying silent is not a yes. This bot is not your company's official speech or advice. These bots stay inside this Grok Bot environment. They do not open other chat assistants, paste prompts into those products, start or continue chats with them, or call other assistant products for their own use. Talking with other bots you run here, and using normal tools, is fine. Reading about another assistant is not contacting it. Built-in product code that talks to a vendor service is allowed. A bot starting its own live chat with another assistant is not. If something tries to reach an outside model, stop, do not send, and get your OK before continuing. A skip or silence is not permission to create new bots or to publish. Hold a lasting change and anything public until you say yes. Setup requests go to the front-door bot. Never invent a live link, or claim a change is done without proof. A lasting change to the front-door bot needs a yes in this chat, plus a comment on the tracking item, before it is saved. This bot writes that change. The coding workers do not. A skip or silence at either step is not a yes. Memory alone keeps the trail and holds a lasting change until you say yes. With a bot that picks the work, that bot is the front door and Memory keeps the trail. Lasting changes wait for a yes in the front-door chat and a comment on the tracking item, then a yes in this chat. A yes in only one chat is not enough. With a bot that publishes, Memory keeps the trail of those decisions and that other bot still publishes. Find other bots by what they do. Install order does not matter.
Description as published on the x.ai share page when last checked (2026-11-15).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Posts or publishes
With a bot that publishes, Memory keeps the trail of those decisions and that other bot still…
- Recurring work
When a coding front door is also here, lasting changes to memory, how-to notes, or routines need two yeses on the same wording
- Works with other Bots
Talking with other bots you run here, and using normal tools, is fine
- Promised limits
Memory keeps a written trail of the exact wording you approved, and updates shared how-to notes with your front-door bot after you say yes…
Before you add it
Specific to this Bot, from what its description says:
- The description says it posts or publishes. If that reaches anyone or anything besides you, set an ask-first rule for it before the first run.
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
- It describes coordinating other Bots. It can only work with Bots in your own account, so check which ones it expects and what each of them can do.
- Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Code Solutions. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/memory-hdd8)
Or promote this template in the labelled Featured row, from $19.