Troubleshooting & Logs

Start with the smallest reproducible action and preserve the exact status code. Do not paste raw keys, prompts, transcripts, repository paths, authorization headers, or tool arguments into a public issue.

What v0.4.4 records#

The native log plugin is configured at warning level and writes to standard output. The interface also exposes a bounded in-memory log view with up to 500 entries. The audited configuration does not promise a persistent rotating log file.

Several error paths redact known secret patterns. Redaction can miss a new provider shape or value, so inspect every line before sharing it.

Provider connection checklist#

Confirm the device is online for a hosted provider.
Compare the API base and model ID with the provider guide and account console.
Check that the key belongs to the same provider and has billing/access.
Send a short test with no attachment or tool.
Record the HTTP status and a sanitized error summary.

Status	Typical category	Next check
400	Unsupported request/model parameter	Reset custom parameters and verify API format
401	Missing, revoked, or incorrect credential	Revoke if exposed, then create and save a replacement
403	Region, model, policy, or account restriction	Check the provider console and official support
404	Wrong endpoint or model ID	Copy the exact current value from the provider
429	Rate, quota, concurrency, or credit limit	Check provider usage/billing and retry later
5xx	Provider or endpoint failure	Check service status and retry a minimal request

MCP and command failures#

For stdio MCP, verify the executable is installed and visible to the desktop application's environment. Prefer an absolute executable path when PATH differs from an interactive shell. Keep the server in the foreground while diagnosing it.

Useful non-destructive checks include:

node --version
python --version
git status --short

Do not start an unknown server as an unmanaged background process, and do not run repository-wide restore/delete commands as a troubleshooting shortcut.

Preparing a support report#

Include:

Sythoria version, operating system, and architecture;
provider/tool type and sanitized endpoint host;
the minimal steps and expected/actual result;
sanitized status code and error text; and
whether the issue reproduces in a new empty conversation/project.

Before posting, search the report for key prefixes, Authorization, Bearer, home-directory paths, remote URLs, email addresses, prompts, and transcripts.