Guides · Reference

FAQ

Symptoms, and the page that explains them.

Every dashboard screen says "This browser isn't linked to your account" (401). The browser's own identifier was cut or never created — after unlinking it, or when all 10 slots were taken. Sign out and sign back in: it links this browser again, touches neither your agent's key nor your other devices. → Account

My agent's tools all answer 401 since I installed the remote connector. An account has one live agent key; installing the connector revoked the local one. Use the connector, or revoke it on Account and generate a new key for the local server. → Connect an agent

After I approve, the browser cannot open http://localhost:…. That address is the app on your computer finishing its sign-in — Claude Code, for instance. Keep the app running while you approve, and approve within a few minutes: some apps stop waiting after five. On a machine without a browser, sign in with claude mcp login manybases --no-browser: open the address it prints, approve, then paste the address your browser ended on back into Claude Code. → Connect an agent

Sign-up answers 401 with a key my agent created. It no longer does — since 2026-09-07 every publishable key signs users up, whoever created it. A 401 here now means the key is unknown, revoked or rotated. → Keys and identities

A call answered 428. Nothing happened. Read the summary, then re-send the same call with the confirmation_token. → Errors for agents

A call answered 401 "requires a signed-in human". The gesture needs the account's owner: make it from the dashboard, or lend a local agent your session token for an hour. → The human boundary

404 on a project I know exists. The key's scope does not cover it, the project belongs to another account, or it is being deleted: the three answer the same bytes. → Keys and identities

The GitHub run says "project not found". The repository the run is in is not the one linked to the project, the link or the installation was removed, or the project id in the workflow is wrong. → Deploy from GitHub

link_repo answers 404 "not covered". The repository is not in the GitHub App's installation: open the URL in the hint, add it, link again. → GitHub

Writes answer 402 on every project. The account is above a volume quota: reads serve, writes wait until you free space or upgrade. → Limits and quotas

Creating a project answers 402. The Free plan holds two apps: delete one, or upgrade. → Pricing

429 rate_limited. 300 requests per minute per key, shared by every visitor of the app — or, on a function's host, the function's call limits; wait Retry-After seconds. → Limits and quotas

429 on a management call, with Retry-After: 300. Creating, deleting or exporting a project, deploying a function, setting a secret, deploying a site and applying a shared secret share an administration budget — it is what we spend on our infrastructure provider, not what you consume. Nothing ran and your idempotency key is still free: wait the delay, then send the same call again. A tight retry loop only keeps the budget full. → Limits and quotas

I invited someone and the API answered 409. The project has no app URL yet: set it in Settings, or deploy the site. → Invite users

The function's logs are empty. Only the requests a function makes to its project's API are logged, never its console.log. → Functions

A secret I set is not in the function yet. Check the names present on the function (list_function_secrets or its Overview). Redeploying the function picks up the values in force. A shared secret that is still spreading — or still being removed — shows its progress on the account's Secrets screen, where Apply the rest resumes it. → Write an edge function

I deleted a file but a link still works. Wait a few seconds and retry; links are revoked at deletion. If a link is public and the file must stay, there is no way to revoke the link without deleting the file. → Files

The export answers 500 "more files than a single export can carry". The current bound is 40 files per export. → Export your data

I lost a key. Rotate a project key; revoke and regenerate the account key. → Respond to a leaked key

Where is the request id? In the X-Request-Id header of every response, in the body of every 5xx, and on the Logs screen. → API conventions