2026-08-27 · Guide
Name Grok Bots So You Can Find Them in a Year
Three sidebar cards say assistant, and next August you will not know which one still owns Monday. You will open the first assistant, then the second, then the copy. One held the standup. You will delete the wrong card because the names were interchangeable, and deleting a Bot deletes its routines. Nothing is team-level. The twenty most recent run records die with that routine. Leftover files can stay on the shared disk.
This page is grok bot naming as a scheme: JOB-NEVER-OWNER. It is not the week-one invoice where Omar deleted temp. You are here because three assistants already look like one person, or because you are about to type assistant into the create field. Primer: what a Grok Bot is. Disk: the shared computer. Read a listing before you paste: how to read a bot listing.
A name is a search query for a tired human. It is not a vault, not a computer, and not a charter. Encode the job, the stop verb, and the owner on the card at create time. Cute labels collide.
Treat next August as the person who will type into the sidebar
You name a bot on the afternoon you create it, when the job is still in working memory. You search for that bot on a morning when Monday is empty, the iPhone can only pause, and three cards share a generic word. Design the string for the second person.
Next August is you with a worse memory. It might also be a deputy told to pause the standup who cannot tell which assistant is the standup. From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine. A deputy on a train who cannot identify the owner card will pause nothing, or everything.
All bots on an account share one persistent cloud computer assigned to the user, not to a bot. Each bot gets a screen. Screens are not security boundaries. Cookies, sessions, files, and CLI credentials are shared. A precise name does not isolate those. It only lets you find the profile you meant to hide, pause, or retire. Isolation is least privilege and what you refuse to sign in. Naming is retrieval.
Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. There is no team catalog of names. The sidebar is the index. If the index is three assistants, the index is broken.
Encode JOB-NEVER-OWNER on the create screen, not in a later note
JOB is the artifact the bot produces. NEVER is the verb it must not take. OWNER is the human who may pause from a phone and edit only from a desk. Three tokens, hyphenated, typed at create. A later note in chat dies on the second morning. A routine loads standing instructions, not a sticky you meant to write.
Grok Bot does not read SKILL.md or CLAUDE.md. Those files belong to Grok Build. A name stored only as a markdown file on the Agent Computer is readable by every sibling bot, and it is not what the sidebar search uses. Put JOB-NEVER-OWNER on the card.
If the name field is short, keep JOB and NEVER in full and initials for OWNER. InboxTriage-NeverSend-H is still searchable. Assistant is not. Do not drop NEVER to save characters. That token is why you do not delete a send-capable card thinking it was research.
| Catalog job | JOB token | NEVER token | OWNER token | Roster string |
|---|---|---|---|---|
| Inbox Triage | InboxTriage | NeverSend | Harun | InboxTriage-NeverSend-Harun |
| Lead Scout | LeadScout | NeverLogin | Harun | LeadScout-NeverLogin-Harun |
| Standup Scribe | StandupScribe | NeverChannel | Harun | StandupScribe-NeverChannel-Harun |
| Chief of Staff Briefing | Briefing | NeverSend | Harun | Briefing-NeverSend-Harun |
| Churn Watch | ChurnWatch | NeverEmail | Priya | ChurnWatch-NeverEmail-Priya |
| Mail Cleanup Assistant | MailCleanup | NeverDelete | Harun | MailCleanup-NeverDelete-Harun |
The last row is the trap inside the catalog. The listing title contains assistant. That is a directory name for search. On your roster, drop assistant. Mail cleanup that can delete is a different card from inbox triage that must never send. If both say assistant, you will retire the wrong one.
Paste the same three tokens into the first line of the charter so the card and the instructions agree.
Ban assistant, temp, and helper as collision magnets
Assistant is a role. Temp is a disposal plan pretending to be a name. Helper is assistant with worse search. All three collide the moment you have two jobs. The product may reject an exact duplicate, or it may accept Assistant, Assistant 2, and Assistant copy. A year later those still search as assistant.
This page does not retell Omar. It bans temp so you never park a weekday job on a card you already intend to throw away. A scratch research pass can still exist. Name it VendorEval-NeverPurchase-Harun, put files under a folder you will sweep, and refuse a standing routine on that card. Disposable work still needs a retrievable name.
| String people type | What it hides | What collides | Scheme replacement |
|---|---|---|---|
| assistant | Every job | Mail, research, and standup as one word | InboxTriage-NeverSend-Harun |
| temp | That you plan to delete it | Any keeper routine you parked because the card was open | VendorEval-NeverPurchase-Harun |
| helper | The stop verb | A second helper that also has no never-line | Briefing-NeverSend-Harun |
| bot, new, copy, test | That this is unfinished | The finished twin you meant to keep | Recreate under JOB-NEVER-OWNER, then retire the stub |
| My Grok | The owner and the job | Every other personal bot on the account | ChurnWatch-NeverEmail-Priya |
Banned does not mean you cannot run a one-shot. It means the create field does not get those families. If you already have them, inventory first. Collision is a retrieval failure. Delete is a routine failure. Fix retrieval before you cut.
Follow Harun through three assistants that hid Monday
Harun runs ops at Northglass Studio, six people who sell lighting kits to galleries. Grok Bot launched in beta on 11 August 2026. In the first fortnight he created three generic names, parked one standing job, then cleaned the sidebar. That is the year-shaped failure compressed into the weeks you actually have.
He created Assistant for overnight mail because that was the pain. He did not encode NeverSend. He connected a mailbox when the account offered it. The session, once granted, lives on the one computer.
The inbox bot drifted into public-page research. He created Assistant 2 for sourcing and signed that screen into a vendor trial. Screens are not vaults. The trial cookie sat in the shared browser.
Weekday standup had nowhere to live. He created Assistant copy and scheduled a 09:00 DM on that card. A routine assigns a workflow to one Bot. Max 50 routines per Bot. The app keeps 20 most recent run records per routine. He had one routine. He had the wrong name on it.
Cleanup Friday arrived. The sidebar looked like one person cloned. He kept Assistant, because it was the original. He deleted Assistant copy, because copy sounded unfinished. Monday 09:00 did not arrive. The standup lived on the copy. The mail bot was still there. The vendor cookie was still there. The twenty run records were not.
| Clock | Card | What it owned | What Harun believed |
|---|---|---|---|
| Create 1 | Assistant | Mail drafts, no NeverSend | The only bot |
| Create 2 | Assistant 2 | Research plus a vendor trial cookie | A safe sibling vault |
| Create 3 | Assistant copy | Weekday 09:00 DM to Harun | Overflow, disposable |
| Cleanup Friday | Assistant kept, copy deleted | Standup routine gone with the copy | He deleted a stub |
| Monday 09:00 | Assistant and Assistant 2 remain | Empty DM. Files and cookie remain | A clock bug |
This is not Omar deleting temp. Omar had one disposable name and one vanished brief. Harun had three names that searched as one word, so the delete was a guess. StandupScribe-NeverChannel-Harun is not a card you delete to tidy mail.
If Monday is already empty, stop renaming in your head and read Grok Bot routine did not run. Ownership first, clock second.
Spell the never-token as a stop verb the listing already named
NEVER is not careful, not be nice, not ask if unsure. It is a verb you can fail: send, login, channel, delete, email, purchase, merge, refund. Take it from the listing boundary before you type the name. How to read a bot listing scores job, never, evidence, heartbeat. The never field on the card should match the never field you just scored. If the listing has no boundary, do not paste it, and do not name a bot after its vague title.
botskills.sh requires every listing to declare a boundary: the one action the bot never takes without a human. Your roster string should quote that action. InboxTriage-NeverSend-Harun is searchable. InboxTriage-BeCareful-Harun is a vibe. BeCareful does not tell you whether the card can send.
Do not encode two nevers if the field is short. Pick the irreversible one. Send beats file. Purchase beats scrape. Channel-post beats format. Write the rest of the never-list in the charter. The name holds the one verb that would make a wrong delete expensive.
If two bots share a job family, the never-token is what splits them. MailCleanup-NeverDelete-Harun and InboxTriage-NeverSend-Harun both touch mail. They are not the same card. Assistant and assistant 2 cannot carry that split.
Stamp initials so a year-later human is still findable
OWNER is a person who can pause from iPhone and who edits on macOS, Windows or Linux. Android and iPad run the companion app. The Bot runs as a non-root user on a managed Linux VM. That VM is not the Linux desktop app. If the owner is travelling with only a phone, pause is the whole toolkit. The deputy needs to know which card to pause.
Stamp a name or initials, not a team. Nothing is team-level. Routines do not belong to Northglass. They belong to one Bot on one user account. Harun on Harun's seat is the owner. Priya on Priya's seat is a different computer, because the computer is assigned to the user, not to a bot. Do not name a bot Northglass-Standup and expect the next hire to inherit it. Copy the charter as text onto the new seat. Do not hand off by hoping the string contains the company.
If two people use one eligible account, the OWNER token is still one human. That is a bad sharing shape, not a naming trick. The deputy who may pause should be written in the charter, and should find the card from JOB and NEVER even if they forget the initials.
Initials collide inside a six-person studio less often than assistant collides. If two Haruns appear, use a surname token.
Reject pet names that survive only while you remember the joke
Grok, Buddy, Friday, Alfred, and the intern are jokes. They work for a week because you still remember that Friday is the briefing bot. In November Friday is a weekday. You will open it looking for the standup and find a send-capable mail drafter, or you will delete Alfred because the joke got old.
Pet names also hide NEVER. Alfred sounds like a butler who sends. The intern sounds disposable, which is how a keeper routine ends up on a card you already plan to fire. If you want morale, put the joke in the avatar. The sidebar string stays JOB-NEVER-OWNER.
A pet name is not isolation and not a computer. Changing a joke to a scheme, if a rename action exists in your build, still leaves the vendor cookie in the shared browser. The string changed. The jar did not. The docs say not to use separate Bots as a security boundary. They also do not say a cute name is a vault.
Align the roster string with the catalog boundary you just scored
You found the job on a listing. You are about to paste. The listing title is written for search on botskills.sh, not for your sidebar in 2027. Read the boundary. Type JOB-NEVER-OWNER to match. Then paste the charter, and put the same three tokens in the first line.
If the listing is Lead Scout, the roster is LeadScout-NeverLogin-Harun, not Research Assistant. Lead Scout never contacts anyone. Encode NeverLogin or NeverEmail, whichever irreversible verb you actually fear on that computer. If you already signed a sibling into HubSpot, NeverLogin is the token that would have stopped you from creating a second research assistant as a fake vault.
If the listing is Churn Watch, the roster is ChurnWatch-NeverEmail-Priya. A card named assistant that also watches churn will be deleted during an inbox cleanup.
Score first, name second, paste third. The reverse order is how a directory title lands on the card and the never-list stays on a web page you will not open next August. How to write a charter is the seven-block paste. This page is the string on the card that lets you find that paste.
Recreate under a scheme name when a rename control is not documented here
This page will not invent a rename button, a pencil on the avatar, or a settings path. Product chrome moves. Confirm the current sidebar actions in the app on a supported desk. Supported clients are macOS (Apple silicon and Intel), Windows (x64 and Arm64), and iPhone on iOS 18 or later. iPhone cannot edit. If a rename action exists in your build, use it only after you copy the charter and any routine text into a file you own.
Treat a rename, if offered, as a new string on the same Bot object. Routines assign to one Bot, not to a nickname. They should stay attached to that profile. The computer stays the same persistent cloud machine. Cookies stay. Files stay. A renamed Assistant is still the mail session. JOB-NEVER-OWNER on an old profile does not wipe the vendor trial. Retirement is still the session checklist, not a label change.
If you cannot find a rename control, recreate: create InboxTriage-NeverSend-Harun, paste the charter, recreate any keeper routine, enable the new copy, pause the old assistant, then retire the old card. Duplicate is not the same move. Duplicate copies profile, settings, skills, routines, and avatar. It does not copy conversation history or isolate the cookie. Both cards still share the computer.
Do not recreate as a security plan. Separate bots are two screens. Recreate is how you stop searching for assistant.
Move keeper routines off labels you already plan to throw away
A routine lives on one Bot. Delete that Bot and the routine is gone. If the card is named temp, assistant copy, or test, you already wrote a disposal date into the owner of the schedule. Move the keeper first.
How to retire a Grok Bot is the order: inventory consoles, recreate keeper routines on a durable bot, sign out, sweep /workspace, delete last. Durable means the string is JOB-NEVER-OWNER, not a synonym for assistant. Recreating Monday onto Assistant 3 is not a move. Recreating it onto StandupScribe-NeverChannel-Harun is.
Hide if you still need the chat. Pause if the job should stop tonight and you are not at a desk. iPhone can pause. It cannot delete. Do not start a naming cleanup on a phone and call the roster done.
If the standing job is already missing, you are on the missed-run page, not on a naming pass. Rebuild from any copy you kept. The twenty-record window will not help you if the routine died with the bot.
Answer the typing argument that assistant is faster than a scheme
The strongest objection to JOB-NEVER-OWNER is honest: you type the name once, assistant is eight letters, InboxTriage-NeverSend-Harun is a slog, and you will remember which assistant is mail because you built it this afternoon.
You type the name once. You search it for a year. You ask a deputy to pause it from a phone that can pause but cannot edit. You try to delete a stub on a Friday and the stub is the standup. The short string is expensive at retrieval. The long string is cheap at create.
Remembering which assistant is mail is a property of this afternoon. Next August has three of them, and one vendor cookie you forgot. There is no audit view outside Enterprise to tell you which profile used the cookie. The name will not tell you either if the name is assistant. The scheme at least tells you NeverLogin versus NeverSend.
The objection wins a slice when you have exactly one bot, no routine, and you will delete it tomorrow after a one-shot scrape. Even then, VendorEval-NeverPurchase-Harun is still one create, and retirement has a card it can find. Speed that produces three assistants is a setup whose failure mode is an empty Monday and a leftover login.
Fail a Friday scan if two cards still share a generic word
This check can fail. Sit at a desktop. Editing and testing routines need one, and the full sidebar reads better there. Open the sidebar. Read every visible string out loud. If two cards share assistant, temp, helper, bot, new, copy, or test, fail. A fail is a change before Monday, not a note you intend to write.
| Check | Fail if | Fix before Monday |
|---|---|---|
| Scheme on every card | Any card is assistant, temp, helper, or a joke | Recreate under JOB-NEVER-OWNER, or rename if your build offers it, after copying charter and routine text |
| Never-token matches the listing | Mail card does not say NeverSend or NeverDelete | Stop the routine. Align name and charter. Do not wait for a send to teach you |
| Owner token is a human | The string is the company, the team, or My Grok | Stamp the person who pauses from a phone |
| Keepers not on disposal names | A weekday routine lives on copy, test, or temp | Recreate the routine on the scheme card, then retire the stub |
| Collision | Two cards still search as the same generic word | One of them is misnamed. Inventory both before any delete |
Pass is boring: every card is JOB-NEVER-OWNER, no two share a banned family, keepers are on durable strings, and you can pick Monday's owner without opening chat. Audit the fleet is the longer pass if you already have nine bots. This scan is only the names.
There is no Grok Bot-specific spend cap, but the account-level On-demand monthly limit applies. A cleanup Friday that deletes the wrong owner does not show up as a token line. It shows up as a missed DM.
Keep a paper index because Grok Bot has no team catalog of names
No page lists your bots, their routines, and their never-lines. You reconstruct the roster from the sidebar plus memory. Memory is how Harun kept Assistant and deleted the copy. Write a paper index, or a file you own off the Agent Computer. Sibling bots can open /workspace.
Update the index when you create, hide, recreate, or retire. If the index and the sidebar disagree, believe the sidebar for what exists now. Before you delete a generic card, paste its routine text under the scheme row that will replace it.
ROSTER INDEX (keep a copy off the Agent Computer)
Scheme: JOB-NEVER-OWNER
Date: 2026-08-27
Seat: Harun, Northglass Studio
InboxTriage-NeverSend-Harun
Job: label overnight mail into four queues. Drafts stay in Drafts.
Never: send, reply live, create labels.
Routine: none this week.
Listing: Inbox Triage. Boundary read before paste.
LeadScout-NeverLogin-Harun
Job: public-page research pack, sourced URLs only.
Never: sign into CRM, HubSpot, or any production console.
Routine: none until inspected.
Listing: Lead Scout.
StandupScribe-NeverChannel-Harun
Job: weekday DM of work shipped yesterday, to Harun only.
Never: post to a shared channel, @channel, or a customer thread.
Routine: weekdays 09:00, this bot only. Copy text before any delete.
Listing: Standup Scribe.
Banned strings: assistant, temp, helper, bot, new, test, copy, Friday, Alfred.
Retirement: never delete a card until its keeper routines exist on a scheme name.
That file is not a charter. The charter still has to live in the bot instructions a routine loads. The index is how a deputy finds the card. Prefer a doc you own over the only copy on the Agent Computer.
Stop when a stranger can pick the owner card without opening chat
Hand the laptop to someone who did not build the roster. Ask them to pause the weekday standup. If they click StandupScribe-NeverChannel-Harun, the names work. If they ask which assistant, you are not done.
A stranger test is allowed to fail. Failure is two cards that still share a generic word, a keeper on a disposal name, or a never-token that does not match the charter. Fix the string, then retest. Do not add a fourth assistant as a workaround.
Naming does not finish isolation, spend, or send. It finishes retrieval. When retrieval works, retirement has a target, a missed run has an owner, and a listing's boundary has a card that quotes it.
Keep reading: Seven Grok Bot Mistakes Everyone Makes in Week One, How to Retire a Grok Bot Without Leaving Sessions Behind, How to Read a Bot Listing Before You Paste It Into Grok Bot.
Frequently Asked Questions
Does grok bot naming replace the never-list inside the charter?
No. The roster string is a search index for humans. The charter is the instruction a routine loads. JOB-NEVER-OWNER on the card helps you find InboxTriage-NeverSend-Harun eleven months later. It does not stop a send if the standing instructions still say be helpful. Paste the stop verb into the instructions, the same verb you encoded in the name. Grok Bot does not read SKILL.md or CLAUDE.md. A name without a charter is a label. A charter without a findable name is a job you will delete by accident. Use both.
If I change the displayed name, do the routines stay on that bot?
This page does not invent a rename menu. If your build offers a rename action, confirm it in the desktop app. From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. A new string on the same bot is a label change on the same profile. Routines attach to one Bot, not to a nickname. They should stay with that Bot object. Files, cookies, and sessions stay on the shared computer. A renamed card is not a wipe. If you cannot find rename, recreate under the scheme, copy routine text first, then retire the old card.
Why not name every bot assistant and keep the job in the charter?
Because you will search the sidebar, not the charter, when Monday is empty. Three assistants hide which card owns the 09:00 DM. Deleting a Bot deletes its routines. Nothing is team-level. The twenty run records die with the routine. The charter text may still sit in a file on the shared disk, which is the opposite of the miss you notice. Week one already billed a deleted temp. This page is the scheme that makes that delete an obvious bad click. Assistant is a role, not a job. Put the job in the card.
I already have three assistants. Should I delete two of them today?
Not until you know which one owns a standing job. Open each card at a desk. List routines, last runs, and the charter. Copy any keeper routine text into a file you own. Recreate keepers under JOB-NEVER-OWNER names, enable the new copies, pause the old ones, then retire using the retirement checklist. Delete first and you recreate the missed-run case. Hide if you still need the chat. The phone app can delete a Bot too, so finish the checklist before anyone taps it. Files and sessions can remain after the name is gone. Naming cleanup is not a security wipe.