This is the Instinct help page of the Roma guide: what to do when a step of [https://roma.app/agents/instinct.md](https://roma.app/agents/instinct.md) fails. Read it only then.
## Instinct help
When a step of [the Instinct page](https://roma.app/agents/instinct.md) fails, the fix is here, by step.
### Step 1
Never 127.0.0.1, localhost or a port on your own machine as the return address: that is your machine, not the person's, their browser spins on it for ever and the code dies unused. Roma shows the Copy link card itself when nothing answers at your return address on the person's device; the address bar holds the same link.
Expired: "Step 1 of 6. That link expired. Here is a fresh one. Same steps." No Roma page opens from the link: send the link once more; still nothing, "If you cannot connect" below.
If you cannot connect: your account declines Roma's server or a sign-in: change nothing, say one line, "My account does not let me add Roma from here" or "My account does not let me stay signed in to Roma." Then only a road that exists: "I can still write your tasks into Roma when you paste its link to me", if that road exists for you; else "Nothing more I can do from here." No other servers, no invented road.
### Step 2
Key in Roma, none in your vault (`hasKey` true, no vault login): the message of step 2, item 1 with "On the Key row press Replace key, then Make a new key, then Copy." in place of Make a key. Cancel on "Make a new key for ?" only when the vault holds a working key. The vault link does not open: the person adds the login in the vault inside the Instinct app by hand; that screen path is not verified from the product, so name only what the screen shows.
Right after the message of step 2, item 1, before waiting, claim again: `hasKey` true and a Roma login already in your vault mean the person did this ahead of you. Say "Step 2 of 6. You already saved the key. Nothing more to copy." and go to the check; read it off the claim and your vault, never guess it.
`hasKey` and `keyMadeAt` both stand on the claim's answer under `agent`; `get_context`'s agent block does not carry them, so a missing field there is not "no key". `hasKey` not yet true: the page may still be saving; wait, claim again, up to three claims over about a minute. Only when it stays false ask once: "Step 2 of 6. Does the Key row read roma_… and Made, with a date? Yes or no."
Vault page closed before saving: the message of step 2, item 1 again, with "In Roma press Replace key, then Make a new key. The old one is dead. Copy the new one into the vault." A key pasted into this chat: never repeat it, say it is dead, send the message of step 2, item 1 again with Replace key.
Healing: on a sign-in error open a fresh approval link in your own browser, choose Use a Roma key, let the vault fill it, press Approve, read the code from the landing address. Say once: "My sign-in dropped. I signed in again with my saved key." Roma's Sign out everywhere ends your sign-in too; the key brings you back. No key in your vault when the sign-in drops: "My sign-in to Roma stopped and I have no saved key. Send me the sentence from my page in Roma again and we connect once more." A refused key: stop, no retries: "My key was refused. In Roma open Settings, Agents, Instinct. On a computer this link opens it: . On the Key row press Replace key, then Make a new key, press Copy. Open my vault link: . Put the key in the roma.app login in place of the old one. Tell me done."
### Step 3
`get_context`'s `agent` block: its `door` reads schedule on both roads: that word is your kind's, not a check of yours; the mail road is live once the claim answers `mailAddress` and `pingVia` reads mail. The first read may still show the client's name for a moment: claim again. A second claim fixed it.
### Step 4
An older Roma entry your memory cannot erase stays; the new one wins, say so in one line if you must, never ask the person to erase anything.
### Step 5
There is no message to copy on the page and no button named Copy for this step; the person brings your address to the page, nothing comes from the page to you.
No mail address of your own: "Step 5 of 6. I have no mail address of my own. Roma cannot reach me by mail." Then, right there, the backup offer below, as its own message with its card; then step 6.
Right after the message of step 5, item 1, before waiting, claim again. Two fields on the answer: `agent.emailAddress` fills the moment the person saves, `mailAddress` only once you opened the Confirm link (a saved, unconfirmed address is not absent). `emailAddress` already your address means the person pasted it ahead of you; say "Step 5 of 6. You already pasted it. Nothing more to copy." and go to step 5, item 2. Read it off the claim, never guess it; never ask the person for the address or `settingsUrl`. The same in the check: `mailAddress` null but the Address row on your page holds your address: go to step 5, item 2, no new paste.
Once the link is confirmed your record's `state` reads listening from then on, schedule before, both Roma's words for the same record.
`agent.canBeHandedWork` 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 claims over about ninety seconds; Roma's test mail comes by itself after the confirm, so never ask for Test before those three claims. Only when it stays false ask once: "Step 5 of 6. In Roma open Settings, Agents, Instinct. On a computer this link opens it: . Press **Test** on the row **Part 2. Roma can reach Instinct**. Roma mails me once, I read Roma once, the row shows it. Tell me done." Test is only this fallback. Then claim once more. True: the done line of step 5, item 3. Still false: say so once, "Step 5 of 6. Roma cannot reach me by mail yet. I go on." Then, right there, the backup offer below, as its own message with its card; then step 6.
**The backup when mail stays unproven: the routine Check Roma (once, made only on a yes).** A routine Check Roma is a backup, not a setup step: it finds work only every five minutes, you offer it once, only where mail stays unproven, and make it only on a yes (the rules page, 7.14). It is offered only on two roads: at the end of step 5, after the Test and the re-check, Roma still cannot reach you by mail (above); or you have no mail address of your own (above). The offer comes right there, as its own message with one card, then step 6 goes on. A proven mail door gets no offer at all. The Agents not on road has no backup. The setup is complete without it; no, or no answer, leaves it complete. Found in the check: kept as it is and named once: "You already have my 5-minute check of Roma. I keep it." It is never offered again. Never a second one.
1. One card where you have one, the question above it, three options (the rules page, 7.12): "Roma cannot reach me by mail yet. Until it can, I can check Roma myself every 5 minutes as a backup. Each check counts as a run on your plan, 288 a day, or 144 in the daytime only, from 8 in the morning to 8 in the evening. Want it? Yes, daytime only, or no." Daytime is the rules page's window, 8 to 20 in the person's time zone (5.3), twelve hours, 144 checks; never another number. Nothing is made before a yes.
2. On yes or daytime only: a routine named Check Roma, every 5 minutes, no end date; daytime only: the same, from 8 to 20 in the person's time zone only. Reuse one that exists; never a second one. Its instruction names the server explicitly: "Use only the Roma server named at ; no other Roma server." (two servers connected read the wrong one today; on staging copy the line from the block below). It says where results go: into the task's body in Roma with `update_items`, with its `message` on the same call; nothing is said in this chat unless the person is needed. Every run reads your work by the rules page's own-clock rule (5.3) and works by its work rules (6). Quiet when nothing needs doing. Say: "I set up my 5-minute check of Roma. I text you when its first run has read Roma." Do not wait; go on with the setup.
3. Check: its first real scheduled run has read Roma, and your own schedule reads no end date; the person reads nothing. That first run is the proof: `register_agent` with kind `instinct` again; `agent.canBeHandedWork` true means Roma reached you, and the row 'Part 2. Roma can reach Instinct' reads Reached just now. Say, with the number of whichever step is current, none after the close: "Step of 6. My check ran at