Grok Bot agent computer blocked by Cloudflare/hCaptcha on Suno; Create often silent-fails

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Where does the bug appear (feature/product)?
Something else… → Grok Bot (agent computer / shared cloud browser)

Related site: suno .com

Date: 2026-08-12

Describe the Bug
Trying to use Grok Bot’s shared computer to generate music on Suno (signed-in browser session; no official Suno connector/MCP). Bot walls keep blocking real work:

Cloudflare “Verify you are human” appears on suno .com/create (and also showed up on Cursor auth when trying to post this from the agent browser).
Even after I take over the agent computer, clear the challenge, and hand control back, Create often silent-fails: spinner / click, then nothing in Workspace, Library, or History — no toast, no credit error.
Worked around with an unofficial suno CLI using the browser session. Auth/credits work after patching billing JSON drift, but generation hits hCaptcha (Captcha required (version 2)). The CLI’s headless/offscreen Chrome solver fails with hcaptcha never finished loading on suno .com/create. So captcha is the final boss even outside pure UI clicking.

Steps to Reproduce

Open a Grok Bot → Agent Computer browser → https://suno. com/create
Sign in to a Suno account (Free plan in our case)
Enter a Simple-mode prompt, model v4.5-all, click Create
Observe Cloudflare “Verify you are human” → clear via takeover → return control
Retry Create (browser automation and/or desktop clicks)
Observe empty Workspace / Library / History with no error UI
(Optional) Auth unofficial CLI from the same Chrome profile → suno describe --model v4.5-all --wait → hCaptcha required → solver cannot load the widget on this environment

Expected Behavior

After I sign into Suno on the agent computer (and clear any CAPTCHA myself when needed), the Bot should be able to generate songs reliably — same as a normal personal browser — or at least fail with a clear error instead of a silent no-op.

Operating System

Windows 10/11

Version Information

Latest Grok

For AI issues: which model did you use?

Latest Grok

Additional Information

Impact
Sites behind Cloudflare/hCaptcha are exactly where “Bot has its own computer” should shine when there’s no MCP. Right now Suno is effectively unusable for autonomous generation from Grok Bot without repeated human challenge clears, and even then Create can no-op. Same class of bot-mitigation also blocked logging into the Cursor forum from the agent computer.

Environment
Grok Bot agent computer (Linux, Chrome, custom user-data-dir profile)
Suno Free plan (billing shows credits available; only v4.5-all usable)
Persistent signed-in suno .com session on the agent browser
No official Suno plugin/connector in the catalog
Also tried unofficial suno-cli 0.9.0 against the same session
Ask / feature requests
Detect Cloudflare / hCaptcha on the agent computer, pause cleanly for takeover, then resume with a fresh valid session (no silent Create no-ops).
Less bot-fingerprinted egress for the agent browser (or documented guidance when datacenter IPs will keep failing).
First-party connectors for high-value sites so Bots don’t have to fight bot walls for basic tasks.
When Create/API fails after a challenge, surface the real error in the Bot UI instead of failing silently.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Ekius

The Cloudflare/hCaptcha walls on Suno (and the Cursor login) are the site’s anti-bot layer reacting to the agent’s cloud browser, not anything you’ve misconfigured. Taking over to clear a challenge is the intended path, but on aggressive sites the clearance is tied to that session/network, so the site can keep re-flagging it, which is why Create sometimes goes through the motions and then silently does nothing. That silent no-op with no error is on us to fix, not on you.

For now, sites behind heavy anti-bot will stay unreliable for autonomous runs from the shared cloud browser even after a manual solve. Running the same task from your own signed-in browser avoids the wall entirely.

Your asks (pause cleanly for takeover, a less bot-flagged browser, first-party connectors, and surfacing the real error) are exactly the rough edges we’re tracking. I’ve made sure the team has this. No timeline to share, but I’ll post here if there’s an update.

7

I also must add: Amazing product! So useful. Exactly what I needed. But we need a solution for cloudflare. You can not pass it even manually. Since it is used by almost everyone nowdays, the computer feature is useless in its current state.