Skip to content

[bug] Windows: memory writes and statusline fail on a fresh install (POSIX-only path… #2774

Open

Description

@AmanzioJW

What happened

On Windows every memory write is refused and the statusline crashes on every render, because several tools assume POSIX paths and permission bits

Summary

Environment

  • LifeOS 8.761.0, Windows 11, Bun 1.4.4 (Windows x64)
  • Claude Code 2.1.303, hooks run through Git Bash
  • The user-data folder is a directory junction from the install tree into the config tree

Summary

On Windows, every memory write is refused and the statusline crashes on every render. Both come from code that assumes / separators, a / filesystem root, or POSIX permission bits. Seven defects, each hidden behind the previous one.

Memory (health check reports "Latest reviewer run is failed")

  1. TOOLS/lib/Boundary.ts, confinedPath: an absolute walk starts at sep, so the first component it stats is a backslash followed by the drive letter, which never exists (ENOENT). Every absolute path is refused, including the real file inside the user-data repo. Relative paths pass. Error: EWRITE_FAILED: memory write refused at the system/user boundary ... does not resolve inside the USER_DATA repo. Fix: start from parse(p).root and join with cur.endsWith(sep).

  2. TOOLS/lib/Boundary.ts, atomicWrite: invariant((fstatSync(fd).mode & 0o777) === mode) always fails, because Windows reports 0o666 whatever mode was requested.

  3. TOOLS/MemoryWriter.ts, snapshotBeforeWrite: absPath.split("/").pop() returns the whole Windows path, which trips the invariant snapshot target ... must sit directly in ... memory-snapshots.

  4. TOOLS/MemoryWriter.ts: the invariant snapshot dir ... is wider than 0700 fails for the same reason as (2).

  5. TOOLS/MemoryWriter.ts (4 sites): abs.replace(CLAUDE_ROOT + "/", "") leaves the full drive-letter path as the ledger row's file key. CortexLedger.ts verify then reports entries-drift on files the writer itself just wrote.

Statusline (prints nothing)

  1. STATUSLINE/Admission.ts (3 sites): startsWith(this.directory + "/render-") throws INVARIANT VIOLATION: render lock must be scoped to inflight. Fix: use sep.

  2. STATUSLINE/State.ts, expandRoot: converts a drive-letter install root to the MSYS form (slash, drive letter, slash). Bun on Windows cannot open that form, so every read under state.root returns null. Visible effect: blank STATE row and no doctor line. Fix: keep the native path when process.platform === "win32".

Smaller items found on the way

  • TOOLS/MergeSettings.ts with a relative --output settings.json fails with EEXIST: file already exists, mkdir '.'. An absolute output path works.
  • TOOLS/Inference.ts line 483: spawnSync("id", ["-un"]).stdout.trim() throws when the USER variable is unset and id is not on PATH (PowerShell).
  • TOOLS/ParkedReplay.ts replays only EDRIFT items, so writes parked with EWRITE_FAILED are never replayed after the cause is fixed.
  • The header's flag emoji draws as two letters, because Windows fonts have no flag glyphs.

Repro

  1. Fresh install on Windows 11; let one session end so the memory reviewer fires.
  2. Run bun LIFEOS/TOOLS/MemoryHealthCheck.ts: overall is critical.
  3. Pipe any session JSON into LIFEOS/LIFEOS_StatusLine.sh: invariant violation.

Verification of the fixes

  • confinedPath: 12 accept and refuse cases pass, including .. escapes through the junction and targets in the system tree.
  • After all seven: the health check has 0 critical findings, CortexLedger.ts verify is OK, a reviewer run wrote entries unaided, and the statusline renders every row.

The patches are small, about 25 changed lines in four files. Happy to open a PR.

Details

  • Kind: bug
  • LifeOS version: 8.761.0

Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.

Activity

  1. katieskoehler-star commented on Nov 16, 2026

    @katieskoehler-star

    Confirming this on a second machine: LifeOS 8.761.0, Windows 11 Home, Bun 1.4.4, hooks run through the Claude desktop app (Code tab), user data linked through a directory junction. Defects 1–5 reproduced exactly as described, and the fixes in this issue cleared them. Three more findings from the same install that this issue doesn't cover yet:

    8. The reviewer needs the claude CLI on PATH, which a desktop-app-only install doesn't have. Before any of 1–5 bite, the reviewer fails with inference failed: Executable not found in $PATH: "claude", and the health check reports it as parse-failed. The desktop app ships its own claude.exe, but in a versioned folder that changes on every app update, so it can't be relied on. Installing the standalone CLI (irm https://claude.ai/install.ps1 | iex) didn't put %USERPROFILE%\.local\bin on the user PATH here, so the reviewer kept failing until it was added by hand, and then the CLI also needed its own claude auth login. Suggestion: have Doctor (or DetectInference) check that claude resolves and is signed in, and name both fixes.

    9. Ledger rows written before fix 5 need a migration. Rows that were already written with a drive-letter file key stay unmatched after the fix. CortexLedger.ts adopt says "matches the ledger, nothing to adopt" (because inspectDrift finds no head for the relative key and returns null), verify keeps reporting no-events, and genesis refuses because events exist. What worked: move the old cortex-events.jsonl to archive/, then run genesis. A one-time rekey step in Migrate.ts (convert any file key that is absolute or uses \ to the POSIX path relative to the root) would avoid the manual step.

    10. MemoryHealthCheck reports settings-hook-absent for hooks that are registered. On Windows the installed commands look like "C:/.../bun.exe" "C:/.../hooks/MemoryReviewFire.hook.ts" (quoted, absolute, forward slashes). The check flags MemoryTurnStart, MemoryReviewFire and MemoryHealthGate as "not registered in any settings layer" even though they're registered and firing. It looks like the matcher doesn't accept the quoted absolute form.

    The same POSIX mode-bit pattern as 2 and 4 also appears in TOOLS/Secrets.ts (.env must be mode 0600 after set), TOOLS/lib/CacheDir.ts and TOOLS/SplitAndTranscribe.ts, so Secrets.ts set will likely hit it on Windows as well. Guarding them with process.platform !== "win32" worked here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions