Troubleshooting
Resolve request, workspace, connection and usage problems
Start with the exact action, expected result and displayed error. Include what you already tried so the next step can test a different cause.
A request stops or fails
Read the reported outcome. A missing decision, allowance limit, failed check and provider error need different responses. Answer the question, wait for the displayed reset, or provide the error and ask for a focused repair. Stopping a request does not undo completed changes.
The Computer or preview is unavailable
Check workspace readiness and the reconnect/recovery message. Tell the agent whether the whole desktop is unavailable or only the app page is blank. Existing workspaces can depend on a different provider account or image than new projects. Preserve the existing workspace while investigating access or recovery.
An MCP connection fails
Open Agent → MCPs and inspect the connection status. Reconnect expired provider consent or have the owner review a changed endpoint/token. For a settings conflict, reload and compare the latest settings before saving again. See MCP reference.
A goal or automation does not progress
Check its status, enabled state and any requested input. Scheduled execution also needs a ready background worker. If the UI reports unavailable or degraded scheduling, ask the environment operator to inspect it; a saved schedule or an open browser tab does not establish worker readiness.
Usage or billing is pending
Open your account's usage view and inspect current limits and reset times. Pending usage or a failed meter read is not proof that a request cost nothing. See Limits and usage.
You cannot sign in
Use the sign-in options currently shown. Access can be limited by the environment's signup or invitation settings. If access is restricted, follow the displayed invitation/waitlist instructions or contact support.
When reporting a problem, include the approximate time and relevant project/request identifiers, but omit passwords and access tokens.