# Hermes Agent ignoring your project instructions

> Verify the active directory, chosen context file and loading evidence before rewriting the rules.

Canonical: https://hermeswatcher.com/troubleshoot/project-instructions-not-loaded  
Section: Troubleshooting · Memory & context  
Last reviewed: Oct 19, 2026  
Basis: Explained from the official Hermes Agent docs and repository (Nous Research). Steps follow the linked official sources.

## Locate the session's actual project

Record where the session started, which project it is working in and the instruction file you expected it to use. The context-file guide documents selection priorities and directory discovery. A file existing somewhere on the machine does not establish that it was selected for this session. In particular, inspect higher-priority files and local overrides before assuming an AGENTS.md edit took effect.

Ask the agent to identify the applicable instruction source and quote one harmless, distinctive rule. Compare that answer with the file itself and available loading diagnostics. If the wrong project or directory was used, start from the intended workspace and repeat the small check. Avoid duplicating the same instructions across many unrelated folders.

## Check loading failures

Look for a blocked-file notice, a read failure or a truncation marker. A long instruction document can obscure its own essential rules. Reduce the startup guidance to project purpose, key paths and operating constraints, then move detailed reference material into documents the agent can open when needed.

If the correct file loaded but behavior still conflicts, use one minimal task that exposes the rule and record the actual action. Ask for the specific reason it departed from the instruction. This separates file discovery from instruction following, which require different repairs. Repeated rewriting without identifying which stage failed makes the result harder to diagnose.

## Expected result and limits

The useful evidence is a known applicable file, a successful loading indication and correct behavior on a bounded task. It is not merely the agent saying it understands. This guide uses current context-file documentation; installed releases may implement different priorities. Preserve existing project customizations while inspecting overrides or simplifying guidance.

## Related tools

- [Carry project knowledge into the next session](https://hermeswatcher.com/workflows/project-knowledge.md)
- [Build a useful GitHub issue review](https://hermeswatcher.com/workflows/github-issue-review.md)
- [Context files: give a project durable instructions](https://hermeswatcher.com/tools/context-files.md)

## Sources

- [Context Files](https://hermes-agent.nousresearch.com/docs/user-guide/features/context-files)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt