Engineering
Keep a spare model for when Cursor and Grok Bot go down together
One supplier means one outage takes IDE, Cloud Agents, and Grok Bot at once.
What hurt
Robert Reed (@Oldhandai) felt a joint Cursor/Grok Bot outage. Tip: keep a spare second model or local one, and paste a recovery prompt that lists where you stopped, the next three steps without the main tool, and what to save so you can resume. Not affiliated with xAI.
What to install or create
Tip only. Save his recovery prompt in a note. Keep a second chat or local model ready.
Bots
No new bot. Follow the first-run steps.
Plugins
None on day one. Follow the first-run steps.
Files
outage-note.md. Spare model name + the resume prompt.
Routines
None on the first run. Watch one manual pass first.
The prompt
Outage resume (author-quoted)
Quoted from @Oldhandai — as published. Do not invent a second system prompt.
My main AI tool is down. Here is where I stopped: [paste last task]. Give me the next 3 steps I can do without it, and what to save so I can pick up fast when it's back.
First run
- 1Read https://x.com/Oldhandai/status/2109809188646133763 (credit @Oldhandai).
- 2Pick a spare: second vendor chat or a local model.
- 3Save his resume prompt with a blank [paste last task] slot.
- 4On outage: paste last task into the spare and follow the three steps.
- 5When main tools return, resume from what you saved.
Approval fence
No spend or post required — recovery planning only.
What to tweak
Steal the spare + resume prompt. Dual-vendor before you need it.
Source
Robert Reed | Old Hand AI @Oldhandai · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.