openclaw - ✅(Solved) Fix [Bug]: npm grammyjs npm anthropic frequent disturbance shell popup in windows every 15 seconds [1 pull requests, 3 comments, 3 participants]

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…
GitHub stats
openclaw/openclaw#72315Fetched 2026-04-27 05:31:43
View on GitHub
Comments
3
Participants
3
Timeline
6
Reactions
0
Timeline (top)
commented ×3labeled ×2cross-referenced ×1

npm grammyjs npm anthropic frequent disturbance shell popup in windows every 15 seconds

Root Cause

npm grammyjs npm anthropic frequent disturbance shell popup in windows every 15 seconds

PR fix notes

PR #72594: fix(runtime-deps): hide bundled npm staging windows

Description (problem / solution / changelog)

Problem

On Windows 11, bundled plugin runtime dependency staging can flash visible npm command windows while installing Telegram grammY / Anthropic runtime dependencies. This is disruptive during gateway/postinstall/runtime staging and is tracked in #72315.

Root cause

The bundled runtime-deps npm child-process calls did not pass windowsHide: true, even though the npm runner already preserves Windows-specific shell / windowsVerbatimArguments behavior.

Complete fix boundary

This sets windowsHide: true on every bundled runtime dependency npm staging execution path found by tracing resolveNpmRunner / resolveBundledRuntimeDepsNpmRunner to actual spawn calls:

  • src/plugins/bundled-runtime-deps.ts for runtime / doctor repair installs.
  • scripts/postinstall-bundled-plugins.mjs for packaged postinstall eager installs.
  • scripts/stage-bundled-plugin-runtime-deps.mjs for build/runtime-postbuild staging installs.

Regression coverage checks the runtime Windows npm shim path, the postinstall spawn helper, and a real stageBundledPluginRuntimeDeps() fallback install path that reaches the mocked npm spawn and materializes staged deps.

What intentionally did not change

  • scripts/npm-runner.mjs is unchanged because it only resolves command/args/options metadata; it does not spawn npm.
  • Active-plugin scoping, stale version detection, and temp cleanup behavior are unchanged because those are separate runtime-deps issues with existing open PRs.
  • Other process-spawn callers are unchanged because this PR is scoped to bundled plugin runtime dependency npm staging.

Tests run

  • pnpm install --frozen-lockfile --offline
  • pnpm test src/plugins/bundled-runtime-deps.test.ts test/scripts/stage-bundled-plugin-runtime-deps.windows-hide.test.ts
  • pnpm exec vitest run test/scripts/postinstall-bundled-plugins.test.ts -t "runs nested local installs with sanitized env when the sentinel package is missing"
  • pnpm exec oxfmt --check scripts/postinstall-bundled-plugins.mjs scripts/stage-bundled-plugin-runtime-deps.mjs src/plugins/bundled-runtime-deps.ts src/plugins/bundled-runtime-deps.test.ts test/scripts/postinstall-bundled-plugins.test.ts test/scripts/stage-bundled-plugin-runtime-deps.windows-hide.test.ts
  • pnpm check:changed
  • git diff --check HEAD~1..HEAD

Local note: running the whole test/scripts/postinstall-bundled-plugins.test.ts file on this Windows worktree still fails in existing packaged-dist/symlink tests (unsafe dist entry, symlink EPERM, stale unlink expectation). The targeted postinstall regression for this diff passes, and the failures do not touch the npm spawn option path changed here.

CI status

Greptile passed with confidence 5/5 and no requested changes.

CI currently has unrelated red checks:

  • check-additional-runtime-topology-architecture fails check:madge-import-cycles on an existing src/cli/argv.ts -> src/cli/program/... cycle. This PR does not touch src/cli/**.
  • checks-node-core-fast-support fails src/cli/command-registration-policy.test.ts (matches plugin registration skip policy). This PR does not touch that test or command registration code.
  • checks-node-agentic-commands fails src/cli/program/root-help.test.ts because a mock is missing CORE_CLI_COMMAND_DESCRIPTORS. This PR does not touch CLI root help or descriptor mocks.
  • check-additional and checks-node-core are aggregate failures caused by the leaf jobs above.

The changed files are limited to bundled runtime-deps npm spawn options and their focused tests:

  • scripts/postinstall-bundled-plugins.mjs
  • scripts/stage-bundled-plugin-runtime-deps.mjs
  • src/plugins/bundled-runtime-deps.ts
  • src/plugins/bundled-runtime-deps.test.ts
  • test/scripts/postinstall-bundled-plugins.test.ts
  • test/scripts/stage-bundled-plugin-runtime-deps.windows-hide.test.ts

Linked issue

Fixes #72315

Changed files

  • scripts/postinstall-bundled-plugins.mjs (modified, +1/-0)
  • scripts/stage-bundled-plugin-runtime-deps.mjs (modified, +1/-0)
  • src/plugins/bundled-runtime-deps.test.ts (modified, +1/-0)
  • src/plugins/bundled-runtime-deps.ts (modified, +1/-0)
  • test/scripts/postinstall-bundled-plugins.test.ts (modified, +1/-0)
  • test/scripts/stage-bundled-plugin-runtime-deps.windows-hide.test.ts (added, +63/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

npm grammyjs npm anthropic frequent disturbance shell popup in windows every 15 seconds

Steps to reproduce

OpenClaw 2026.4.24 (cbcfdf6)

configure telegram

run

Expected behavior

no issue

Actual behavior

[Bug]: npm grammyjs npm anthropic frequent disturbance shell popup in windows every 15 seconds

OpenClaw version

2026.4.24

Operating system

Windows 11

Install method

No response

Model

minimax

Provider / routing chain

openclaw > minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The frequent disturbance shell popup in Windows every 15 seconds may be related to a compatibility issue between grammyjs and anthropic in the OpenClaw environment.

Guidance

  • Investigate the compatibility of grammyjs and anthropic in the OpenClaw environment, specifically on Windows 11.
  • Check for any updates or patches for grammyjs and anthropic that may address the issue.
  • Consider testing the application with a different provider or routing chain to isolate the problem.
  • Review the OpenClaw configuration and setup to ensure that it is correctly integrated with grammyjs and anthropic.

Notes

The lack of logs, screenshots, and evidence makes it difficult to provide a more specific solution. Further investigation and debugging are necessary to determine the root cause of the issue.

Recommendation

Apply workaround: Try updating grammyjs and anthropic to the latest versions or testing with a different provider or routing chain to mitigate the issue.

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…

FAQ

Expected behavior

no issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: npm grammyjs npm anthropic frequent disturbance shell popup in windows every 15 seconds [1 pull requests, 3 comments, 3 participants]