Hey, @BG1, thanks for the detailed report. There are two separate things here.
First, the grokbot://mcp/oauth/callback you saw is no longer what we send. Since 7 September, Robinhood sign-in from Grok Bot uses a normal https://www.cursor.com/agents/... callback, so the part about allowlisting grokbot:// is basically not relevant anymore.
Second, your attempt on the evening of 7 September did come back from Robinhood with an authorisation, but it arrived about 17 minutes after the start. The sign-in request is only valid for a short window of time, about 15 minutes. That’s why we rejected it as expired on our side, not because of oauth/error.
Please try again like this:
In Grok Bot on your phone, open the Robinhood connector and tap Authenticate.
Complete the Robinhood login, any device approval, and tap Allow within a couple of minutes of starting. If Robinhood asks you to approve the device in its app, do that first, then restart from step 1.
If you land on robinhood.com/oauth/error again, copy the full authorise URL from the browser. It starts with agent.robinhood.com or robinhood.com and includes redirect_uri=. Send it here, along with the exact time you tapped Allow.
If it still won’t work on your phone, the most reliable path right now is to connect Robinhood once from Grok Bot desktop on Mac or Windows, or from Cursor on a computer, using the same account. Connectors are stored on the account, so the trading tools will then show up in Grok Bot on your phone too.