Resolve loading issues caused by file path/naming errors, priority overrides, and reload requirements
This page helps you diagnose issues where project instructions (memory), Skills, or Agents are not loaded as expected.
When the project instructions file (default
Memory / project instructions not loaded
When the project instructions file (default AGENTS.md) is not loaded into context:
- File name: confirm the file name matches the
context.fileNamesetting (defaultAGENTS.md). - Discovery boundary: the upward search stops at a directory containing
context.memoryBoundaryMarkers(default.git). Files outside the boundary are not discovered. - Additional directories: only the current directory is scanned by default. To load memory from additional trusted directories, enable
context.loadMemoryFromIncludeDirectories. - Discovery limit:
context.discoveryMaxDirs(default 200) caps the number of searched directories; very large repositories may hit the limit. - Folder trust: untrusted directories do not load project content.
- Use
/memoryto view the currently loaded memory sources.
Skills not loaded
- Use
/skillsto view the list of loaded Skills. - Directory structure: a Skill must live at
skills/<name>/SKILL.md. Confirm the directory hierarchy and file name are correct. - Source priority: Skill sources rank built-in < plugin < project level < user level; on name conflicts, higher priority overrides lower.
- Conditional Skills: activated only when file paths match; they do not appear otherwise.
- Feature switch:
/skillsrequires Skills support and the admin toggle to be enabled.
Agents not loaded
- Use
/agentsto view loaded Agents. - Confirm the Agent definition files are in the right location and format (definition files under the
agents/directory). - Check whether
agents.overridesdisables the target Agent. - Extra definitions loaded via
--agentsapply to the current session only.
Reloading
- After editing a definition, reload per object:
/memoryfor memory,/skills reloadfor Skills,/agents reloadfor Agents;/commandsfor custom commands. - If none of those work, restart Qoder CLI CN; some loading-related settings are marked "restart required" and only apply after a restart.
Next steps
- Context and memory mechanics: How Memory Works, Memory.
- Extension loading issues: Hooks, MCP, and Plugin Issues.
- Configuration issues: Settings Not Taking Effect.