$ the-wire · showcase
fs-safe 0.14.0 ships safer guest listings, Code Mode stops dropping tool calls
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
Today's work is mostly about silent failure: fs-safe 0.14.0 changes what a descriptor-relative listing reports, openclaw closes two paths where Code Mode and Codex made bad state invisible, and CI stops burning runners on superseded PRs.
fs-safe 0.14.0 openclaw/fs-safe
The headline behavior: descriptor-relative guest listings now report regular files as well as directories without following symlinks, so consumers can select files without reopening a path-type check. Symlinks and special entries report neither kind, which means any switch over the returned kinds needs a default branch.
fix(code-mode): prevent silent loss of tool calls and data openclaw/openclaw
Code Mode could lose output and tool calls produced by returned getters, and invalid JSON arguments were silently saved as null instead of failing. Getter-emitted work now completes through the normal execution lifecycle including suspension, invalid arguments fail catchably, and Gateway config reads expose the same bounded, redacted data direct tool users already get.
fix(native): preserve falsy Windows close failures openclaw/fs-safe
Every thrown value from Windows native write-descriptor cleanup is now preserved, including null and undefined, while all owned closes are still attempted after publication. The native CI job runs the close-failure regression suite with FS_SAFE_NATIVE_MODE=require, and the Windows run executed all 26 cases successfully.
fix: keep legacy Workshop repair out of Gateway startup openclaw/openclaw
Gateway and local CLI startup no longer perform legacy Skill Workshop discovery and repair, which also removes startup failures from an unreadable legacy backup directory. Repair now happens only when you run openclaw doctor --fix or openclaw doctor --yes.
fix(codex): dismiss native requests resolved by another client openclaw/openclaw
Codex approval prompts that another connected client already answered were left pending, eventually producing a duplicate response or a false timeout. OpenClaw now dismisses those requests and suppresses late replies, and the remaining openclaw fixes cover split-pane view preferences and linked-account mention consistency.
Action items
