LOCI v0.1.111 (Date: 30 Jul 2026)

A stability and accuracy release — twelve fixes across Plan Guard, Save Guard, the on-demand skills, and the Portal. No new capabilities this time.

Fixed

• loci login no longer crashes on Windows in Git Bash — A conflicting OpenSSL library pulled in from Git's own toolchain was aborting the CLI the moment it opened its first secure connection. Login now works normally from any shell.

• Accurate worst-case stack results — Fixed stack-depth's assembly parser reading hexadecimal stack-pointer offsets as zero, which could understate worst-case stack usage.

• exec-trace now analyzes the latest build — Fixed exec-trace running against a stale compiled binary instead of the newest one after a source change.

• ARMv6 timing restored — Fixed timing analysis returning no results for ARMv6 targets because the prediction model was unavailable.

• Correct instruction-to-prediction mapping — Fixed the timing prediction service returning results out of order, which could mismatch assembly instructions with their predicted timing.

• Accurate Save Guard performance diffs — Fixed the Performance row comparing two different calculations as if they were the same metric, which could produce a misleading delta.

• Reliable Save Guard diffing on Rust crates — Fixed before/after comparisons falling back to absolute numbers only, for the rest of a session, after the first edit inside a multi-file Rust crate.

• No more redundant recompiles in Save Guard — Fixed Save Guard recompiling a file from scratch even when Plan Guard had already compiled it earlier in the same session.

• Correct target detection on /loci:setup — Fixed /loci:setup picking up a stale target architecture left over from a previous project when no project was actually open.

• No more silent failures on missing output folders — Fixed LOCI failing silently when a required output directory didn't exist, instead of creating it or surfacing the error.

• Code Health insights load correctly — Fixed the Code Health page in the Portal showing empty when telemetry had stopped updating.

• Correct session count in the Usage tab — Fixed the Portal's Usage tab undercounting the number of sessions.

---

Questions or feedback? [e-mail]