Conversation
We pin the OpenClaw core (config/openclaw-target.txt) but installed the codex plugin unpinned — `openclaw plugins install codex` resolves @latest. So the plugin drifts ahead of the pinned core and every Codex chat crashes with "_diagnosticRuntime.createDiagnosticTraceContextFrom ActiveScope is not a function" (the newer plugin calls a runtime API the pinned core doesn't expose). Two customers on the latest ClawBox hit this; "You're up to date" boxes can't self-heal via the updater. - gateway-pre-start.sh: read the openclaw-target pin; reinstall codex when its version != the core target (not just when missing/broken); install the scoped pinned spec @openclaw/codex@<target> instead of the bare @latest alias. Drifted boxes now self-heal on next gateway start. - install.sh: the plugin-refresh loop derives each plugin's npm package from rootDir and pins @openclaw/* plugins to $TARGET instead of reinstalling by bare id (which also resolved @latest). - bump version 3.0.5 -> 3.0.6 so already-current devices receive the fix. Validated on a Jetson: forced codex to 2026.5.27 against core 2026.5.22, ran the heal path, confirmed it detected the mismatch and realigned to 2026.5.22.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdd optional OpenClaw target pin handling; install script refreshes external plugins by deriving npm package names and pins ChangesOpenClaw Plugin Version Pinning and Alignment
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
Actionable comments posted: 0 |
The browser install test navigated to openclawhardware.dev, but the main domain is now clawbox.tech. Update the navigation target, title, assertion, and comment accordingly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Actionable comments posted: 0 |
We pin the OpenClaw core (config/openclaw-target.txt) but installed the codex plugin unpinned —
openclaw plugins install codexresolves @latest. So the plugin drifts ahead of the pinned core and every Codex chat crashes with "_diagnosticRuntime.createDiagnosticTraceContextFrom ActiveScope is not a function" (the newer plugin calls a runtime API the pinned core doesn't expose). Two customers on the latest ClawBox hit this; "You're up to date" boxes can't self-heal via the updater.Validated on a Jetson: forced codex to 2026.5.27 against core 2026.5.22, ran the heal path, confirmed it detected the mismatch and realigned to 2026.5.22.
Summary
Type of change
How was this tested?
bun run lintpassesbun run testpassesbun run buildsucceedsChecklist
Screenshots / logs (if UI or runtime change)
Summary by CodeRabbit
Bug Fixes
Chores
Tests