Skip to main content

Desktop app problems

When the interface, history, or runtime misbehaves, preserve the error and the data first. Reinstalling the app or clearing directories should not be the first step, especially before you have a backup.

It will not start​

Check the installer's origin, the platform architecture, the minimum system requirements, and the exact error text. An operating-system block, a missing dependency, and a corrupted file are different problems and should be handled according to the message. Install-related details are in Install and update.

Conversations or profile cards are missing​

First confirm the project folder is the same as before, then check whether .mystilink/ exists inside it, is readable, and the disk is healthy. A successful web sign-in does not automatically restore local records from another computer.

Also distinguish a freshly opened, empty new conversation from a past conversation whose first message was already sent. Do not create piles of same-named profile cards or overwrite backups while looking for old records; see Data backup and migration.

Cannot send, or it waits forever​

Check whether the current run has actually finished, and whether it is waiting for an inquiry or a card draw or cast. Then check the primary model, account or API permissions, and the network. For model errors see Connection problems.

If you decide to cancel, watch whether the state ends first, then send again; clicking repeatedly may not speed things up and can create duplicate requests.

Search finds nothing​

Try keywords from conversation or profile card names, and check which workspace is open. Do not conclude that data was deleted just because search returned nothing; open the relevant lists and check the directory and backups directly.

Settings do not stick​

Pay attention to how the current section saves and to failure messages. Check read and write permissions on the home and project directories, free disk space, and whether sync software is holding the files. Preserve the current state; do not delete settings.json or the model configuration directly.

A panel is stuck or the layout is broken​

Keep a screenshot and the steps that triggered it; if nothing is pending, quit and reopen, then check whether it reproduces. Back up before updating. If it persists, provide the operating system, version, specific panel, and reproduction steps; see Contact support.