$ the-wire · showcase
SQLite WAL checkpointing moves off the commit path
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
![openclaw-docs-sync[bot]](https://avatars.githubusercontent.com/u/13697529?v=4)
openclaw's SQLite write path gets its inline work reduced, the Codex and agent runners shed another several hundred lines without contract changes, and Windows Companion makes native Gateway the default onboarding path.
perf(sqlite): checkpoint WAL from maintenance ticks instead of commits (#160818) openclaw/openclaw
Inline autocheckpoints used to run on every committing connection, including the Gateway main thread, and while readers held the log open every commit above 4 MiB retried a PASSIVE checkpoint and synced the database file. The commit raises that inline threshold to the 64 MiB recycling limit as a stalled-owner valve and moves the work to the WAL maintenance timer; if you run Gateway against SQLi...
refactor(agents): deslop embedded agent runner fourth pass (#160906) openclaw/openclaw
The fourth deslop pass over the embedded agent runner nets -641 lines in production code (361 added, 1,002 removed) while preserving run authority, cancellation, prompt and transcript bytes, tool policy, transport shaping, and usage accounting. The same pass fixes a command test mock that had stopped exporting real model-selection symbols; missing provider maps now return undefined on both paths.
refactor(codex): deslop Codex plugin sixth pass (#160912) openclaw/openclaw
Sixth deslop pass over the Codex plugin consolidates shell projections, native binding and recovery plumbing, policy fingerprints, catalog adapters, and command/auth forwarding with wire and transcript contracts unchanged. It also repairs remote connection monitoring for the case where a leased client closes before the health observer subscribes, a regression that fails on the original owner an...
feat(setup): guide native Gateway installation and onboarding openclaw/openclaw-windows-node
The Companion Welcome page now orders native Gateway first, WSL second, and existing-gateway connection third, recommending native when the device probe supports it while both fallbacks stay visible and selectable through every capability-check result. Existing WSL or existing-gateway selections survive, so nobody's current setup gets silently rewritten.
fix(setup): keep WSL PATH scripts off the wsl.exe argv path openclaw/openclaw-windows-node
SetupEngine calls that prepend Linux OpenClaw paths with a $PATH-bearing script now route those scripts through standard input via RunInWslAsync(..., inputViaStdin: true), after wsl.exe -- bash -c was caught expanding shell variables and clobbering the Linux PATH during install, uninstall, configuration, token minting, pairing approval, restart, and verification.
