Troubleshooting
Find the failing layer first, then apply the smallest safe fix.
Most Seira failures come from one of four layers: the desktop app, a local agent CLI, a connected service, or a computer backend.
Where are my logs?
Where the logs are on Windows, macOS and Linux, and how to share them with secrets removed.
App startup and ports
App will not open, local server is unavailable, or a port is occupied.
Agent engines
CLI missing, model unavailable, authentication failure, or reconnect loop.
Connected apps
OAuth completes but tools do not appear or an account disconnects.
Desktop updates
Download spins, restart does nothing, or the new version does not launch.
Google sign-in in a cloud browser
A passkey sign-in stops at “Verifying it’s you” in a bot’s browser.
Report a bug from any chat: @devs
In any chat with a bot, on the desktop app or on the Cloud, type @devs (it is
the last entry in the @ list) and a few words about what went wrong, then send.
Typing it prepares the report. Nothing is sent until you submit it yourself.
The bot answering the message adds a short summary: what you said went wrong, what it saw itself in the conversation, and steps to reproduce. Seira adds its own facts: the app version, the computer's system, whether it runs on the desktop or the Cloud, the bot's engine and model, recent errors in that conversation, the server's latest warnings and errors, and the conversation's ids. Keys, passwords, tokens, cookies and the parameters of web addresses are masked first. The rest of the conversation is never sent, and neither is any file.
The chat then shows a notice with an Open on GitHub button. It opens a
prefilled issue form in the Seira repository on GitHub. Read the text, change it
if you like, and submit it there. The issue is public once you submit it. Home
folders show as ~, and your email address and install id are not in it.
Collect useful evidence
Before opening an issue, record:
- Seira version and operating system;
- selected engine and model;
- the exact visible error, not only “it failed”;
- whether the same agent CLI works directly in a terminal;
- whether restarting only the affected task changes the result;
- the file from Settings → General → Diagnostics → Export Diagnostics…, which removes keys and passwords (see Where are my logs?).
Never post API keys, OAuth callback URLs, bearer tokens, or the contents of secure credential files.