When a long Bot name blocks first setup

Initial Grok Bot setup can fail with “Grok Bot couldn’t finish setting up. Can’t reach your computer right now.” Settings may refuse to open, so Recover and Update stay unreachable. Curl to *.cursorvm.com can still return a response, and your phone hotspot can work the same way. Staff (kevinn, Sep 10, 2026) confirmed the Agent Computer was healthy on forum 171270. The last setup step — creating the first Bot — rejects a name longer than 255 characters and surfaces that rejection as a connection error.

Short name, then full instructions in chat

1. Quit Grok Bot completely (app menu → Quit, tray icon included on Windows).
2. Open Grok Bot and sign in so setup restarts.
3. On Create your first Bot, put a short name in the Name field (a few words, for example Assistant). Stay well under 255 characters.
4. Create the Bot.
5. Send the long brief as the first chat message. That is where instructions belong.

Staff said an update that caps the name automatically is on the way. Until then, keep the Name field short.

If a short name still fails

Reply on the forum thread with the short name you tried and your app version. Ask staff to dig further rather than looping Recover from a Settings screen that will not open.

Distinct from network can’t-reach

Generic unreachable Agent Computer steps live in Fix Grok Bot “Can’t reach your computer”. Use that path when the computer itself is offline. Use this page when setup fails at first-Bot create while the VM host still answers.

Pitfalls

• Pasting a full system prompt into the Name field during onboarding.
• Reinstall loops and hotspot tests when the real limit is name length.
• Waiting on a status-page Cloud Agents blip that staff already ruled unrelated.