Common Errors

This page covers the user-facing failures most teams see first when onboarding, authorizing IDE access, or configuring workspace integrations.

Login Or Onboarding Does Not Finish

If a user stays on /login, loops back to /start, or never reaches the main app, first confirm that the sign-in method completed and that the workspace selection step is not still blocking progress. Users who requested access to an existing workspace can also be sent to /onboarding/pending until an admin approves the request.

IDE Keeps Asking For Login

Repeated login prompts usually mean the MCP client is configured, but the OAuth grant was never completed or the local config still points to the wrong server details. Check the platform-specific config path, retry a single tool call, complete the browser consent flow, and then confirm the connected client appears on /integrations/agents.

Unauthorized Or Forbidden Tool Calls

401 and 403 errors usually mean one of three things: the user never completed consent, the current workspace is not the one they intended to use, or their role does not allow the requested action. Remember that contributors can draft and edit decisions, but approve or supersede actions require approver or admin access.

Raw API Key Used As Bearer Token

Organization API keys are not direct bearer tokens for /v1/* or /mcp. They must be exchanged through the OAuth token endpoint to obtain a short-lived access token. If a service is calling the API with the raw key, token exchange is the first thing to fix.

GitHub Integration Looks Incomplete

If the GitHub page shows no repositories or no linked installation, check whether the app install was claimed in the correct organization and whether repository sync has run. GitHub sign-in and GitHub App installation are separate auth surfaces, so a user can be signed in successfully while the repository integration still needs setup.