Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Windows install regressions slipped past current CI coverage

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

On Windows 11, we reproduced two install/build regressions locally that required fixes outside current main, even though the repo already has a Windows CI lane.

The two observed regressions were:

  1. scripts/pnpm-runner.mjs needed a Windows-native direct-exec path when npm_execpath pointed to pnpm.exe from @pnpm/exe.
  2. extensions/lobster/src/lobster-runner.ts needed an installed-package fallback when @clawdbot/lobster/core was not available from the packaged install layout.

This issue is about preventing recurrence by tightening the Windows-targeted regression coverage.

Root Cause

These are the kinds of regressions that Linux/macOS-focused development can miss naturally, even with good general CI. The repo already has a Windows lane, so the main opportunity here looks like tightening which Windows-specific install/runtime regressions that lane enforces.

RAW_BUFFERClick to expand / collapse

Summary

On Windows 11, we reproduced two install/build regressions locally that required fixes outside current main, even though the repo already has a Windows CI lane.

The two observed regressions were:

  1. scripts/pnpm-runner.mjs needed a Windows-native direct-exec path when npm_execpath pointed to pnpm.exe from @pnpm/exe.
  2. extensions/lobster/src/lobster-runner.ts needed an installed-package fallback when @clawdbot/lobster/core was not available from the packaged install layout.

This issue is about preventing recurrence by tightening the Windows-targeted regression coverage.

Why current CI did not catch this

The repo already has a Windows job in .github/workflows/ci.yml, but that lane intentionally runs a narrow suite via pnpm test:windows:ci.

As of April 20, 2026, package.json includes test/scripts/pnpm-runner.test.ts in test:windows:ci, but it does not include extensions/lobster/src/lobster-runner.test.ts.

That means a Lobster-side Windows install regression can still slip past the current Windows lane even if the pnpm runner regression is covered.

Observed evidence

  • Local Windows work required the fixes currently discussed in #67395.
  • The pnpm runner regression is deterministic enough to encode in test/scripts/pnpm-runner.test.ts.
  • The Lobster packaged-runtime regression is deterministic enough to encode in extensions/lobster/src/lobster-runner.test.ts.
  • The current Windows CI lane (pnpm test:windows:ci) does not run the Lobster regression file.

Suggested regression coverage

  1. Keep the Windows-native pnpm.exe and pnpm.cmd cases in test/scripts/pnpm-runner.test.ts.
  2. Add extensions/lobster/src/lobster-runner.test.ts to test:windows:ci in package.json.
  3. Consider a small Windows install/build smoke that exercises the bundled Lobster runtime resolution path, so this is covered one level above unit tests as well.

Why this matters

These are the kinds of regressions that Linux/macOS-focused development can miss naturally, even with good general CI. The repo already has a Windows lane, so the main opportunity here looks like tightening which Windows-specific install/runtime regressions that lane enforces.

Environment where this was reproduced

  • OpenClaw version: 2026.4.20
  • Operating system: Windows 11
  • Install/launch context: local source checkout and Windows packaged/global install paths
  • Model/provider involvement: none; this is an install/build/runtime bootstrap issue

extent analysis

TL;DR

To prevent recurrence of Windows-targeted regression, add extensions/lobster/src/lobster-runner.test.ts to the test:windows:ci suite in package.json.

Guidance

  • Review the current Windows CI lane configuration in .github/workflows/ci.yml to ensure it covers all necessary test cases.
  • Add extensions/lobster/src/lobster-runner.test.ts to test:windows:ci in package.json to include the Lobster regression file in the test suite.
  • Consider implementing a small Windows install/build smoke test to exercise the bundled Lobster runtime resolution path.
  • Verify that the updated test suite covers both pnpm.exe and pnpm.cmd cases, as well as the Lobster packaged-runtime regression.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The suggested changes aim to tighten the Windows-targeted regression coverage, but may not cover all possible regressions. Additional testing and verification may be necessary to ensure the changes are effective.

Recommendation

Apply the suggested workaround by adding extensions/lobster/src/lobster-runner.test.ts to the test:windows:ci suite, as this will help prevent recurrence of similar regressions in the future.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#parallel task#integration issue#index setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING