This is the Grok help page of the Roma guide: what to do when a step of [https://roma.app/agents/grok.md](https://roma.app/agents/grok.md) fails. Read it only then. ## Grok help When a step of [the Grok page](https://roma.app/agents/grok.md) fails, the fix is here, by step. Screen names on grok.com are unverified: on a mismatch ask what the person sees. ### The check, then the count The check's point 2, asked for `agentId` (today's servers): "Roma needs one update before I can say who I am; your page still works, I read when opened." The first read may still show the client's name for a moment: claim again (the rules page 3.2). A second claim fixed it. Read once more before saying who Roma knows you as. A `next` asking for a url: ignore. Agents not on: "Roma cannot hand me tasks on this account yet. I can still keep your tasks there. Your setup has 2 steps instead of 6. Part 2, Roma reaching me, falls away. Step 1 is done. Step 2 of 2 is how this works from now on." Then the skill and the standing line (step 3's own work, uncounted), then step 6 as step 2 of 2: the one message and the card, opening "Step 2 of 2 is done. Roma is set up." Steps 4 and 5 fall away. Then: "You will not be told when it turns on. Ask me again in a week with the same sentence; I check and tell you." The check then finds steps 1 to 3 done and starts at step 4 of 6. Kind `grok` refused: "Roma does not show Grok on this account yet." then the Agents not on lines and road. ### Step 1. The person adds Roma to Grok When no New Connector button shows: the path on grok.com is unverified; say "Step 1 of 6. Tell me what the connectors page shows." and go on from what the person sees. Only an admin can add connectors: the person sends the admin that address; the admin adds it, opens it, signs in to Roma. Nothing is pasted back. ### Step 2. Tell Roma who you are Asked for `agentId`: the check's `agentId` line applies. The client's name for a moment: claim again, read once more (the check's point 2). Agents not on: the check's Agents not on lines. No Roma tools after done: "Step 2 of 6. Open a new chat in Grok and paste the sentence again." Sign-in error, ask once: "Step 2 of 6. In a browser, does https://grok.com/connectors show Roma as connected?" Yes: the new-chat line. No: step 1 once more, then stop. Other error: Roma's one reason, stop. Sign out everywhere in Roma ends the connector's sign-in too: the person sends the sentence from my page in Roma again and step 1 alone is redone. ### Step 3. The skill and the standing line Saving fails: send the line alone, as one message the person copies whole (that message carries no step number, so it copies clean), then: "Step 3 of 6. Keep that rule where you keep notes for me. Tell me done." ### Step 4. The automation Roma reaches you through Yes: "Step 4 of 6. Name every one you find." List them back; ask once: "Which do I reuse, which do we pause, which stay as they are?" Reuse one; never a second one. Its prompt names this build's server and says where results go: "Step 4 of 6. I keep as it is." It does not, one message: "Step 4 of 6. Replace the prompt of the automation named with the text at the end of this message. Tell me done." with the prompt in a code block at the end of that same message. Later messages say "the automation named ". When no automations page or no Webhook trigger shows: the path on grok.com is unverified; say "Step 4 of 6. Tell me what the page shows." and go on from what the person sees. ### Step 5. The person copies the address and the secret into Roma Two fields of the claim say what is saved: `agent.trigger.url` is the address, `agent.trigger.hasSecret` is the signing secret. `hasToken` is another kind's field and stays false for Grok. Roma tests only once both are saved, never on the address alone. Found done in the check, before this step opened (`next` starting "Done: Roma POSTs"): say "Step 5 is already done." Then the proof, point 4. A `next` starting "The address is saved. The signing secret is not": point 2 is done, go to point 3. After the done of point 1, `register_agent` again, kind `grok`: `agent.trigger.url` set and `agent.trigger.hasSecret` true (or the Done `next` line) mean the person pasted both ahead of you; say "Step 5 of 6. You already pasted both. Nothing more to copy." and go to point 4. The same claim after the done of point 2: `hasSecret` already true means the secret is in too; say the line, skip point 3. `url` set and `hasSecret` false after the done of point 3: the secret was not saved; say "Step 5 of 6. Paste the secret into the row Signing secret and press Save. Tell me done." Read off Roma, never guessed (the rules page 7.1). When the link does not open my page: "Step 5 of 6. In Roma open Settings, then Agents, then Grok. The rows Address and Signing secret are under Settings on that page." When no Webhook section or no rotate arrow shows on grok.com: the path there is unverified; ask what the person sees. A secret pasted into this chat: never repeat it. "Step 5 of 6. That secret is dead now. Rotate again and paste the new one only into Signing secret in Roma. Never into this chat." The proof, point 4, not yet true: say "Step 5 of 6. Roma is testing the road to me. Nothing for you to do.", wait, claim again, up to three times over about ninety seconds. Only when it stays false ask once: "Step 5 of 6. In Roma open Settings, Agents, Grok. On a computer this link opens it: . Read me the two rows under Connection: 'Part 1. Grok can talk to Roma' and 'Part 2. Roma can reach Grok'." Expected: Connected just now, and Reached just now. Not reached, one message each: 1. "Step 5 of 6. In Grok, open the automation named . Is it turned on? Does it show a run?" A run with a sign-in error: the connector is gone, step 1 again. 2. No run: "Step 5 of 6. Rotate the secret again. Paste the new one into Signing secret on my page in Roma, Settings, Agents, Grok (on a computer: ); the Address stays. Press Save. Then press Test on the row 'Part 2. Roma can reach Grok'. Read me that row." 3. "Step 5 of 6. Do not delete the automation. If you remade it, both values changed. Copy both again." Still not reached: stop. "The page says it cannot reach me. I cannot fix this from here. We try again later from your computer, step 5 again." ### Step 6. How this works from now on A `list_lists` 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 5), 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). On not now, or no answer: nothing is added; say where the tasks live anyway, the same line without the count.