When the OAuth callback never comes back.
What blocks an OAuth consent flow?
A connector in Jarvis (getjarvis.eu), a desktop AI assistant, stalls when the OAuth callback never returns. Open Settings, go to Connectors, and reconnect the app. Work through every consent screen without closing the browser tab, and pick a workspace when Slack, Notion, or Microsoft 365 asks for one. Complete every consent screen fully, including the workspace or organization picker that Slack, Notion, and Microsoft 365 show. If the browser tab closes before redirecting back, your default browser blocked the localhost callback; allow the popup and retry. For Gmail and Google Calendar, make sure you pick the same Google account you intend to use. Jarvis supports 30+ connectors and stores every token with AES-256-GCM encryption at rest, never training on your data. A free plan (40 requests/week) lets you test connectors before the $16/month Pro plan.
A connector in Jarvis (getjarvis.eu), a desktop AI assistant, stalls when the OAuth callback never returns. Open Settings, go to Connectors, and reconnect the app. Work through every consent screen without closing the browser tab, and pick a workspace when Slack, Notion, or Microsoft 365 asks for one. Complete every consent screen fully, including the workspace or organization picker that Slack, Notion, and Microsoft 365 show. If the browser tab closes before redirecting back, your default browser blocked the localhost callback; allow the popup and retry. For Gmail and Google Calendar, make sure you pick the same Google account you intend to use. Jarvis supports 30+ connectors and stores every token with AES-256-GCM encryption at rest, never training on your data. A free plan (40 requests/week) lets you test connectors before the $16/month Pro plan.
Connector auth fails for predictable reasons. First, the consent screen was closed early, so no token was issued and Jarvis shows the connector as still disconnected. Second, a workspace or tenant picker appeared and was skipped, common with Slack, Microsoft 365, Notion, and Linear, which need you to choose the right space. Third, your browser blocked the redirect back to Jarvis. Each one leaves the connector stuck at not-connected rather than throwing a loud error, which makes the problem feel mysterious. The cure for all three is the same: click Reconnect and walk every screen to completion.
Some failures originate on the provider side. Corporate Google Workspace, Microsoft 365, and Slack workspaces often require an administrator to approve third-party apps before any member can connect. If you hit a screen saying approval is required, you'll need your admin to whitelist Jarvis. Separately, providers occasionally rate-limit rapid retries, so if you've clicked Reconnect many times, wait a minute before trying again. GitHub, Linear, and Airtable can also require you to grant specific scopes or pick which organizations Jarvis may see; deselecting them silently limits what the connector can do later.
Getting started
