Waiting
Grok Bot stuck waiting for login
Grok Bot stuck waiting for login means the bot is on a page that wants a human. Open the computer and take over that step. Do not paste the password or the verification code into chat.
A bot cannot start a second computer-use task on the same screen until the current one finishes or you redirect it.
Why the native method fails
The native method is to Reset, or to type the password into the transcript, because the bot has stopped talking. Official troubleshooting treats a stuck bot as a status check: read the sidebar and the conversation, open the computer, and look for a question, an approval, a login, a CAPTCHA, or a secret request. Send a short redirect if the approach is wrong. Send Stop now if the work should end. None of that is a computer rebuild.
Staff add a sentence you can use when takeover never appears: ask the bot to hand you the computer. For a passkey prompt, use Try another way rather than fighting the passkey on a machine that does not have your device. The cloud computer cannot complete a passkey that lives on your phone unless you are the one holding that phone.
Steps
- Open Agent Computer from the chat and see whether the bot is waiting on a page. If it is a login, take over, sign in yourself, finish two-factor or the CAPTCHA, confirm the signed-in page has loaded, return control, and tell the bot to continue from that page.
- Do not paste a password or a one-time code into ordinary chat. When a connector shows a secrets card, fill it there. Values are masked, stay out of the conversation, and are not shown to the model.
- Some sites expire the session or ask again on every sensitive action. Official troubleshooting says that cannot always be avoided. Have the bot stop and notify you instead of bypassing the check.
- A reminder that says the bot is waiting for help on its computer, after you already finished login another way, clears only when you answer that card or send any chat message. Staff say it does not auto-dismiss. Clicking around the computer without answering the card leaves the reminder up.
- If the computer itself says Reconnecting, the bot cannot finish the turn no matter how you redirect it. That is the can't-reach page. If every bot is silent and the computer view is fine, that is usage. This page is the case where one bot is visibly waiting.
Limits
Takeover does not put the cloud computer on a corporate VPN. Staff say the machine cannot join that VPN today, and a VPN client installed on it can knock it offline. Sites that exist only inside the VPN need Execution on Local Computer on a machine that is already on the VPN, which is the local-computer page. Public SSO in the browser, such as an Atlassian Cloud login, is the takeover path above, not a VPN install.
iOS can watch and take over a stuck login. It cannot set Always allow, and it cannot show a routine webhook URL. If the desktop is black and the phone on the same account still works, do not Reset. You can finish the login from the phone, or Recover the desktop, without deleting bots.
An approval card that timed out is the approval page, not this one. Mixing them leads people to type a password into a card that was only asking to allow a shell command.
FAQ
The bot never offered Take over. What do I say?
Staff say to ask it to hand you the computer. Then sign in yourself. For a passkey, choose Try another way.
Can I paste the two-factor code so it goes faster?
No. Official troubleshooting says not to paste a password or verification code into ordinary chat. Take over the computer, or use the secrets card when the connector shows one.
I finished the login in another window and the waiting card is still there.
Answer that card, or send any chat message. Staff say the reminder does not notice that login already succeeded.
Will Reset get the bot off the login page?
It might destroy unsynced work and still leave you signing in again on the new computer. Take over first. Reset is the last resort on the recover page.
The site is inside our office VPN. Can the bot join it?
Not by installing a VPN client on the cloud computer. Staff say that can take the machine offline. Use local execution on a computer that is already on the VPN.
Related
- Shared computer — How takeover and the secrets card work.
- Approval needed stuck — A timed-out card, which is not a password prompt.
- Sign-in does not complete — Your Cursor login, as opposed to a website login.
- Local computer — Internal sites that the cloud machine cannot VPN into.
Sources
- Official troubleshooting
- Hand me the computer
- Waiting card
- VPN, SSO, passkeys