Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Integrations show "configure" instead of "connected" after successful OAuth [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46323•Fetched 2026-04-11 06:23:19
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
meresloanemeresloane
Participants
github-actions[bot]github-actions[bot]meresloanemeresloane
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Error 1 (most common): Error 2 (appeared later): Error getting authentication result. Please try again.

Code Example

Error 1 (most common):
Public API request returned 403: Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct.
request_id: req_011CZuV7hWjgibQqd5eAYdN1

Error 2 (appeared later):
Error getting authentication result. Please try again.
request_id: req_011CZuV8KZfAJ1J8xohYvPGt
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Multiple integrations (including Airtable, and others) are not showing as connected in Claude Desktop and claude.ai browser, even though the OAuth flow completes successfully.

Steps to reproduce:

  1. Go to integrations/connected apps
  2. Click configure on any integration
  3. Complete the OAuth flow — get a "connected" popup
  4. Integration reverts to "configure" button, never shows as connected

What I've tried:

  • Disconnecting and reconnecting multiple times
  • Revoking access from the third-party app side and reconnecting
  • Fully quitting and relaunching Claude Desktop
  • Disconnecting VPN
  • Flushing DNS cache
  • Trying in both Claude Desktop and claude.ai in browser — same issue on both

Additional context:

  • The underlying connections actually work — Airtable API calls succeed through Claude Code CLI
  • Logs show step=success in the OAuth redirect, so auth is completing
  • Issue affects multiple integrations, not just one
  • Claude Desktop version: latest (checked for updates)
  • macOS version: 25.4.0
  • affects Claude.ai on phone, desktop and browser

What Should Happen?

Integrations should work!

Error Messages/Logs

Error 1 (most common):
Public API request returned 403: Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct.
request_id: req_011CZuV7hWjgibQqd5eAYdN1

Error 2 (appeared later):
Error getting authentication result. Please try again.
request_id: req_011CZuV8KZfAJ1J8xohYvPGt

Steps to Reproduce

  1. Open Claude Desktop (or claude.ai in a browser)
  2. Go to Settings → Integrations (or Connected Apps)
  3. Click "Configure" on any integration (e.g. Airtable, or others)
  4. Complete the OAuth sign-in flow in the popup window
  5. See a "Connected" success popup appear
  6. Observe that the integration still shows "Configure" instead of "Connected"
  7. Fully quit and relaunch Claude Desktop — integration still shows "Configure"

This happens with multiple integrations, not just one.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

It worked a few days ago

Claude Code Version

claude --version 2.1.85 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

<img width="1998" height="1232" alt="Image" src="https://github.com/user-attachments/assets/7cff1a7c-765b-42db-8682-dc2fe486b95b" />

extent analysis

TL;DR

The issue can likely be resolved by investigating and fixing the authentication token validation or permissions issue that is causing the 403 error.

Guidance

  • Verify that the authentication tokens obtained after the OAuth flow are correctly stored and validated on the Claude Code side.
  • Check the permissions associated with the user and token to ensure they match the required permissions for the integrations.
  • Investigate the request_id logs to see if there are any patterns or clues that could indicate why the authentication result is not being correctly processed.
  • Consider testing the integrations with a different user or token to isolate if the issue is specific to a particular account or token.

Example

No specific code example can be provided without more context on the Claude Code implementation, but an example of how to validate tokens and check permissions in a general OAuth flow might look like:

import requests

# Assuming 'token' is the obtained authentication token
response = requests.get('https://api.example.com/validate-token', headers={'Authorization': f'Bearer {token}'})

if response.status_code == 200:
    # Token is valid, proceed with integration
else:
    # Token is invalid, handle error

Notes

The issue seems to be related to authentication and token validation, but without more specific details on the Claude Code implementation, it's difficult to provide a more precise solution. The fact that the underlying connections work through the CLI suggests that the issue might be specific to the desktop or browser application.

Recommendation

Apply a workaround by re-checking the authentication flow and token validation to ensure that the tokens are correctly obtained, stored, and validated. This might involve updating the Claude Code to handle token validation more robustly or adjusting the permissions associated with the user and token.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#agent execution#callback error#memory management#API rate limit

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING