provider proxies keep session state in the repo tree (bin/sessions.json) — move to ~/.local/state #3067

Activity

1. dezren39

   added

   bugSomething isn't workingSomething isn't working

   on Oct 31, 2026
2. dezren39 commented on Oct 31, 2026

   

   dezren39

   on Oct 31, 2026

   MemberAuthor

   More actions

   Scope correction (2026-10-31, after Drew's question): yesterday's move DID happen — PRs #2782/#2784 moved the proxies' WORKDIR state (bin/work/: warm-sessions.json, sessions/, acp-project) to ~/.local/state/cli-proxies. bin/sessions.json is a different path and was MISSED by that fix:

   • bin/commandcode-proxy.mjs:428 — SESSION_FILE = path.join(PROXY_DIR, 'sessions.json'), anchored to the script's own directory, no env override.
   • bin/claude-code-proxy.mjs:52 — SESSION_FILE = env CLAUDE_CODE_PROXY_SESSION_FILE || path.join(PROXY_DIR, 'sessions.json'); the override exists but no unit sets it, so it defaults into bin/ too. (The two proxies share this file / mirrored key space, so the fix must land both on the SAME new path.)
   • bin/muse-proxy.mjs — warm-sessions.json resolves under WORKDIR; that one moved correctly.
   • bin/codex-proxy.mjs — sessions.json resolves via sessionStateDir(); audit in the fix.

   Fix in flight: env-overridable session-file path for commandcode-proxy mirroring claude-code's, both units pointed at ~/.local/state/cli-proxies/sessions.json in home/common/default.nix, live file migrated on deploy.
3. dezren39 commented on Oct 31, 2026

   

   dezren39

   on Oct 31, 2026

   MemberAuthor

   More actions

   Correction per Drew (2026-10-31): do NOT gitignore the old bin/sessions.json path. After the fix nothing may write there at all — a gitignore would mask a regression. The dirty primary is the tripwire: if bin/sessions.json ever reappears as dirt, that is the signal the fix leaked. (Same reasoning as Drew's 2026-10-29 call on the bin/work residue: moved intact, deliberately not gitignored.) The fix is: env-overridable session-file paths + both proxy units pointed at ~/.local/state/cli-proxies/sessions.json + one-time migration of the live file. Nothing else.
4. dezren39

   added 2 commits that reference this issue on Oct 31, 2026

   fix(proxies): move shared sessions.json to ~/.local/state/cli-proxies (…

   ...

   65df622

   Merge pull request #3072 from developing-today/fix/proxy-sessions-sta…

   ...

   2854c40
5. dezren39 commented on Oct 31, 2026

   

   dezren39

   on Oct 31, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: fleet monitor
   • Session / ID: repo-fleet-monitor run 2026-10-31 09:12 CDT (intake enrichment, Duty 2)
   • Found via: monitor reconciliation
   • Task: Intake validation — this issue is already resolved.
   • Expectation: closed as completed with evidence.
   • Links: PR fix(proxies): move shared sessions.json to ~/.local/state/cli-proxies (#3067) #3072 (merged 2026-10-31T13:36:47Z) "fix(proxies): move shared sessions.json to ~/.local/state/cli-proxies (provider proxies keep session state in the repo tree (bin/sessions.json) — move to ~/.local/state #3067)" implements exactly the fix this issue specifies: proxy session state moved out of the tracked tree to ~/.local/state/cli-proxies. Closing as completed.
6. dezren39

   closed this as completedon Oct 31, 2026
7. dezren39

   added a commit that references this issue on Oct 31, 2026

   chore(bin): remove tracked sessions.json — proxy session state lives …

   ...

   60af45b