Use this page when a connection or tool call fails. Keep the actual error, remove secrets, and follow its next step. These problems come from current source error paths and client guides.

1. The client shows no tools

Keep Swarmtab open. Open Connect and copy the current executable path. Restart the client. Check its MCP server list and enable Swarmtab. For VS Code use servers, not mcpServers; for Cursor use Agent mode. See your client guide.

2. Chromium is missing or cannot start

Use swarmtab chromium install for real mode or swarmtab chromium install --shell for the shell. Inspect swarmtab chromium path. An invalid SWARMTAB_CHROMIUM override stops discovery; fix or unset it rather than expecting a fallback. Do not point it at an unrelated executable.

3. The license is missing or expired

Sign in in the window and check the device license. Reconnect to refresh an expired pass. If all three device slots are occupied, remove the intended device in the account page and read the date its slot becomes free. Removing it does not bypass its still-valid offline pass.

4. “the human has this page now”

Finish or decline the human check in the window and release control. The agent should repeat the same ask_human request to wait. Retrying screenshots or clicks while you type will not work.

5. The human paused or stopped all agents

Resume in the window only after reviewing why work was stopped. The error says to ask the human to resume. An agent cannot resume itself with settings.

6. “only the human can set permissions or budgets”

Open Permissions and review the proposed scope yourself. Do not try a different tool or the REST API to get around it. A corrupted permissions file can start all agents in observe mode; inspect the recovery warning before changing rules.

7. Another engine has the data folder open

Close your own earlier instance gracefully or use a separate test data folder. Do not delete a live lock file or stop a process you do not own. This error prevents two engines from writing the same state.

8. A saved space is busy or its name is rejected

One agent can use a saved space at once. Have that agent leave or close first. A space name permits letters, digits, - and _, at most 40 characters. List spaces instead of guessing the name. A locked keychain needs your attention; do not replace an existing key.

9. A recipe draft cannot run

Approve the exact version and hash in Recipes. Imports and edits need a new approval. If an expectation fails, inspect the failed step and page before rerunning. A submit may already have happened.

10. A page control changed or the tab limit was reached

Read the page again and use fresh control numbers. A changed approved upload control needs a new approval. Close unused tabs before opening more. Never guess a replacement control or silently split work to escape a limit.

If these steps do not help, run swarmtab doctor and send a report with a redacted result. Do not paste the token or data-folder files into a ticket.

Troubleshooting