Skip to main content

Configuration diagnostics

Use this page if Explyt does not see an instruction, a rule, a skill, a model profile, or an MCP server, or if it keeps applying an old configuration.

Identify the source first​

Open the active configuration checklist and check only the mechanism related to your symptom. Settings have to be verified across several screens and files.

Explyt does not yet show a single list of the whole effective configuration. The interface also has no full log that explains which path was checked and why each Rule matched or did not match. So check the sources one at a time, and do not treat the absence of a visible indicator as proof that something loaded.

AGENTS.md​

  1. Check that the file is named AGENTS.md and is located strictly in the project root.
  2. Save the file. Explyt tracks it through the VFS and rereads it automatically after a change.
  3. If the new instruction has no effect, start a new chat to rule out old context.

Place AGENTS.md in the project root. Explyt does not load files with that name from nested directories under this scheme. There is no separate indicator listing the AGENTS.md files that were actually loaded.

Rules​

  1. Check the directory: project rules live in .explyt/rules, global ones in ~/.explyt/rules.
  2. Make sure the required filePattern is set in the metadata.
  3. Compare the pattern with the file currently open. Explyt uses Java NIO glob matching; the pattern must match the path in that syntax.
  4. Check that the rule is not disabled in the chat.

Explyt matches filePattern against the path of the current file through Java NIO glob. If no file is selected in the editor, only the general patterns ** and **/* trigger.

filePatternCurrent pathResult
**/*src/main/App.ktmatches
src/**/*.ktsrc/main/App.ktmatches
src/**/*.kttest/AppTest.ktdoes not match
*.mdREADME.mdmatches
*.mddocs/guide.mddoes not match: the pattern does not include a directory
docs/**docs/guide.mdmatches

Use / as the path separator in the pattern and test it against the actual relative project path. Several matched rules can apply at the same time, but the interface does not show the full match trace and the normalized path that was checked.

After you change the rules, the configuration is reread by a watcher. To verify, leave a single rule with a short unambiguous instruction, open a matching file, and start a new chat. A missing required filePattern is highlighted by an IDE inspection; there is no full user-facing report for all front matter errors.

Skills​

Use the structure skills/<name>/SKILL.md inside a recognized configuration root, for example .explyt/skills/<name>/SKILL.md. After a change, Skills are reread automatically.

If a skill does not load, open the Error group in the skill list and hover over the error: the details are available in the tooltip. The error may point to missing front matter, invalid YAML, a required field, or a field path; for syntax errors the line and column may also be shown. Fix the structure or the metadata and invoke the skill manually again with /skill-name.

Model Routing​

In the current implementation, the project-level .explyt/model-routing.yaml fully replaces the global ~/.explyt/model-routing.yaml. Profiles from the two files are not merged by alias. If the project file exists, add every profile the project needs to it. After you update Explyt, verify this behavior on the installed version.

Model Routing files are reread after a change. If a profile does not appear, check the YAML, the selected Project/Global scope, and the availability of the pinned model. See also: model profiles.

Memory Bank​

Check the main toggle at Settings → Tools → Explyt → Memory Bank. When it is off, the memory index is not added to the context and the memory tools are unavailable. Then check .explyt/memory/MEMORY.md and the entry you need. Start a new chat after fixing an outdated entry.

MCP​

Global servers live in ~/.explyt/mcp_servers.json, project ones in .explyt/mcp_servers.json. In the current implementation, a project server with the same name overrides the global one. After you update Explyt, verify this behavior on the installed version.

  1. After editing the file manually, refresh the servers with the interface action available in your installed version.
  2. If the connection was lost, run Reconnect. On reconnect, Explyt fetches the tool list again.
  3. Read the structured connection or call error: it separates the error type from its message and additional data.
  4. Check the URL or command, the environment variables, the account permissions, and whether the tool is present in Tools.

For a detailed look at connections, see MCP and external tools.

If sources conflict​

If instructions from the current request, AGENTS.md, Rules, Skills, Memory Bank, and a custom mode conflict, narrow down the source step by step:

  1. keep the instruction under test in a single source;
  2. disable optional Rules, Skills, and Memory;
  3. start a new chat;
  4. bring the sources back one at a time.

If you cannot find the cause, collect the data as described in "Contacting support".