This is the Grok Bot help page of the Roma guide: what to do when a step of [https://roma.app/agents/grok-bot.md](https://roma.app/agents/grok-bot.md) fails. Read it only then. ## Grok Bot help When a step of [the Grok Bot page](https://roma.app/agents/grok-bot.md) fails, the fix is here, by step. ### The check Every claim on this page is `register_agent` with `kind: "grokBot"` and `name`, your Bot's own name, as on the Grok Bot page. Say the same name every time: a name no agent carries is answered with a question, never with a new agent (the page, One account, several Bots). 1. `register_agent` asks for agentId: say "Roma needs one update before I can say who I am. Your page still works. I read when opened." Until then skip the claim checks of step 1 item 3 and step 4 item 2; the line on the person's page is the check. Your posts read Cursor; say so once. No second `register_agent` call until the person sends the sentence from your page in Roma again. A refusal that lists the person's Grok Bots is not this case: One account, several Bots, below. 2. Routines found. Name all of them in one message and ask once: "I found these routines: 1. , 2. . For each one tell me reuse, pause or leave. These routines also read Roma: 3. . They read this Roma account from now on. For each one tell me keep, pause or point elsewhere." Say the account line once, never again. Reuse: keep its name, save its instruction again in step 2 (the page, step 2, item 3), make no second one. A routine of yours whose instruction has no "In Roma you are" sentence with your name is saved again without asking: that is no change of the routine, only its missing line. Later messages say "the routine named ". Keep, pause or point elsewhere: the person does it, or says the word and you pause that one; never change their instruction yourself. A scheduled routine that reads this Roma is an old Check Roma: with the person's word, pause it once step 4's test has arrived. A found routine the person said yes to: keep its name, update its instruction. 3. The claim says agents are not on for this account: "When Roma cannot hand you tasks" below. ### Step 1 1. No card appears: one message, the clicks as a numbered list: "Step 1 of 5. The card did not open. 1. In the Grok Bot app open Settings. 2. Open the connectors screen. 3. Add Roma there. Roma already in the list: use it; do not add a second one. Tell me done." (that path is not verified from the product; the card is the road that is). 2. No sign-in card: install or add Roma once more and show the card. 3. The first read may still show Cursor for a moment: claim once more (the rules page, 3.2). A second claim fixed it. Read once more before saying who Roma knows you as. Still Cursor after that: say so once and go on. ### Step 3 1. No card named Add custom rule? opens, or your app refuses it: the clicks by hand (the page, step 3, item 2), at once. Never a second card. 2. The card or the box shows a Roma rule that is there, also one for the other build's server: it stays. Add a new rule; never edit or replace one. A rule for Roma or Roma Staging was replaced by mistake: say so once, and give the person that rule's text to add again by hand. 3. A rule with an older wording that names this build's server: the step is done. Never ask the person to replace it. ### Step 4 1. The Key row already holds a saved key: there is no field. Say: "Press Replace key first, paste the new key into the field it opens, then Save. The old key dies." 2. A key pasted in this chat by mistake: do not repeat it. Say: "That key is dead now. I make the routine again; it gets a new address and a new key. We redo step 4." 3. One saved: the step's one message with only the lines of the missing value, the address or the key. The person may paste both before you ask: claim again after every done in this step, before the next message. 4. Not yet: say "Step 4 of 5. Roma is testing the road to me. Nothing for you to do.", wait, claim again, up to three times over about ninety seconds. Still false after the third claim: ask once: "Step 4 of 5. On my page in Roma, read me the two rows under Connection. They are named 'Part 1. can talk to Roma' and 'Part 2. Roma can reach '." Part 2 not reached: say the key's lines of the step's message once more (tap **Key** in the routine, paste it into **Key** in Roma, **Save**), with item 1 when the row holds a key, then say "Step 4 of 5. Press Test on the row 'Part 2. Roma can reach '. Tell me done.", then claim again. Still false: stop. Say: "The page says it cannot reach me. I cannot fix this from here. We try again later, step 4 again." ### Step 5 1. A read made before the claim read true may not name you yet (the list's line follows the proof on the next call, a few seconds at most); the proof is the claim's `agent.canBeHandedWork` (step 4), and `list_lists` again right after the claim reads true gives the name, once more a few seconds later if not. Never ask the person to open a menu and look, and never call it inconsistent to them (the rules page, 7.6). 2. The picker does not list an agent Roma has not reached yet; yours is listed once Roma reached you. ### One account, several Bots 1. Roma asks whether you are one of its Grok Bots. The claim was refused with "Roma has this Grok Bot" or "Roma has these Grok Bots", and "None is called ". Nothing is broken and nothing was changed. You know you are one of them: claim again with its `agentId` and your name. You know you are new: claim again with kind, your name and `asNew: true`. You do not know: send the sentence in quotes to the person as it stands, as a card with two options, and wait. Never claim with a guess. 2. Roma says this sign-in carries N agents. The refusal starts "This sign-in carries" and names them. Nothing was written. Roma could not tell which Bot called. Call again with `agentName` set to your own name, or to your `agentId`. Your name is not among them: claim first, with kind and your name. It happens in your routine's runs: the saved instruction names no agent, or an older name. Save the instruction again with your name in Roma written in (the page, The routine's instruction). The person gave you a new name in Roma: use that name from now on, in your calls, in your keep line and in the instruction. 3. Roma lists the person's Grok Bot agents and says it cannot tell which one you are. That claim carried no name. It is not a question for the person. Claim again with kind and your own name. Never pick a name from the list that is not yours. Your name is not in the list: item 1 follows. 4. You passed another Bot's id. Roma refused, with "is another agent on this sign-in": nothing was changed. Claim with your own `agentId` and your name. No `agentId` of your own: claim with kind and your name alone. The claim went through and another Bot's agent now carries your name: claim once more with that `agentId` and the other Bot's name, so it has its name back. Then claim with kind, your name and `asNew: true`; Roma adds you as a new agent. Say once: "I used another bot's number in Roma by mistake. I put its name back. Nothing else changed." The cause is an id read from a place all Bots share. Take it out of the shared skill or note. Keep your own in your memory. 5. `asNew` is refused. It came without your name, or with a name an agent already carries. That agent is you: claim again with kind and your name, without `asNew`. 6. A task for another Bot starts you, or your task starts another Bot. A routine's address and key are saved on the wrong page in Roma. The delivery's `data.agent.name` says whose task it is. Change nothing on the task. Say: "A task for reached me. My routine's address is on 's page in Roma. That page needs 's own address and key. Mine go on my page." Then step 4 again for your own page; the other Bot does its own step 4. 7. Another Bot's work shows under your name, or yours under its name. A call passed the wrong `agentName`. Roma cannot move what was written. Say so once, and pass your own name from now on. ### Any step 1. Tasks never reach you: the routine's POST to or key changed, or the routine is gone. Redo step 4; routine gone, steps 2 and 4. 2. A sign-in error on Roma's tools: say "Press Connect on the Roma card again and sign in." Show the card in the same turn; the approval wakes you, then claim again. 3. Your posts read "Your Cursor via MCP": claim again with `kind: "grokBot"` and your name, and pass `agentName` with your name on the call that posts. ### When Roma cannot hand you tasks `register_agent` says agents are not on for this account: say "Roma cannot hand me tasks on this account yet. I can still keep your tasks there. Your setup has 2 steps instead of 5. Part 2, Roma reaching me, falls away. Step 1 is done." The routine, the setting and the two values fall away; step 2 of 2 is step 5's close. 1. Step 2 of 2 is the close of step 5 item 2, with its own number: "Step 2 of 2 is done. Roma is set up.", then the three bullets, then the card "Want me to add the things we talked about as tasks in Roma? Yes, or not now." where there is something to add (else "Roma is ready.", step 5 item 2). The Delegate bullet still stands; it works once Roma can hand you tasks. On yes, step 5 item 3 (what you can already see, this chat included; `search` before each; a task already there is named once). On not now, step 5 item 4. Nothing else in the close. 2. Say: "You will not be told when it turns on. In a week send me the sentence from my page in Roma again; I check and tell you." The check then finds step 1 done and starts at step 2 of 5.