Anyone got this working properly, fully locally, with Hermes n windows?

[aecharles72]

Just can't seem to get it to see Hermes or the old sessions.

[franklyfresh]

I am running this local, have over 100 sessions but still no graph nodes, lessons, crystals. I thought today's update might resolve issues so I did a fresh install - still broken. I'm about ready to give up.

I got an openai compatible URL from Open WebUI and connected my local model. Served through vllm and it handles all compression / summarization perfectly fine. I also had it routed to LiteLLM as well for load balancing between local models and that also worked.

Not sure if my local set up is causing the issues downstream but I'm at a loss as to how to resolve it. Seems like its supposed to be fixed but I'm experiencing the same issues covered in multiple closed threads still on a fresh install.

Edit: sorry this was on linux, didnt see you mentioned Windows

[rohitg00]

Hey @aecharles72 @franklyfresh sorry you both facing these issues, Can you please help me with some instructions so I can reproduce this? Thanks

[aecharles72]

It seems my issue, with the browser console, was with agentmemory(am) and iii using the same ports for everything on windows 11(not wsl2). I got it to see the Hermes-Agent sessions once I started using iii console --port3114. Issue now is i'm using a Hermes-Agent desktop gui and am can't see any of the new sessions on top of the fact that graph, memories, activity and profile have never populated for me. Crystals and lessons populate. I am running fully local on windows 11, LMStudio providing and am is running as an mcp.

[rohitg00]

@aecharles72 @franklyfresh — thanks for the detailed repros. Two different problems in this thread, surfacing them separately.

1. No graph nodes / lessons / crystals on Linux (franklyfresh) — this is CONSOLIDATION_ENABLED defaulting to false. Compression and summarization fire via PostToolUse regardless, but the consolidate pipeline (which writes graph nodes, crystals, and lessons) is gated behind the flag. Your sessions are sitting in the raw observation table waiting for a sweep that never fires.

Two paths from here:

• Immediate workaround: add CONSOLIDATION_ENABLED=true to ~/.agentmemory/.env and restart. The next session-end (or one manual call to POST /agentmemory/consolidate-pipeline) will sweep your 100-session backlog and materialize the graph / crystals / lessons.
• Fix landing in fix(consolidation): default ON when LLM provider is configured (#612) #696: I've opened fix(consolidation): default ON when LLM provider is configured (#612) #696 to flip the default — once an LLM provider is detected (API key set, OPENAI_BASE_URL set for OpenAI-compatible local endpoints, or AGENTMEMORY_PROVIDER=agent-sdk), consolidation auto-enables. After that lands, fresh installs with a configured provider get graph/crystals/lessons without any extra flag flip. BM25-only / AGENTMEMORY_PROVIDER=noop users keep the current behavior.

2. Windows + Hermes "can't see Hermes or old sessions" (aecharles72) — separate issue. A few things to check so I can narrow it:

• Did you launch agentmemory with agentmemory connect hermes or via the plugin install? On Windows, agentmemory connect is currently gated except for claude-code and copilot-cli; Hermes wiring needs the manual install steps (see README → Other agents).
• Is the Hermes binary on PATH? where hermes from PowerShell should resolve. If not, set HERMES_BIN=C:\path\to\hermes.exe in ~/.agentmemory/.env.
• For old sessions not showing in the viewer: what does agentmemory status print? Specifically the "memories" count and "sessions" count. If both are zero on a fresh install, the daemon is reading from a different data/ dir than your runs are writing to (path-quoting on Windows usernames-with-spaces — see fix(hooks): quote plugin script paths #487).

Could you share:

1. Output of agentmemory status on the Windows box.
2. Output of agentmemory doctor.
3. Whether the viewer at :3113 shows the sessions Hermes is producing, or is empty.

That's enough to narrow whether it's a path / connect / Hermes-binary problem and I'll ship the fix.

[aecharles72]

Did you launch agentmemory with agentmemory connect hermes or via the plugin install? On Windows, agentmemory connect is currently gated except for claude-code and copilot-cli; Hermes wiring needs the manual install steps (see README → Other agents).

Yes did manual install, when running the command it tells you manual is the only way

Is the Hermes binary on PATH? where hermes from PowerShell should resolve. If not, set HERMES_BIN=C:\path\to\hermes.exe in ~/.agentmemory/.env.

Yes it's on path, got them seen. New issue is the desktop gui using a seperate home now but seemingly using both directories(I think its a them issue not an agentmemory issue atm)

For old sessions not showing in the viewer: what does agentmemory status print? Specifically the "memories" count and "sessions" count. If both are zero on a fresh install, the daemon is reading from a different data/ dir than your runs are writing to (path-quoting on Windows usernames-with-spaces — see #487).

Shots

There are also no spaces in any pathing

[aecharles72]

that was on .9.16

[aecharles72]

Graph working on 24, memory and activity still not. New session still not being caught but again, most likely because of the desktop gui.