hermes/agent-framework
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Redesign file system to avoid conflicts: layered approach with project overrides and global defaults, proper upgrade process

Browse Source
This commit is contained in:
gitea
2026-06-11 22:25:09 -04:00
parent 8897852cc0
commit c629661b28
9 changed files with 120 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompts/research.md
+9 -2
View File
@@ -4,8 +4,15 @@ Your only job is to produce a clean, unambiguous specification. Do not write cod
## Read These Files
1. {project}/.agent-framework/RULES.md — project-specific rules
2. {project}/.agent-framework/AGENT.md — project agent config (if exists)
The Orchestrator reads files using a **layered approach** with a clear precedence:
1. **Project overrides** (highest precedence): `{project}/.agent-framework/` — contains project-specific customizations
2. **Global framework** (default): `~/.agent-framework/` — contains the base framework files
**Precedence rule**: If a file exists in the project's `.agent-framework/` directory, read it from there. If it doesn't exist, read it from the global `~/.agent-framework/` directory.
1. {project}/.agent-framework/RULES.md (if exists — project override) OR ~/.agent-framework/RULES.md (global default) — project-specific rules
2. {project}/.agent-framework/AGENT.md (if exists — project override) OR ~/.agent-framework/AGENT.md (global default) — project agent config
## Task