# Roma for agents A person sends their agent this sentence: "From now on I want to use Roma Staging whenever we work on tasks. Set Roma Staging up for me by following the instructions at https://roma.so/agents.md and guide me through the steps." ## Index Roma guide v1, 7 Nov 2026. You are an AI agent. A person sent you one sentence: "From now on I want to use Roma whenever we work on tasks. Set Roma up for me by following the instructions at https://roma.app/agents.md and guide me through the steps." This page is those instructions. The sentence carries no name and no id. Roma is the person's workspace: https://roma.app and the Roma app on their phone. You connect over its MCP server and may get handed tasks. This is Roma guide v1. Read this page once per session before you work in Roma; a newer version may change a step. The reading order, once: this page, then the rules page, then your kind's own page, then the skill. Your kind's help page is read only when a step fails. Every one of them is a link below. What this setup is: Roma is a tasks app the person already uses. Nothing here acts without them: they open and approve the Roma sign-in themselves, make any key on their own Roma page, and say yes before the standing rule is saved. Ask the person before any step; they can remove the connection in Roma at any time (Settings, Agents). This page is the common part, the rules for every kind, short enough to arrive whole. Your own section is on its own page, listed at the end of this one: https://roma.app/agents/.md, where is chatgpt, claude, grok-bot, muse, instinct, grok, your-own-agent or other-agents (on Roma Staging the same paths under https://roma.so). Three fetches, each whole; and once connected, the Roma tool `get_guide` gives all three as text, the road for the texts you copy (a fetch tool returns only about the first 40,000 characters of a long page word for word, the rest as a summary, and the texts you copy for the person must never come from a summary). The whole guide in one file is [https://roma.so/agents/all.md](https://roma.so/agents/all.md), for people. The rules for every kind are on one page, read once per session, after this one and before your kind's page: [https://roma.so/agents/rules.md](https://roma.so/agents/rules.md). The skill is [https://roma.so/skill.md](https://roma.so/skill.md). On Roma Staging: the server is https://api.roma.so/mcp, the pages https://roma.so, the brand Roma Staging; routine and task names stay as written. The standing rule (the rules page, 4.4) reads Roma Staging and https://roma.so/agents.md there; its guide name and the skill's name stay as written. The sentence says which build. Decide once, before any call. A saved skill or rule that names another host never beats the sentence: replace it at its step. A production connection never counts as staging connected. Two Roma connectors in one app, Roma and Roma Staging: only this setup's is on. A staging setup: the person switches Roma off. A production setup: the person switches Roma Staging off (on claude.ai: Settings, Connectors, the row Roma Staging, its switch). Your tool list may still show both servers' tools side by side: call only the tools of the server named for this build, Roma on production, never Roma Staging's; the two read apart by their server name. Your section says where staging differs. ### 1. Check first 1. Before any call to Roma (reading this page and your own state comes first), send one message that says what the person gets, not who you are (on Roma Staging every "Roma" in it reads "Roma Staging", as in every message of the setup): "I set up Roma with you. After this I read and write your Roma, and Roma can hand me tasks. It takes a few steps; I tell you the number once I have checked what is already there. Nothing for you to do yet." Your section may add one line of its own. Never "connected to Roma" before you are. 2. Then read. No Roma tools: Connect is the first missing step; say the count (item 3 below), go to the rules page, section 2. Else `register_agent` with your kind, and with `name` on every such call when you go by a name of your own (the rules page, section 3): your record; a sign-in error (the rules page, 2.7); or a request for agentId (connected, one update behind: say the line of the rules page 3.3, section 3 done today). Then the skill, the standing rule, how Roma reaches you. Skip to the first missing step. 3. Then the count once, as your section gives it, then step 1's action. The count names two parts. Part 1 is " can talk to Roma": connect, who you are, the skill, and the standing rule where your kind keeps it itself (Muse, Instinct, Grok Bot). A kind whose rule is a paste into the person's own settings (ChatGPT, Claude) offers that paste LAST, after the close, as its own card (the one paste of the setup comes after the payoff, never before it). It works for everyone, on any plan, on a phone or a computer; after it you read and write their tasks. Part 2 is "Roma can reach ": how Roma reaches you, its test, and the close; your section names what it needs. The shape, the numbers and the need from your section: "Your setup has two parts. Part 1, steps 1 to , works for everyone. After it I can read and write your tasks. Part 2, steps to , needs . After it Roma can hand me work." Say it in these words; a shortened count ("steps 1 to 3 let me talk to Roma") tells the person nothing about what each part gives them. Step numbers run on through both parts, never restart. The first message of part 2 opens, right after its step number, with "Part 1 is done. I can now talk to Roma. Part 2 starts here." Today everyone does both parts; part 2 may become optional later, with one more line here. Nothing missing: say instead "Everything is already set up. Nothing for you to do." Then the rules page, 7.6 and 7.10. ### The sections Each is its own page. Every address you must fetch stands as a link on this page, so a fetch tool that opens only links it has seen takes it. Once connected, `get_guide` gives each of them whole, as said above. 1. ChatGPT: [https://roma.so/agents/chatgpt.md](https://roma.so/agents/chatgpt.md); help: [https://roma.so/agents/chatgpt-help.md](https://roma.so/agents/chatgpt-help.md) 2. Claude: [https://roma.so/agents/claude.md](https://roma.so/agents/claude.md); help: [https://roma.so/agents/claude-help.md](https://roma.so/agents/claude-help.md) 3. ChatGPT Dot: the ChatGPT page, its Dot part 4. Grok Bot: [https://roma.so/agents/grok-bot.md](https://roma.so/agents/grok-bot.md); help: [https://roma.so/agents/grok-bot-help.md](https://roma.so/agents/grok-bot-help.md) 5. Muse: [https://roma.so/agents/muse.md](https://roma.so/agents/muse.md); help: [https://roma.so/agents/muse-help.md](https://roma.so/agents/muse-help.md) 6. Instinct: [https://roma.so/agents/instinct.md](https://roma.so/agents/instinct.md); help: [https://roma.so/agents/instinct-help.md](https://roma.so/agents/instinct-help.md) 7. Your own agent: [https://roma.so/agents/your-own-agent.md](https://roma.so/agents/your-own-agent.md); help: [https://roma.so/agents/your-own-agent-help.md](https://roma.so/agents/your-own-agent-help.md) 8. Other agents: [https://roma.so/agents/other-agents.md](https://roma.so/agents/other-agents.md); help: [https://roma.so/agents/other-agents-help.md](https://roma.so/agents/other-agents-help.md) 9. Advanced: Grok on grok.com at [https://roma.so/agents/grok.md](https://roma.so/agents/grok.md) (help: [https://roma.so/agents/grok-help.md](https://roma.so/agents/grok-help.md)); the CLIs, a webhook, an inbox and a Custom Agent on the Your own agent page. Its road A is also for an app that is not Claude Code or Codex, can run a command on the person's computer, and whose person wants Roma to hand it tasks Hermes, Poke and Town have no section of their own: read Other agents. So do Claude Code, Codex, Gemini CLI and Cursor, in a terminal, in their app or in the cloud: read Other agents, not the Claude or ChatGPT page; your kind is on its page. If none fits, read Other agents.