Repository navigation
[0.10.1, Windows] Local harness: daemon writes refinements to a shared sessions/harness/, kernel reads per-session session-artifacts/<id>/harness/ — local refinements invisible and mixed across sessions
#3816
Replies: 2 comments
|
I traced this on current main ( Branch: main...armaanamatya:prime-agent:fix/refine-local-harness-dir-v2 Root cause. The refinement writer and the kernel reader derive the "local" store from two different bases, and it is not Windows-specific.
TS v0.9.8 has one resolver, Why it surfaced in 0.10.1. Fix. Resolve the local store once on the host (the way Verification. The new test passes with the fix and fails without it. The |
|
Still present on prime-agent 0.10.2 (Windows 11, daemon sessions), seen 18 Nov 2026 in two sessions of two projects.
Two requests on top of the fix proposed above: a migration (or at least a note in the release) for the entries stranded under A smaller, separate point: the digest at session start shows three global memories and counts the rest ("+19 more memory entries"); a note behind the count is easy to miss, and the titles of all entries would fit. |
Uh oh!
There was an error while loading. Please reload this page.
Related: #3547 (v0.10.0, Windows — daemon/kernel disagree on local harness env vars; auto-closed as unvouched, not fixed). This looks like the same family after the 0.10.1 change.
Environment
prime-agent update --check→ up to date), Windows 11 x64, kernel-venv Python 3.11What happens
~/.prime/agent/session-artifacts/<session-id>/harness/harness_state.jsonRLM_HARNESS_STATE_DIR(set per session)~/.prime/agent/sessions/harness/harness_state.jsonPRIME_AGENT_SESSION_DIR+/harness— same file for every sessionrlm.get_harness_state()(local) shows 0 entries andrlm.harness.search(...)finds nothing; the per-session file does not exist.sessions/harness/harness_state.jsoncontains local entries and refinement events from several different sessions (e.g. 2026-10-22 and 2026-10-27).session-artifacts/*/harness/harness_state.jsonfiles were last modified 2026-10-22 16:48 KST; the first refinement in the shared file is 2026-10-22 02:03 UTC; 0.10.1 was installed on 2026-10-22. Before that, local refinements landed in the per-session files.Repro
os.environ['RLM_HARNESS_STATE_DIR']→…/session-artifacts/<id>/harness./refine(or let a user refinement create a local memory).rlm.get_harness_state().entries→ empty;Path(os.environ['RLM_HARNESS_STATE_DIR'])/'harness_state.json'→ missing.~/.prime/agent/sessions/harness/harness_state.json→ contains the new local entry (plus other sessions' local entries).Expected
Local refinement writes to the same per-session state the kernel reads (
RLM_HARNESS_STATE_DIR), and sessions do not share one "local" file.Impact
rlm.harness.search).~/.prime/agent/harness/harness_state.json).All reactions