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

Open
#2,774 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

  • #2802 by @isihussain — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, typescript
Domain
backend, devtools

Research direction

Start with TOOLS/lib/Boundary.ts, TOOLS/MemoryWriter.ts, STATUSLINE/Admission.ts, and STATUSLINE/State.ts; trace the seven Windows path and permission failures described in the issue. Run the listed memory health check and pipe session JSON into LIFEOS_StatusLine.sh on Windows to reproduce them. Done means the health check has no critical findings, ledger verification succeeds, and the statusline renders every row.

Written by the indexing model from the issue text.

Description

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.

Dominant language
TypeScript
Stars
19.9k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.