Help
Troubleshooting
The messages you might see, what they mean and what to do.
Sign-in problems
Your SwisserAI session expired. Sign in again to continue.
The key of this editor is no longer valid. That happens when it was deleted in the account settings or the session ended. Click Sign In in the message and connect again. Your tasks and settings stay.
The connect page says Connected, but nothing happens in VS Code
- Click Didn't open? Try again on the connect page and allow the browser to open VS Code.
- Check that VS Code is running and is the editor where you clicked Sign in to SwisserAI.
- If VS Code asks whether SwisserAI may open a link, click Open.
- Some browsers block app links on the first try. Start again from Sign in to SwisserAI in the extension.
Sign-in failed: invalid token. Try signing in again.
The sign-in link was old or opened twice. Start again from Sign in to SwisserAI in the extension and use the new tab that opens. The message Couldn't reach SwisserAI to verify your sign-in means your internet connection or a firewall blocked ai.swisser.dev.
Out of credits
The extension shows You're out of credits. Top up to keep building. with an Add Credits button. Tools using the API get error 402 with Insufficient credits and your balance.
- Top up or pick a plan on the pricing page. The task can continue right after.
- Free accounts get 25 credits on each day they sign in to the website.
- If a task used much more than you expected, read Habits that save credits.
Premium model without a plan
swisserai-premium needs a plan. Without one, the API and OpenCode answer with Model "swisserai-premium" requires a premium subscription. Please upgrade or use "swisserai-free".
In the extension the same case can show up as Your account is currently unavailable. Contact support and we'll sort it out. If it appeared right after you changed the model, set the model back to swisserai-free in the settings under Providers. If it stays, contact support.
The agent reads too many files
When the agent searches through many folders, it does not know where to look. Every file it reads costs credits and makes the next steps more expensive too.
- Name the resource, and the file if you know it: "In sw-garages/config.lua ...".
- Open only the folder of the resource you work on, not the whole server.
- Hide maps, models, logs and cache with a .swisseraiignore file.
- Keep Read in auto-approve off for a while: then you see each file it wants and can say "no, look in client/main.lua".
The agent changed the wrong resource
Click Restore Changes or restore the last checkpoint, then repeat the task with the resource name in it. Many servers have several resources that do similar things, for example two garage scripts; the agent cannot guess which one is in use.
Terminal output is missing
When the agent runs a command, it needs to read what the command printed. If you see Shell Integration Unavailable or the agent says it got no output:
- Open the settings, Terminal, and turn on Use Inline Terminal (recommended). Commands then run inside the chat, without your shell profile.
- If you need the normal VS Code terminal, raise Terminal shell integration timeout for slow shells.
- For PowerShell with missing or doubled output, turn on Enable PowerShell counter workaround.
OpenCode problems
OpenCode uses a different model, not SwisserAI
OpenCode did not find opencode.json, so it fell back to its own default. Start OpenCode in the folder that contains the file, or put the file into ~/.config/opencode/. The model name shown at the start of a run should be swisserai-free or swisserai-premium.
OpenCode says the API key is missing or invalid
The variable SWISSERAI_API_KEY is not set in this terminal. Run echo $SWISSERAI_API_KEY (Linux) or echo $env:SWISSERAI_API_KEY (PowerShell). If it prints nothing, set it again as shown in Connect OpenCode to SwisserAI.