This is the ChatGPT help page of the Roma guide: what to do when a step of [https://roma.app/agents/chatgpt.md](https://roma.app/agents/chatgpt.md) fails. Read it only then.
## ChatGPT help
When a step of [the ChatGPT page](https://roma.app/agents/chatgpt.md) fails, the fix is here, by step.
### The check
No subscribe tool in this chat (the Mac app with Local, the iPhone app, the Mac app's Set up Roma chat): never retry the subscribe here; the hand-over of the check, one message with https://chatgpt.com/work. Such a chat does part 1 (steps 1 and 2) and hands part 2 over: after step 2, one message, "Part 1 is done. I can now talk to Roma. Part 2, Roma reaching me, needs a Work chat on chatgpt.com in your browser; this chat cannot listen for Roma. 1. Open https://chatgpt.com/work in your browser, on your computer or your phone. 2. Start a new chat. 3. Paste this into it and send it:" then the setup message in a code block: `Help me set up @Roma with the $roma skill`; then one line: "In the ChatGPT app on a Mac a new Work chat with **Cloud** selected works too." Then stop; the new chat reads the ChatGPT page itself and finds steps 1 and 2 done. The browser is named first on purpose: it is the one road that is the same on a computer and a phone. In a chat without the subscribe tool add to the count: "This chat cannot do part 2; after part 1 I send you to the right place with one message."
The phone's ChatGPT app has a Work tab, but its Work chat has no tool to listen for Roma's events; chatgpt.com in the phone's browser has it and does part 2. So in the phone app do part 1 (steps 1 and 2) and hand part 2 over once with the hand-over message of the check; after it, part 2 holds everywhere, since the listening lives in the cloud. No Work tab anywhere on the account: "Then Roma works from this chat only when you pick it with @, and Roma cannot reach ChatGPT on this account yet." Steps 2 and 4 still run where Roma is picked.
In a regular chat, one message and nothing else: "Roma works from a Work chat, a different kind of chat in ChatGPT. 1. On the ChatGPT home switch the tab from **Chat** to **Work**. 2. Start a new chat. 3. Paste this into it and send it:" then the sentence the person sent you, word for word, in a code block (the person sends the same sentence again and the new chat starts from the top; nobody picks anything). This chat ends there; nothing moves to the new one, and the new chat reads the ChatGPT page itself. The person insists on a regular chat: part 1 works there (the pick, the claim, the line), part 2 does not: say "Roma can read and write your tasks from here. For Roma to hand me work, we need a Work chat; this chat has no way to listen for Roma." and stop after step 2 with the close of step 4 without its Delegate bullet, then the offer of the line.
The Set up Roma chat stays at "Thinking": "Close this chat. Open https://chatgpt.com/plugins/plugin_asdk_app_6abdc72bf1d08191bd7e6a8c4c1f0526?no_universal_links=1 and press Set up Roma again, or open https://chatgpt.com/work and paste the sentence."
If `register_agent` is missing or asks for `agentId`: "Roma needs one update before I can say who I am; your page still works, I read when opened." Step 2 then waits for Roma's update.
If the claim says agents are not on for this account, say its line as it is, then: "Roma cannot hand me tasks on this account yet. I can still keep your tasks there." Step 3 falls away. The count then: "Your setup has 3 steps instead of 4. Part 2, Roma reaching me, falls away: step 3 falls away; step 4 comes after step 2."
Read A is only for when the claim could not answer: "In Roma open Settings, Agents, ChatGPT. On a computer this link opens it: . Under Connection read me the two rows, Part 1 and Part 2. One says whether ChatGPT can talk to Roma, the other whether Roma can reach ChatGPT. Tell me done." Part 2 reading Reached means step 3 is done.
### Step 1
The link does not open: "Step 1 of 4. In ChatGPT open Settings, Plugins. Find Roma in the list and press Add. Tell me done." (the list's own labels past Settings, Plugins are not verified on the product; if one differs, ask what the person sees).
No sign-in page: "Step 1 of 4. In ChatGPT open Settings, Plugins, Roma. Tell me whether it reads Connected." Not connected: press Connect, then this message again.
Roma's tools missing from your tool list after the install: "Step 1 of 4. In the message box type @ and pick **Roma**. Tell me done." (on staging **Roma Staging**; two Roma rows mean a production and a staging plugin both installed, and the row's name tells them apart). Still missing after the pick: "Step 1 of 4. 1. Open **Settings**. 2. Press **Plugins**. 3. Press **Roma**. 4. Press **Manage**. 5. Press **Refresh tools**. Tell me done."
The plugin shows fewer tools than the ChatGPT page names (no `register_agent`, no `get_guide`): the plugin's tool list has not refreshed; say so in one line, do part 1 with what is there, and ask the person to remove and install the plugin once more, or to come back in an hour.
A different or empty Roma in `get_context`: "In ChatGPT open Settings, Plugins, Roma, Connected accounts. Check it is the account you use in the Roma app." Never switch to another Roma server.
A sign-in error: change nothing. Once: "In ChatGPT open Settings, Plugins, Roma, and connect it again. Sign in with the account you use in the Roma app. Press Approve. Then start a new Work chat with Roma and send me the sentence from my page in Roma again." Then Check first there.
On Roma Staging, no Add custom MCP server: ask what the person sees and stop: "Roma Staging cannot be added from this account yet." Still missing after the pick, and only then: "Step 1 of 4. 1. Open **Settings**. 2. Press **Plugins**. 3. Press **Roma Staging**. 4. Press **Manage**. 5. Press **Refresh tools**. Tell me done." The same order as step 1's message 3: the pick first, Refresh tools second. With the production Roma installed too, the chat may use production's tools: read the server's address off the first call, and when it is not this build's, the @ pick of **Roma Staging**.
### Step 2
The plugin carries the Roma skill; if not loaded, read [https://roma.app/skill.md](https://roma.app/skill.md) and say so once.
The first read may still show the client's name (Cursor) for a moment: claim again. A second claim fixed it.
### Step 3
Reached, but this chat holds no listening (an earlier Work chat's): the record's facts are per record, not per chat; add this chat's listening as the ChatGPT page's step 3 says, and the earlier chat's goes with that chat.
A Work chat that already listens for Roma is recognised by what it listens to (a Roma delivery from this build's server), not by the word Roma in its title; name every one you found and ask once which to reuse, pause or leave. An earlier listening whose record is gone or that Roma never reached (the claim's `canBeHandedWork` false) is dead: pause it and set up here, and say so in one line, no question. Only a live one that Roma reached gets the one question: keep it, or move the listening here.
Roma not yet reached after the test: wait, claim again, up to three times over about ninety seconds. Only when it stays false, the person's one read and the Test: "Step 3 of 4. In Roma open Settings, Agents, ChatGPT. On a computer this link opens it: . Under Connection press **Test** on the row 'Part 2. Roma can reach ChatGPT'. Tell me done." Then claim once more. Reached: step 4. Still not: stop. Say: "The page says it cannot reach me. I cannot fix this from here. We try step 3 again later."
If this chat cannot listen to the plugin's events (the events tools are missing: a local Work chat, see the check), change nothing and hand over: "Step 3 of 4. Part 1 is done. I can now talk to Roma. Part 2, Roma reaching me, needs a Work chat that runs in the cloud. 1. On the ChatGPT home switch the tab to **Work**. 2. Start a new chat. 3. In the ChatGPT app, make sure **Cloud** is selected, not **Local**. 4. Paste this into it and send it:" then the setup message in a code block: `Help me set up @Roma with the $roma skill`. Then stop; the new chat reads the ChatGPT page itself and finds steps 1 and 2 done. A cloud Work chat that still cannot listen: "Step 3 of 4. This chat cannot let Roma reach me. You can still keep your tasks in Roma." Add that on Roma's page the row 'Part 2. Roma can reach ChatGPT' keeps reading In progress, and stop. The model is the chat's; Roma cannot set it.
Proven end to end on staging, 24 October and 8 November 2026 (the second in a Work chat, Test pressed by hand before Roma sent its test by itself). Promise nothing beyond that. Never a task the person makes to test, and the person reads nothing while things work.
### Step 4
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`, not this read. If not named, say nothing of it and read once more a few seconds later; never ask the person to open a task's Delegate menu and look, and never call it inconsistent to them.
Agents not on (step 3 fell away): step 4 comes right after step 2, with the same message and card. After the card, as its own line: "You will not be told when it turns on. Ask me again in a week; send me the sentence from my page in Roma again. I check and tell you."
### The Dot
You are the Dot, the sentence arrived, and you have no Roma tools (the plugin was never installed, or Roma is not on in your settings): ONE message, then stop: "Roma is not in my tools yet. The Roma plugin must be installed first. 1. Open this link in your browser and press **Install**: https://chatgpt.com/plugins/plugin_asdk_app_6abdc72bf1d08191bd7e6a8c4c1f0526?no_universal_links=1 2. Turn Roma on in my settings in ChatGPT. 3. Send me the sentence again." Never the @ pick, never a custom server; a Dot has neither.
For the person: "If the ChatGPT Dot stops answering, open its page in Roma, Settings, Agents, . The row 'Part 2. Roma can reach ' shows when Roma last reached it. If that is old, send the Dot the sentence again."
### Any step
Ask only if you cannot tell whether you are ChatGPT in a chat or a Dot: "Are you talking to me in a normal ChatGPT chat?"
ChatGPT may ask before a tool changes something in Roma: the person allows it; a remembered choice holds only in that conversation. Say so once when it happens, not before. Answer what the chat offers.
This chat calls itself Codex or names its tools codex_apps: you are ChatGPT in a Work chat; follow the ChatGPT page, write no Codex file.
ChatGPT's own rules when Roma reaches you: a Dot and ChatGPT share one sign-in, so both pass `agentName` with their own record's name on every `update_items` and `post_chat_message`. Without it Roma files the work under the task's delegate, else under the one Roma rang last, else under ChatGPT. The saved listening instruction carries the sentence (the page, step 3, item 3). A listening saved before it did: add the sentence to its instruction.
For the person: "Roma reaches ChatGPT when you open a task in Roma, tap Delegate and pick ChatGPT, or reply to its message. On my page in Roma, Settings, Agents, ChatGPT, the row 'Part 2. Roma can reach ChatGPT', shows when Roma last reached me. If that stops, do step 3 again."