This is the Other agents help page of the Roma guide: what to do when a step of [https://roma.app/agents/other-agents.md](https://roma.app/agents/other-agents.md) fails. Read it only then. ## Other agents help When a step of [the Other agents page](https://roma.app/agents/other-agents.md) fails, the fix is here, by step. ### The check 1. A Roma entry in your app is recognised by its address (this build's server), not by the word Roma in its name; two entries (Roma and Roma Staging): name both, use only the one build's, say which, never both. ### Step 1. Connect, and tell Roma who you are 1. Cannot add it yourself: one message, the clicks as a numbered list, the address alone in a code block at its end: "Step 1 of 2. This step connects to Roma. 1. On your computer open https://roma.app/agents/other. 2. Follow the first step for : add Roma with the address below. 3. Sign in when it asks and press Approve. Tell me done." 2. No sign-in page: name the command to run again; a pop-up blocker or Safari is the usual cause. No browser on that computer: these apps need one once, except OpenClaw: "Step 1 of 2: open the link I show on your phone, sign in, press Approve. The page shows a short code. Send me only that code; it works once and dies in minutes. I never repeat it." Then `openclaw mcp login roma --code `. 3. In the cloud with no return address of your own, the landing address is the last resort: "Step 1 of 2. After Approve the page looks broken. That is expected. Its address carries a one-time sign-in code. It dies in ten minutes. Copy the whole address from the address bar and paste it here. I use it once and never repeat it." Never repeat it, never store it. 4. A sign-in error: once (the rules page 2.7), one retry. 5. Tool missing, or it asks for `agentId`: "Step 1 of 2. Roma needs one update before I can say who I am. Your page still works. I read when opened." Go on to step 2. No claim: send the person nowhere; the `get_context` read is the check. A refusal that names the person's agents and gives a question is not this case: the rules page 3.3. 6. Codex through the plugin: no claim. The plugin signs in as ChatGPT. Roma files your calls under the person's ChatGPT record. That record is not you, and you have no page and no link of your own. Step 1, item 5 of the page gives your sentence; step 2, items 2 and 3 give your line on handing you work. Your Codex record, the one Roma hands tasks to, is made by the Roma Bridge pairing of part 2 (the page, part 2, item 6). `get_guide` reads your kind off that ChatGPT record and answers the ChatGPT page: pass `kind: "codex"` on every `get_guide` call. 7. The first read may still show the client's name for a moment (Claude Code reading Cursor): claim again. A second claim fixed it. Read once more before saying who Roma knows you as. 8. Codex added by hand, and `codex mcp add` ended with "timed out waiting for OAuth callback": the server is added, only the sign-in is missing. `codex mcp login ` opens the sign-in again. Never add the server a second time. The person pastes a link ("Codex did not open. Copy the link and paste it into Codex." on Roma's page): they approved after the wait ran out. You cannot use the link. Run the login again and say: "Step 1 of 2. That page came too late. I open the sign-in page again. Press Approve there." 9. Claude Code or Codex added the server by hand and Roma's tools are not there after the sign-in: the session started before the server was added. "Step 1 of 2. Close and start it again. Then send me the sentence again." 10. Step 1's command cannot run or cannot reach Roma, or step 2's file cannot be written, and you may not ask for more access (a Codex session whose sandbox has no network and whose approval policy is never): do not try again, and write no script and no workaround file. Say only "I need full access for this setup. Type /permissions and choose Full Access, then tell me to continue." and stop. On "continue" go on where you stopped. ### Step 2. Keep the skill and the standing line 1. Only where you cannot: ONE message, the clicks as a numbered list, the block (the rules page 4.4) in a code block at its end: "Step 2 of 2. This step saves the setting that makes me use Roma on my own. 1. Open Cursor Settings. 2. Open Rules. 3. Open User Rules. 4. Add a new one; do not edit one that is there. 5. Paste the text below into it and save. Tell me done." Then ask for its first words read back. 2. The claim answered with a record and agents are on: read `list_lists` once; the Tasks list's `delegates` names your record once Roma reached you (Codex through the plugin has no record of its own until part 2's pairing made its Codex record), and a read made before the proof may not name you yet; read once more after the claim reads true. ### Part 2. Roma can reach you: Roma Bridge, or Roma for Mac (Claude Code and Codex only) 1. No `npx` on that computer (Node is missing): skip the part and say so. `npx -y roma-bridge` answers 404 or "not found" from npm: Roma Bridge is not published for this build yet. Do not try other package names, and install nothing else. Say: "Part 2. I cannot set this up today. Roma Bridge is not available to install yet. Nothing is wrong on your side. I can still read and write your tasks. Say part 2 again later." The person has Roma for Mac: Roma Bridge is inside it and needs no `npx`. Say instead: "Part 2. Open Roma for Mac. Open Settings, Agents, Roma Bridge. Press Install Roma Bridge. Tell me done." Then the check (the page, part 2, item 5). The command ends with "This Roma Bridge is too old to connect": an old copy ran. Run the same line with `npx -y roma-bridge@latest` in place of `npx -y roma-bridge`. 2. The browser did not open: the command printed a line starting Open; open that link yourself (`open ''` on macOS), then send that link, whole, with its `at=` part: "Part 2. Open this link in a browser on this computer: . It does not work on a phone or on another computer." The page asks for a sign-in first when the person is signed out. The page reads "Open this on your computer" and has no Approve: it was opened on another device, or without the link's `at=` part. Send the link again with the same sentence. 3. The page shows another code than yours: "Press Deny. That page is not mine." Then run the command again. The code ran out (ten minutes), or the person pressed Deny: the command ends with the reason; say it in one line and offer once to run it again. The command ends with "Roma cannot hand work to an agent on your computer yet. Nothing was connected.": the Roma account signed in in that browser cannot use this yet. Do not run it again. Say: "Part 2. The Roma account in your browser cannot use this yet. I am connected to . If the browser shows another account, sign in to Roma as there. Then say part 2 again." 4. The page is titled "Connect again" and reads "Roma Bridge on this computer gets new access. The old one stops working.": Roma Bridge already holds your record (Roma for Mac, or an earlier pairing). The claim reads `agent.canBeHandedWork` true (Roma reaches it; `npx -y roma-bridge status` does not see Roma for Mac's): "Press Deny. Roma Bridge is already set up." Then the check (item 5). It is gone, on another computer, or Roma refuses it: "Press Approve. This connects me again." The old access works until the new one is connected, then stops. The page asks "Is this one of these agents?" and you are not among them: "Pick Add it as a new agent." The new agent is the one Roma Bridge runs; say its name from the command's closing lines. Codex through the plugin has no agent of its own, so the page lists the person's other Codex agents. One is listed: "Pick . That is the Codex you already have in Roma." Several: ask which one runs on this computer. The person says none of them is this Codex: "Pick Add it as a new agent." The command ends with "the Roma account approved, not . Nothing was connected": the browser is signed in to another Roma account than yours. "Part 2. Your browser is signed in to Roma as . I am connected to . Sign in to Roma as in that browser. Then tell me done." Then run the command again. The person pressed No on "Connect this computer?": nothing was connected; ask which Roma account is theirs before you run it again. 5. Not a Mac, or the closing lines say Roma Bridge could not be set to start at login: the closing lines say "Roma Bridge is running now, in this window. It stops when you close the window." The command does not end after them: it is Roma Bridge from then on. Do not wait for it to end, and do not stop it. It runs inside your session, so it stops when your session ends. Say so, and give the person the line it printed under "To start it again later:" to run in a terminal window of their own (the page, part 2, item 4). 6. Still `schedule` in `get_context`: the pairing did not finish; read the command's last lines. Codex through the plugin reads `list_agents` instead (the page, part 2, item 6): no Codex record whose `reach.id` reads `helper` means the same. 7. The claim reads `agent.offline` true: Roma reached Roma Bridge before and it is not running now. Not a new pairing: `npx -y roma-bridge status` on `agent.computer`, then `npx -y roma-bridge install` (a Mac) or the start line the pairing printed. `agent.helper.source` reads `macApp`: neither command sees that Roma Bridge; say "Open Roma for Mac on . It starts Roma Bridge again." Say: "Roma Bridge on is not running. I start it again." Otherwise not yet: wait, claim again, up to three times over about ninety seconds, saying "Roma is testing the road to me. Nothing for you to do." Only when it stays false: `npx -y roma-bridge status`, then "In Roma open Settings, Agents, . On a computer this link opens it: . Read me the two rows under Connection: 'Part 1. Claude Code can talk to Roma' and 'Part 2. Roma can reach Claude Code'." Not reached: "Press Test on that row." Codex through the plugin: `list_agents` in place of every claim here, and "In Roma open Settings, Agents, ." in place of the link. 8. The command cannot run, or cannot reach Roma, and you may not ask for more access (a Codex session whose sandbox has no network and whose approval policy is never): do not try again, and write no script and no workaround file. Say only "I need full access for this setup. Type /permissions and choose Full Access, then tell me to continue." and stop. On "continue" go on where you stopped. 9. The person said done and the command is gone with no closing lines: it was stopped before the approval reached it. `npx -y roma-bridge status` says whether Roma Bridge is connected. Not connected: run the pairing again, this time so it keeps running after your turn ends, and say: "Part 2. That did not finish. I start it again. The Roma page shows a new code." 10. You run over SSH, in a container, or on a computer with no browser: the pairing cannot finish there. The approval must come from a browser on the computer Roma Bridge runs on. A link opened anywhere else connects nothing. Do not start it. Say: "Part 2. I cannot set this up from here. The Roma page must open in a browser on the computer I run on. Sit at that computer, open me there and say part 2. Roma is set up for talking to me." The command ends with "the pairing was approved, but not in a browser on this computer": the same cause. Say: "Part 2. Nothing was connected. You approved in a browser on another device. The page must be open on this computer. I start it again." Run it again once.