Skip to main content

​
A client stays on “Setup pending”

Passport marks a client connected only after it observes real activity. Opening or copying the setup instructions is not enough.
  1. Keep the AI client open.
  2. Finish its browser sign-in.
  3. Ask it to list your Passport tools.
  4. Return to Clients, open the client, and choose Refresh or Troubleshoot.
Passport’s client-specific troubleshooting shows the exact check for Claude Code, Cursor, VS Code, Codex, Claude, ChatGPT, and Passport CLI.

​
An app is missing from one client

Open Clients, select that client, and check App visibility.
  • Turn on the app if it is available but hidden.
  • If it says Not connected yet, open Apps and finish the app connection.
  • If the app is not listed, you may not have access to it. Ask a workspace admin.
After a visibility or access change, ask the client to refresh its tools. Starting a new chat or session can also help clients that cache their tool list.

​
Tools appear twice

You probably have both the normal connection and Desktop compatibility configured for the same client. Open Clients, choose the affected client, and remove the compatibility connection. Keep the normal browser-sign-in connection when it works.

​
”Redirect URI is not allowed” when signing into an app

Some providers allow sign-in to return only to approved domains. The fix is in that provider’s dashboard, not in Passport. Add your Passport domain (or the full callback URL) to their allowed redirect settings:
Admins can copy this from the app’s setup screen under Sign-in service or Callback URL. For Mintlify, use Admin → MCP → Allowed OAuth redirect URIs. This is different from the custom-domain DNS settings. If your organization has several Mintlify deployments, allow the redirect on each one or choose the intended deployment during consent.

​
”A different workspace” / reconnect prompts

Passport will not attribute your activity to the wrong workspace. If this machine’s saved Passport sign-in belongs to a different workspace than the one a client expects, you may see:
  • In the desktop app: “Connected to another workspace (…). Reconnect to use …”
  • From the bridge: “This machine’s Passport credential now belongs to a different workspace. Reconnect this client from the Passport app.”
Reconnect that client from Clients in the intended workspace. This often happens after the same computer signs into another workspace.

​
”This connection isn’t signed in”

Open Clients, select the client, and reconnect it. Finish the browser sign-in before retrying.

​
An agent says an app needs sign-in

The agent should offer a Connect or Reconnect action. Depending on the AI client, this appears as a built-in prompt or as a secure Passport link in the conversation.
  1. Open the link and confirm that it uses your Passport domain.
  2. Sign in to the provider in the browser. Do not paste a password, API key, or provider token into the chat.
  3. Wait for Passport to say All set, then return to the agent. It can retry the original action.
If there is no link, the app may need one-time company setup, or the agent may be an autonomous background agent with no person attached. Open Apps to see the next step or ask your workspace admin.

​
”This account has been deactivated”

A deactivated person cannot sign in or use Passport. You may see:
  • From a connection: “This account has been deactivated.”
  • On the sign-in page: “Your account has been deactivated. Contact your workspace admin.”
An admin can reactivate you in People. Then sign in again and reconnect any accounts that need it.

​
Rate limited

Wait a moment and try again. The message says whether the limit applies to the connection, workspace, or number of calls happening at once. Self-host operators can tune these limits; see Self-host.

​
Passport CLI cannot connect

Run:
doctor checks the runtime, credential store, endpoint, sign-in, and protocol without printing credentials. If it asks you to sign in, run the passport login command shown under Clients → Add client → Terminal & automation.

​
Passport CLI exits with an error code

Stable exit codes help scripts and agents: Run with --json for a structured cause and any approval or app hint.