root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-3179): document layered agent memory access

Browse Source 
Documents the layered agent memory access system in the agents documentation, with a minor update to the engine tools reference guide to reflect the documented behavior.

Fusion-Task-Id: FN-3179
This commit is contained in:
Fusion
2026-05-02 02:35:03 -07:00
committed by gsxdsm
parent 623772629f
commit 6b75b3ac8e
5 changed files with 245 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/agents.md
View File

@@ -121,6 +121,21 @@ Agent deletion is available from both the detail header lifecycle controls and t
![Agents view](./screenshots/agents-view.png)
## Agent Memory Layers in Runtime Tools
When engine sessions include per-agent memory context, the memory tools operate over the full agent-memory workspace under `.fusion/agent-memory/{agentId}/`, not only the inline `agent.memory` field.
Runtime behavior:
- `fn_memory_search` can surface snippets from:
- `.fusion/agent-memory/{agentId}/MEMORY.md` (long-term)
- `.fusion/agent-memory/{agentId}/DREAMS.md` (synthesized patterns)
- `.fusion/agent-memory/{agentId}/YYYY-MM-DD.md` (daily notes)
- `fn_memory_get` is intentionally bounded to those same files only.
- Empty inline `agent.memory` does **not** disable search/read of existing dreams/daily files once the agent-memory workspace exists.
This layered behavior is shared by heartbeat agents and task-scoped sessions that inherit agent identity.
## Research Tools in Planning/Execution Sessions
Triage and executor runtime sessions now include a bounded research tool surface: