Troubleshooting
What the common errors mean and what to do about them.
The client never asks me to sign in, or loops on sign-in
Check the URL. It must be the exact value from the dashboard's MCP settings, ending in the workspace id. A bare /v1/mcp answers 404. Some clients cache a failed registration; remove the connector and add it again.
401 Authentication required
The client sent no token, or one the server does not recognize. An API key or a CLI session in the token field causes this too; the connector takes OAuth only. Sign in again from the client.
403 This account has no active membership in the requested workspace
The account you signed in with is not a member of the workspace in the URL, or the membership was deactivated. Ask for an invite, or fix the URL.
403 No active workspace for this account
The account exists but belongs to no workspace at all. Create or join one in General Input first.
503 Authentication service temporarily unavailable
The server could not reach the service that resolves your token. Retry in a moment; nothing about the connector's configuration is wrong.
A tool fails with "The workspace sandbox is unavailable right now"
The sandbox pool could not provision or adopt a pod. This arrives as a failed tool call rather than an HTTP error, so the assistant sees it and can retry. Nothing is lost, since work/ is checkpointed after every call that changed it.
The agent says a browser login is not available over this connector
The browser sign-in handoff needs a live view a person watches, which the connector cannot open. The tool result says only that; it does not tell you where to go. Sign in to the site from the dashboard's browser page or with geni browser request-login, then ask the assistant again.
The agent keeps asking me to confirm every step
Your host is gating write tools on their annotations. Set the connector's tool permissions to always allow; see the client page for where that setting lives.
Files I asked for do not open
Download links expire after seven days. Ask the agent to send the file again.
Getting help
Include the workspace id from the URL and the client you are using. Nothing in the URL or a connector name is secret.