Repository navigation
chore(openclaw): bump nix-openclaw to 2026-11-05 HEAD; memory autoCapture on - #6151
Conversation
…ture on nix-openclaw 4b261b08 -> 26516d99: ACP agent-runtime schema fix (upstream #176/#178), undici 8.12.2 + Zod 4.6.6 security bumps, MCP SDK 1.32, private Node 24.22.1 runtime, summarize on the private Node runtime. The packaged app pin is still 2026.10.7 — nix-openclaw has not published a 2026.10.10 pin yet (its Unreleased changelog already carries 2026.10.10 pin validation); tracked separately. memory-lancedb autoCapture: false -> true (recall already on; capture is what makes Shed memory compound).
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 42 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Scope verification: the memory-lancedb leaf of this change evaluates cleanly on this branch ( |
nix-openclaw bump
4b261b08(2026-10-30) →26516d99(2026-11-05, current HEAD):type-discriminated options foragents.entries.*.runtime(fix(packaging): restore pin checks and ACP runtimes openclaw/nix-openclaw#178, fixing the issue our fleet filed as nix-openclaw#176; this was the schema blocker recorded on code#2256, which Drew has since adjudicated closed — embedded stays the architecture).App version honesty: the packaged OpenClaw pin at this rev is still
2026.10.7(nix/sources/openclaw-source.nix). Upstream OpenClaw stable is v2026.10.10 (2026-11-03), but nix-openclaw has not published a pin for it yet — no branch, PR, or tag carries it; their Unreleased changelog shows the .10 pin validation already restored, i.e. the pin bump is staged. This PR takes the newest packaged deployment available through the supported channel; the .10 pin gets its own bump the day upstream publishes it (tracking issue filed with this work).memory-lancedb autoCapture
autoCapture: false → true. Phase 1 (#1300) shipped capture-off while recall proved out. Recall has run clean; capture (with the plugin's length/markup filters) is what makes Shed's long-term memory actually compound from Drew's messages — the standard advanced lancedb setup runs both.Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.