401 / authentication failed
401 / authentication failed
Your session or token expired. Re-authenticate the
autonomy server in your MCP client (it will reopen the browser login/consent flow).410 / stale workspace
410 / stale workspace
The
workspace_id no longer exists - workspaces can be recycled. Re-run list_projects to get a current workspace_id, then retry.403 on a preview-config tool
403 on a preview-config tool
Full Mode (the
project_cors_proxy flag) isn’t enabled for this project. See Full Mode.Setup isn't progressing
Setup isn't progressing
Check
get_setup_preview_status for the dev-server state, and list_env_vars to spot required env vars that aren’t set - then fill them with set_env_var.A task seems stuck
A task seems stuck
Tasks run in the background - keep polling
get_task and report progress rather than blocking. If a run is going the wrong way, stop_task cancels it so you can continue_task with new guidance.A project isn't READY
A project isn't READY
A just-connected repo starts in
PENDING_INITIALIZATION. Call initialize_project and poll list_projects until the status is READY (that’s when it gets a workspace_id). If initialization failed, rerun_initialization with the job id.