Troubleshooting

Start with What I did under the answer: it names the model that answered and why, and what went wrong. No reply or a model load failure: confirm the installation finished, check the selected computer is online, close memory-heavy applications, or try a smaller model. A model that cannot load fails at once with the reason.

No live web answer: check that Internet is allowed in the profile, and ask for a search or about something current; a plain question is answered without tools. The same search within 15 minutes is answered from the cache.

An answer did not use your knowledge or memories: use Try a question on the Knowledge page, install an embedding model so search matches meaning, and check that memory is on for the chat. A knowledge source that failed shows the reason; database and web API sources keep answering from the last data fetched.

API connection refused: confirm the daemon is running and copy the current endpoint from API Access. A 401 with local network access on means a request from an app on another device needs a valid API key (people signing in in a browser use their password instead), and a 403 means the key does not allow what the request asked for. Run Test API after changing settings.

To tell the Toskar team about a problem, use Report this beside the error (see Report a problem). For the public issue tracker, include the app version, OS and processor, model, profile, steps to reproduce, and relevant diagnostics, and remove secrets and private prompt or file content before posting.