Grok Bot: Wrangler/box auth reminder stays stuck after auth already succeeded via another path

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

While deploying a Worker from Grok Bot, Wrangler OAuth on the agent computer failed partway (localhost callback / “this site can’t be reached”). I asked the Bot in chat; it recovered by fixing the callback path and completed login successfully, then deployed.

After that, the UI still showed the pending authorization / box-help reminder on the right side and in the conversation, as if I still needed to authorize. The real state was already “logged in / done,” but the reminder never cleared or marked complete. That feels unintelligent: the UI is not synced to the actual auth result.

Steps to Reproduce

  1. Ask Grok Bot to deploy with Wrangler on its computer.
  2. Hit a failed OAuth callback (localhost can’t be reached) or otherwise fail the first handoff.
  3. Resolve auth in chat with the Bot (retry / alternate path) until Wrangler reports successfully logged in.
  4. Observe that the sidebar/right reminder and in-chat auth prompt remain.

Expected Behavior

When auth succeeds—whether via the original card, a retry, or the Bot completing login another way—pending reminders should auto-dismiss or show “completed,” and stop asking me to authorize again.

Screenshots / Screen Recordings

PixPin_2026-08-31_17-33-06.png
PixPin_2026-08-31_17-33-06.png390×369 26.5 KB
PixPin_2026-08-31_17-33-19.png
PixPin_2026-08-31_17-33-19.png923×762 99 KB

Operating System

Windows 10/11

Version Information

版本：0.30.0
发布通道：stable
操作系统：win32

Additional Information

Platform: Grok Bot desktop
Auth target: Cloudflare Wrangler OAuth on the Bot’s computer
Outcome after recovery: deploy succeeded; only the UI reminder stayed stale
Severity: UX/state sync bug; not a hard blocker once you know to ignore it, but it erodes trust

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @guyu, thanks for the report, and glad the deploy itself went through.

When the agent asks for your help on its computer, that reminder only clears when you respond to it directly. It does not yet notice that the login was completed another way, even when the agent recovered on its own.

Clicking “I’m done, continue” (or “Skip this step”) on the reminder card will dismiss it and let things proceed normally. Sending the agent any chat message also clears the “Waiting for you” state in the sidebar.

We’ll continue to work on making this feel more natural and in sync.