Troubleshooting
Pick a page based on what you see in the interface or in the project. Start with the narrowest symptom and change one setting at a time.
| Symptom | Where to go |
|---|---|
| The plugin does not install, cannot be found, or does not open | Installation and first launch |
| The agent stops, gets confused, makes things up, or does more than asked | Agent behavior |
| The context runs out, the model does not start, or the context size is wrong | Models and context |
| The agent reads or changes the wrong files | Files and permissions |
| An external tool or knowledge base does not work | MCP and external tools |
| AGENTS.md, a Rule, a Skill, Memory, Model Routing, or MCP does not load or behaves unexpectedly | Configuration diagnostics |
| Tests, the build, or specific testing features do not run | Runs and tests |
| Explyt or the IDE freezes, CPU/RAM grows, indexing is slow, requests repeat, or history is gone | Performance and stability |
| The problem persists and you need data for a support request | Contacting support |
If Explyt works but the result is weak, read the recommendations for working with the agent. End-to-end scenarios for exploring code, fixing bugs, refactoring, and testing are collected in practical tasks.
General diagnostic order
- Record the exact symptom and the action that triggered it.
- Check the agent mode, the selected model, and the available tools.
- Reproduce the problem on a small task or a single test.
- Do not change the model, rules, MCP, and project settings all at once, or it will be hard to identify the cause.
- If the fix touches code, review the diff and repeat the original scenario.