Troubleshooting

Read the message above the composer, then check in order:

1. Access: you need editing access, not only a guest/viewer invitation.
2. Control: another teammate may be driving this chat. Accept a handoff or fork your own conversation.
3. Computer: open Your computers and bring your own device online.
4. AI setup: open Providers, check installation/login, and refresh connections.
5. Selection: choose an available model and supported effort.
6. Active work: if the agent is already running, use Queue message or wait for completion.

Starting without files still requires computer and AI setup to send a prompt.

Wake the computer, restore internet access, and open desktop using the same account as the browser. Check whether the runner was paused. For the standalone runner, leave the start command running in a terminal.

Use Check connection again. If the app asks for an update, install the newer desktop/runner. If the device was revoked, pair it again explicitly. Repeated disconnects can indicate a proxy/firewall blocking the workspace’s streaming connections.

• Wrong hostname: a public invitation must use your workspace’s public domain, not 0.0.0.0 or someone else’s localhost. For this service use https://multicode.in and preserve the rest of the link.
• Expired/replaced link: ask the host for a fresh invitation. Organisation links expire after 14 days; guest chat access lasts 7 days from creation; handoff offers last one hour.
• Wrong email: guest links are bound to the invited email. Sign in with that account.
• Incomplete URL: preserve the entire guest link, including its #invite= fragment.
• Already accepted: open the workspace or Shared with me; an organisation invitation is single-use.
• Team joined, project missing: ask the project manager to add you to the project.

Do not post the complete token in a public support thread.

Check the entered address and spam folder. Wait for the resend timer, then request a new code and use the newest email. Follow the code expiry and resend instructions shown by Clerk.

If the page reports delivery failure, follow its retry guidance or contact the workspace administrator. Email delivery acceptance does not guarantee placement in the inbox. Google sign-in does not require this separate code flow.

Try the installed AI CLI directly on the connected computer and finish its own login or provider configuration. Update the CLI if needed, then use Check connections and refresh the model picker.

If the app marks a model unavailable, select an available model explicitly. If the provider reports quota or billing errors, resolve them in that provider’s account. For local models, confirm the model is installed and the expected local server is running. Discovery does not download weights.

Confirm the selected room and repository. Your original imported folder, the app’s saved repository, and the runner’s managed worktree are separate locations. Check import completion, save status, the last uploaded activity, and whether the correct repository was published or synced.

Inspect Activity & checkpoints after an interrupted task. Unsynced local files are not available to teammates yet. If editing or publication conflicts, preserve your work and resolve the conflict before retrying.

For Slack/Discord, confirm the intended project, your management permission, server-side provider setup, and the bot’s channel access. Select supported public channels and save the sharing consent. Use Refresh status after authorising in the browser.

For the terminal, see terminal availability. Connecting an AI computer does not enable a remote shell in the hosted application.

Include the action you tried, exact visible error, approximate time, desktop/browser version, and whether the computer/provider showed as connected. Share a screenshot with private conversation text and credentials removed.

Describe what happened before retrying an unconfirmed instruction or recovery action. Do not include invitation tokens, provider credentials, verification codes, or the runner’s private configuration file.