Performance and stability

Use this page if Explyt or the IDE freezes, consumes an unusual amount of CPU or memory, takes a long time to index the project, repeats network requests, or loses chat history.

Narrow the problem down first

1. Note when the symptom appeared and what you did right before it: opening the project, sending a request, an MCP call, indexing, or restoring chats.
2. Wait for the regular IDE indexing to finish. During indexing, CPU, memory, and response time can grow temporarily.
3. Repeat the action in a new chat on a small task. Do not change the model, MCP, and project settings at the same time.
4. If the interface responds, save the exact error text and a screenshot without private code.
5. Before restarting the IDE, write down the names of the open chats and collect a log fragment as described below.

Freezes or high load

Check the OS task manager and the built-in IDE background process indicator. Record which process consumes CPU or memory and whether the load coincides with indexing, a model response, or an external tool call.

If the problem only appears in a large project:

• reduce attachments and do not add the whole repository to the request;
• limit the task to one module or set of files through Edit Scope;
• start a new chat if the current history has grown long;
• temporarily disable an optional MCP server and repeat the same request.

Do not delete IDE system directories, caches, or history files before you collect diagnostics. Such actions can destroy the data needed to analyze the cause.

Slow indexing

Indexing is managed by the IDE. First check that it finished without errors and that it is not indexing build directories, dependencies, or generated files that the project usually excludes.

If the slowdown started after Explyt was installed, compare the same project after a regular IDE restart and record the duration, the project size, and the state of background processes. Do not disable plugins and clear caches at the same time, or the comparison will not reveal the source of the problem.

Network retries and rate limiting

The 429 error means that the service or the MCP server limited the request rate. Do not send the same request over and over. Wait for the period stated in the message or in the Retry-After header, then retry once. If the limit comes back, reduce the number of parallel tasks and check the terms of the selected provider.

For Connection Timeout, check the service availability, the proxy, and the VPN. For MCP problems, use the connection error table.

Chat history is missing or damaged

1. Open History in the Explyt window and find the chat by name using search and the project filters.
2. Restart the IDE the regular way. Explyt restores saved open tabs, but empty new tabs and deleted chats do not come back.
3. If the chat is missing from History, do not create a chat with the same name in its place and do not clear the IDE data.
4. Note roughly when you last worked with the chat, the project, and what you did before it disappeared. Then collect a minimal diagnostic package.

Deleting through Delete Chat is irreversible. There is no recovery operation for a deleted chat.

Collecting diagnostics safely

1. In the IDE, open Help | Show Log in Explorer. In some IDEs the entry is called Show Log in Finder or Show Log in Files.
2. Copy only the log fragment covering a few minutes before and after the problem. Look for lines with the exact error time, Explyt, MCP, 429, timeout, or the message text from the interface.
3. Do not send the whole log directory. Explyt uses the IDE log; the current documentation does not promise a separate Explyt log file.
4. Remove API keys, tokens, authorization headers, request contents, private code, home directories, user names, and internal addresses from the copy. Replace them with clear placeholders such as <TOKEN> and <PROJECT_PATH>.
5. Attach the reproduction steps, the IDE and Explyt versions, the time of the problem, and the sanitized log fragment. The full list is on the "Contacting support" page.