Explore the Memory Graph in Hermes Desktop
The Desktop Memory Graph provides a zoomable map and timeline of skills and memories Hermes has learned. It helps answer what exists, when it appeared, and whether an item was used or learned—without replacing careful review of the underlying content.
Official Desktop documentation: Open the official guide
Learning Journey documentation: Open the official guide
Inspect before editing
Open the graph from the command palette or its status-bar item. Filter nodes by All, Used, or Learned, move through the timeline, and open a node only when its context is relevant.
The management view can edit or remove memories and archive skills. Those actions change what Hermes can reuse, so treat them as content maintenance rather than visual tidying. Verify whether a fact is durable, current, scoped to the correct profile, and appropriate to retain before changing it.
A share control exports graph layout as a compact code. Official documentation says the code contains layout only, not memory or skill text. Even so, screenshots of your graph can expose sensitive node labels, relationships, or timing.
Review checklist
- Confirm the active profile before reviewing its graph.
- Use timeline and filters to locate the relevant learned item.
- Read the node content and context before editing or archiving.
- Remove stale personal facts only after confirming they are not still needed.
- Treat skill archival separately from memory deletion.
- Share layout codes only through an appropriate channel.
- Sanitize graph screenshots before publishing or screen sharing.
Common pitfalls
- Judging a node by its position. Layout proximity is not proof that two facts are logically related.
- Deleting to make the graph prettier. Visual density is not a retention policy.
- Assuming screenshots are harmless because layout codes omit text. Pixel captures can reveal labels directly.
- Editing the wrong profile. Memories and skills can be isolated by profile.
Verification
Open a known non-sensitive node, confirm its type and timestamp, and test each filter without mutating content. If sharing layout is required, export and re-import the code in a safe test context and confirm no skill or memory text is embedded. For edits, re-open the item after the change and verify the exact intended record—not a neighboring node—was affected.