This is the Claude help page of the Roma guide: what to do when a step of [https://roma.app/agents/claude.md](https://roma.app/agents/claude.md) fails. Read it only then. ## Claude help When a step of [the Claude page](https://roma.app/agents/claude.md) fails, the fix is here, by step. Said during a step, each message opens with that step's number. The paths below were read on claude.ai and in Cowork on 8 Nov 2026; a path marked unverified has not been read from the product since. ### The check first Two Roma connectors installed, Roma and Roma Staging: step 1 says which one the person switches off; call only the tools of this setup's server, told apart by its name. The page did not open for you (the rules page 1.6): a copy the person pasted or attached counts; say so once. Asked for `agentId`: say "Roma needs one update before I can say who I am; your page still works, I read when opened." Only when the claim cannot say: the two rows under Connection on Claude's page in Roma, Part 1 and Part 2 (whether Claude can talk to Roma, and whether Roma can reach Claude). Only when the claim shows a door: in Cowork list the scheduled tasks and read their text; otherwise ask once: "Open https://claude.ai/code/routines. Is there a task whose text names Roma and the server ? Read me its name." Name every one found and ask once which to reuse, pause or leave. One to reuse with `agent.trigger.hasToken` true: only the address is missing; the step 4 part of the one message of steps 2 to 4 (Copy beside API, the row Fire URL). One to reuse with `agent.trigger.hasToken` false: its code is gone, the window showed it once; rule 3, a new task. None: the one message of steps 2 to 4. The first read after a claim may still show the client's name for a moment. A second claim fixed it. Read once more before saying who Roma knows you as. ### Step 1 No Add custom connector: a Team or Enterprise plan. There the connector is the organisation's, added once by an admin under Organization settings, Connectors; the member only connects to it. Say so in one line and send the reconnect list. Both a production Roma connector and the staging one installed: only this setup's is on. A staging setup: Roma Staging on, Roma off. A production setup: Roma on, Roma Staging off, by the person: "Step 1 of 5. Two Roma connectors are installed; this setup uses the one named Roma. 1. Press your initials, then **Settings**. 2. Press **Connectors**. 3. Switch the row **Roma Staging** off. Tell me done." Two servers connected read the wrong one; both servers' tools in your list: call only Roma's. Never switch to another Roma server. The Settings list is the fallback where the card cannot be brought up. No Roma tools in the chat: the Cowork reload below, under Step 1; the step's message says nothing about reloading. Roma not in this chat, one message: "Step 1 of 5. Roma is not switched on in this chat. 1. Press the plus menu. 2. Press **Connectors**. 3. Switch Roma on. Tell me done." The Roma page does not open after Connect, one message: "Step 1 of 5. 1. On claude.ai press your initials. 2. Press **Settings**. 3. Press **Connectors**. 4. Find Roma in the list. 5. Press **Connect** on its row. 6. Sign in and press **Approve** on the Roma page. Tell me done." No Connect on the directory page: a work plan, the admin line above. In Cowork the tools of a connector just connected may not reach the running chat. One message: "Step 1 of 5. Roma is connected, but its tools have not reached this chat yet. Reload this chat: in the menu bar press **View**, then **Reload**. Tell me done." Then refresh your tools and claim. Still none: a new chat with the connector switched on and the sentence sent again; say so in one line. ### Steps 2 to 4 Rule 3, the long code: A code pasted here: never repeat it. Say, with the current step's number first: "That code is in this chat now, so it is dead for us. Delete the task Listen to Roma and we redo step 2. On Claude's page in Roma the row Token then shows dots and Replace token: press Replace token and paste the new code there." No New task, or Claude says the plan has no scheduled tasks: "Roma cannot hand me tasks on this plan yet. I can still keep your tasks there." Treat the setup as 2 steps: step 1, then the close as step 2 of 2, then the offer of the line. On the phone the New task form has no API trigger. So steps 2 to 4 are on a computer; say so in one line when the person is on the phone there, and wait. The window closed before the copy: the address message of step 4; the code is gone then, the window showed it once: rule 3, a new task, and Replace token on the row Token. The task window does not open, one message: "Step 2 of 5. 1. On claude.ai press **Code** in the left menu. 2. Press **Routines** at the top. 3. Press **New task**. Tell me done." (unverified: the left menu and the Routines tab have not been read from the product; the address https://claude.ai/code/routines has). Step 3, after the check: `hasToken` false with the address saved: the code was not saved. Say "Step 3 of 5. Paste the code into the row Token and press Save again. Tell me done." Only when it stays false ask, with the step's number first, whether the row Token shows dots. Window closed before the copy: rule 3, a new task. Dots from an earlier try: "Step 3 of 5. Press Replace token first, then paste. Tell me done." Step 4: `agent.trigger.url` set on the claim means it is saved; not set: "Step 4 of 5. Open the task at https://claude.ai/code/routines. Under **Trigger** press **Copy** beside **API**. Paste it into the row **Fire URL** on my page in Roma: . Press **Save**. Tell me done." The test of step 4: Only when it stays false ask once: "Step 4 of 5. On my page in Roma, read me the two rows under Connection. 'Part 1. Claude can talk to Roma' should read Connected just now. Part 2 should read Reached just now." Not reached: "Step 4 of 5. Press Test on the row 'Part 2. Roma can reach Claude'. Tell me done." Then claim again and read `agent.canBeHandedWork` once more. In Cowork a sign-in error right here: the reconnect under Any step on this page, then Test again. Still not reached: stop. Say: "Step 4 of 5. The page says it cannot reach me. I cannot fix this from here. We try again later from your computer, step 4 again." ### Step 5 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 (the rules page 7.6). ### The line A fetch that refuses the address: `get_guide` with part "skill" once connected (the rules page 4.1); never say you follow this page's rules instead. No skill file on claude.ai or in Cowork: the short form of the rules page 4.2, the link plus the standing block, is the whole skill; keep its rules in memory and say so in one line, at once. ### Any step No card possible: a numbered list and the number, or the word. A wrong Roma, a sign-in error, or the connector reads failed, one message: "1. Open **Customize**. 2. Press **Connectors**. 3. Press the row of the Roma connector. 4. Press **Disconnect**, then **Connect**. 5. Sign in and press **Approve** on the Roma page. Tell me done." Then claim again. Roma's Sign out ends only that device; Sign out everywhere ends Claude's sign-in too: then Disconnect and Connect, and "Send me the sentence from my page in Roma again and we redo step 1 only." Cleaning up. A scheduled task made through the API cannot be deleted or switched off by you. The person deletes it at https://claude.ai/code/routines/; say the id from your task list. A connector on an organisation plan is never removed by the person; it is disconnected, or left installed.