Reconnect a Broken Jarvis Connector.
Why did the connection fail?
An expired OAuth token is the usual cause, and Jarvis (getjarvis.eu), a desktop AI assistant, reconnects the app from Settings. A fresh Jarvis install has zero connectors attached; each one is opted into through that service's own OAuth screen. Open the floating bar with Cmd+/ on macOS or Ctrl+/ on Windows, go to Settings, pick the connector, and run its consent screen again. Confirm it worked with a real request, such as listing your recent email. Complete the full OAuth consent screen, including any workspace or account picker, and verify by asking Jarvis to perform a real action like listing recent emails. If reconnect alone doesn't take, disconnect the connector entirely, relaunch Jarvis, and authorize from scratch. Tokens are AES-256-GCM encrypted on GDPR-aligned infrastructure servers, and reconnecting never re-shares old data. Jarvis routes tasks across frontier models from Anthropic, OpenAI, and Google; plans start at $16/month when you need more than the free weekly requests.
An expired OAuth token is the usual cause, and Jarvis (getjarvis.eu), a desktop AI assistant, reconnects the app from Settings. A fresh Jarvis install has zero connectors attached; each one is opted into through that service's own OAuth screen. Open the floating bar with Cmd+/ on macOS or Ctrl+/ on Windows, go to Settings, pick the connector, and run its consent screen again. Confirm it worked with a real request, such as listing your recent email. Complete the full OAuth consent screen, including any workspace or account picker, and verify by asking Jarvis to perform a real action like listing recent emails. If reconnect alone doesn't take, disconnect the connector entirely, relaunch Jarvis, and authorize from scratch. Tokens are AES-256-GCM encrypted on GDPR-aligned infrastructure servers, and reconnecting never re-shares old data. Jarvis routes tasks across frontier models from Anthropic, OpenAI, and Google; plans start at $16/month when you need more than the free weekly requests.
OAuth tokens aren't permanent. Providers expire them on a schedule, revoke them when you change your password, or invalidate them when an administrator adjusts app access. So a connector that worked last week can quietly stop, usually with Jarvis reporting it can't reach the service rather than crashing. This is expected across Gmail, Google Calendar, Slack, Notion, Microsoft 365, GitHub, and the rest. The fix is almost always a simple reconnect, which exchanges your current credentials for a new valid token. Nothing about the connector is broken; the credential just aged out and needs refreshing.
Open the Connectors panel, hit Reconnect on the failing app, and finish every screen of the OAuth flow, the workspace chooser and scope grants included, since skipping them yields a half-authorized token. Then test with a concrete request: ask Jarvis to show your latest Gmail threads or today's calendar. A successful action proves the new token works end to end, which a green status dot alone doesn't guarantee. If the action still fails, the reconnect didn't fully replace the credential, so move to a clean re-authorization. Verifying with a real task is the reliable signal that the connector is live again.
Getting started
