Bundled runtime deps should stage once into the configured/default writable external stage root, then be reused by later gateway, control/session, and doctor paths. After the first successful staging/install: - first user turn should not trigger another broad bundled runtime-deps install pass; - `models.list`, `node.list`, and related control calls should not block for ~50s on dependency staging; - `openclaw doctor --fix` should converge, with a subsequent run reporting no missing bundled runtime deps; - all paths should derive the same stage-root identity and retained manifest state.

openclaw - 💡(How to fix) Fix [Bug]: Bundled runtime deps still restage on first user turn in 2026.4.24-beta.2 [3 comments, 2 participants]

openclaw2026-04-25 13:30:58

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#71599•Fetched 2026-04-26 05:10:53

View on GitHub

Comments

Participants

Timeline

Reactions

Author

Conan-Scott

Participants

Conan-Scott

steipete

Timeline (top)

commented ×3closed ×1labeled ×1

Follow-up to #71420. Retested on 2026.4.24-beta.2 in the same restricted OpenShift/Kubernetes-style deployment. The writable external staging/cache work appears improved, but bundled runtime deps still do not converge across gateway startup, control/session, and doctor paths.

On startup, OpenClaw stages the active bundled plugin set and reaches ready. On the first user turn/control path, it stages a broader provider/plugin set again, delaying webchat/control responses by ~50s and leaving the user turn stuck for several minutes. openclaw doctor --fix also repeatedly reports missing bundled runtime deps and reinstalls them on subsequent runs instead of converging.

This looks like the same class of issue from #71420: staged deps are not being recognized as already satisfied across all plugin-registry/session-control/doctor paths.

Root Cause

Affected users: operators running OpenClaw in restricted/non-root/containerized deployments where packaged application paths are not writable and runtime state must live under explicit writable volumes. Severity: Medium to High for Kubernetes/OpenShift-style deployments. Consequences:

first user turn can hang for several minutes;
control UI calls such as models.list and node.list are delayed by ~50s;
gateway startup remains slow because active bundled plugins restage deps;
doctor --fix does not converge, making the recommended repair path unreliable;
users may need to restart pods to recover stuck turns;
production-style container deployments remain fragile despite the beta fix.

Code Example

[plugins] acpx staging bundled runtime deps (1 missing, 38 install specs): acpx@0.5.3

---

Startup excerpt from 2026.4.24-beta.2:

2026-04-25T22:37:23.180+10:00 [gateway] starting...
2026-04-25T22:37:24.842+10:00 [plugins] acpx staging bundled runtime deps (1 missing, 1 install specs): acpx@0.5.3
2026-04-25T22:37:39.318+10:00 [plugins] acpx installed bundled runtime deps in 14476ms: acpx@0.5.3
2026-04-25T22:37:41.254+10:00 [plugins] browser staging bundled runtime deps (7 missing, 8 install specs): @modelcontextprotocol/sdk@1.29.0, commander@^14.0.3, express@^5.2.1, playwright-core@1.59.1, typebox@1.1.31, undici@8.1.0, ws@^8.20.0
2026-04-25T22:37:44.539+10:00 [plugins] browser installed bundled runtime deps in 3285ms: @modelcontextprotocol/sdk@1.29.0, commander@^14.0.3, express@^5.2.1, playwright-core@1.59.1, typebox@1.1.31, undici@8.1.0, ws@^8.20.0
2026-04-25T22:37:46.379+10:00 [plugins] discord staging bundled runtime deps (8 missing, 13 install specs): @buape/carbon@0.16.0, @discordjs/voice@^0.19.2, discord-api-types@^0.38.47, https-proxy-agent@^9.0.0, opusscript@^0.1.1, typebox@1.1.31, undici@8.1.0, ws@^8.20.0
2026-04-25T22:37:50.718+10:00 [plugins] discord installed bundled runtime deps in 4339ms: @buape/carbon@0.16.0, @discordjs/voice@^0.19.2, discord-api-types@^0.38.47, https-proxy-agent@^9.0.0, opusscript@^0.1.1, typebox@1.1.31, undici@8.1.0, ws@^8.20.0
2026-04-25T22:38:04.036+10:00 [plugins] memory-core staging bundled runtime deps (2 missing, 14 install specs): chokidar@^5.0.0, typebox@1.1.31
2026-04-25T22:38:07.114+10:00 [plugins] memory-core installed bundled runtime deps in 3078ms: chokidar@^5.0.0, typebox@1.1.31
2026-04-25T22:38:09.250+10:00 [plugins] telegram staging bundled runtime deps (5 missing, 17 install specs): @grammyjs/runner@^2.0.3, @grammyjs/transformer-throttler@^1.2.1, grammy@^1.42.0, typebox@1.1.31, undici@8.1.0
2026-04-25T22:38:11.880+10:00 [plugins] telegram installed bundled runtime deps in 2629ms: @grammyjs/runner@^2.0.3, @grammyjs/transformer-throttler@^1.2.1, grammy@^1.42.0, typebox@1.1.31, undici@8.1.0

First user-turn/control path summary from the same run:

# first user-turn/control path staged the broader set again:
[plugins] acpx staging bundled runtime deps ...
[plugins] anthropic staging bundled runtime deps ...
[plugins] brave staging bundled runtime deps ...
[plugins] browser staging bundled runtime deps ...
[plugins] discord staging bundled runtime deps ...
[plugins] google staging bundled runtime deps ...
[plugins] memory-core staging bundled runtime deps ...
[plugins] openai staging bundled runtime deps ...
[plugins] tavily staging bundled runtime deps ...
[plugins] telegram staging bundled runtime deps ...

# control calls delayed around the same window:
[ws] ⇄ res ✓ models.list ~49700ms
[ws] ⇄ res ✓ node.list ~49700ms
[ws] ⇄ res ✓ device.pair.list ~49700ms

# later warning:
[diagnostic] stuck session: sessionId=unknown sessionKey=agent:main:main state=processing age=214s queueDepth=1

Stage-root evidence from the beta 2 pod shows both a versioned beta 2 root and a fresh openclaw-unknown-* root under ~/.openclaw/plugin-runtime-deps:

openclaw-2026.4.24-beta.2-f53b52ad6d21
openclaw-unknown-6ff65e466848


The beta 2 versioned root had a manifest updated at 2026-04-25 23:21:09 +1000 with 38 specs. The beta 2 openclaw-unknown-6ff65e466848 root had a manifest updated at 2026-04-25 23:12:54 +1000 with 11 specs, matching the Discord/Telegram/shared deps subset (@buape/carbon, @discordjs/voice, @grammyjs/runner, grammy, typebox, undici, ws, etc.).

So beta 2 is still creating/updating an openclaw-unknown-* stage root alongside the expected versioned root. That supports the theory that at least one runtime-deps path is deriving a different package/version identity than the main gateway path.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

Yes

Summary

This looks like the same class of issue from #71420: staged deps are not being recognized as already satisfied across all plugin-registry/session-control/doctor paths.

Steps to reproduce

Run OpenClaw 2026.4.24-beta.2 in a restricted container/Kubernetes/OpenShift-style deployment where the packaged app tree (/app) is not writable by the runtime user.
Use persistent writable OpenClaw state under /home/node/.openclaw.
Start the gateway with bundled plugins enabled, including at least acpx, browser, discord, memory-core, and telegram.
Wait for gateway startup to complete.
Open webchat/control UI and send the first user turn.
Watch the gateway log during the first user turn/control path.
Separately, run openclaw doctor --fix twice and compare whether the second run recognizes bundled runtime deps as already satisfied.

Expected behavior

Bundled runtime deps should stage once into the configured/default writable external stage root, then be reused by later gateway, control/session, and doctor paths.

After the first successful staging/install:

first user turn should not trigger another broad bundled runtime-deps install pass;
models.list, node.list, and related control calls should not block for ~50s on dependency staging;
openclaw doctor --fix should converge, with a subsequent run reporting no missing bundled runtime deps;
all paths should derive the same stage-root identity and retained manifest state.

Actual behavior

On 2026.4.24-beta.2, startup still stages bundled runtime deps and reaches ready after roughly one minute. Then the first user turn/control path stages the broader provider/plugin set again and blocks control responses for ~50s. The agent turn remained stuck for several minutes and produced a stuck-session diagnostic.

Observed startup staging set:

acpx
browser
discord
memory-core
telegram

Observed first user-turn/control staging set:

acpx
anthropic
brave
browser
discord
google
memory-core
openai
tavily
telegram

Observed control-call delay after the first turn/control path:

models.list around 49.7s
node.list around 49.7s
device.pair.list around 49.7s
later node.list around 52.7s

Observed stuck-session warning:

state=processing
age=214s

openclaw doctor --fix also does not converge in this deployment. Each run reports a “Bundled plugin runtime deps are missing” section, then an “Installed bundled plugin deps” section, and during the fix phase logs fresh staging again, for example:

[plugins] acpx staging bundled runtime deps (1 missing, 38 install specs): [email protected]

Subsequent doctor --fix runs repeat the same missing/install output rather than recognizing the staged deps as already satisfied.

OpenClaw version

2026.4.24-beta.2

Operating system

Debian GNU/Linux 12 (GHCR docker image)

Install method

docker/k8s

Model

openai-codex/GPT-5.5

Provider / routing chain

N/A

Additional provider/model setup details

N/A

Logs, screenshots, and evidence

Startup excerpt from 2026.4.24-beta.2:

2026-04-25T22:37:23.180+10:00 [gateway] starting...
2026-04-25T22:37:24.842+10:00 [plugins] acpx staging bundled runtime deps (1 missing, 1 install specs): [email protected]
2026-04-25T22:37:39.318+10:00 [plugins] acpx installed bundled runtime deps in 14476ms: [email protected]
2026-04-25T22:37:41.254+10:00 [plugins] browser staging bundled runtime deps (7 missing, 8 install specs): @modelcontextprotocol/[email protected], commander@^14.0.3, express@^5.2.1, [email protected], [email protected], [email protected], ws@^8.20.0
2026-04-25T22:37:44.539+10:00 [plugins] browser installed bundled runtime deps in 3285ms: @modelcontextprotocol/[email protected], commander@^14.0.3, express@^5.2.1, [email protected], [email protected], [email protected], ws@^8.20.0
2026-04-25T22:37:46.379+10:00 [plugins] discord staging bundled runtime deps (8 missing, 13 install specs): @buape/[email protected], @discordjs/voice@^0.19.2, discord-api-types@^0.38.47, https-proxy-agent@^9.0.0, opusscript@^0.1.1, [email protected], [email protected], ws@^8.20.0
2026-04-25T22:37:50.718+10:00 [plugins] discord installed bundled runtime deps in 4339ms: @buape/[email protected], @discordjs/voice@^0.19.2, discord-api-types@^0.38.47, https-proxy-agent@^9.0.0, opusscript@^0.1.1, [email protected], [email protected], ws@^8.20.0
2026-04-25T22:38:04.036+10:00 [plugins] memory-core staging bundled runtime deps (2 missing, 14 install specs): chokidar@^5.0.0, [email protected]
2026-04-25T22:38:07.114+10:00 [plugins] memory-core installed bundled runtime deps in 3078ms: chokidar@^5.0.0, [email protected]
2026-04-25T22:38:09.250+10:00 [plugins] telegram staging bundled runtime deps (5 missing, 17 install specs): @grammyjs/runner@^2.0.3, @grammyjs/transformer-throttler@^1.2.1, grammy@^1.42.0, [email protected], [email protected]
2026-04-25T22:38:11.880+10:00 [plugins] telegram installed bundled runtime deps in 2629ms: @grammyjs/runner@^2.0.3, @grammyjs/transformer-throttler@^1.2.1, grammy@^1.42.0, [email protected], [email protected]

First user-turn/control path summary from the same run:

# first user-turn/control path staged the broader set again:
[plugins] acpx staging bundled runtime deps ...
[plugins] anthropic staging bundled runtime deps ...
[plugins] brave staging bundled runtime deps ...
[plugins] browser staging bundled runtime deps ...
[plugins] discord staging bundled runtime deps ...
[plugins] google staging bundled runtime deps ...
[plugins] memory-core staging bundled runtime deps ...
[plugins] openai staging bundled runtime deps ...
[plugins] tavily staging bundled runtime deps ...
[plugins] telegram staging bundled runtime deps ...

# control calls delayed around the same window:
[ws] ⇄ res ✓ models.list ~49700ms
[ws] ⇄ res ✓ node.list ~49700ms
[ws] ⇄ res ✓ device.pair.list ~49700ms

# later warning:
[diagnostic] stuck session: sessionId=unknown sessionKey=agent:main:main state=processing age=214s queueDepth=1

Stage-root evidence from the beta 2 pod shows both a versioned beta 2 root and a fresh openclaw-unknown-* root under ~/.openclaw/plugin-runtime-deps:

openclaw-2026.4.24-beta.2-f53b52ad6d21
openclaw-unknown-6ff65e466848


The beta 2 versioned root had a manifest updated at 2026-04-25 23:21:09 +1000 with 38 specs. The beta 2 openclaw-unknown-6ff65e466848 root had a manifest updated at 2026-04-25 23:12:54 +1000 with 11 specs, matching the Discord/Telegram/shared deps subset (@buape/carbon, @discordjs/voice, @grammyjs/runner, grammy, typebox, undici, ws, etc.).

So beta 2 is still creating/updating an openclaw-unknown-* stage root alongside the expected versioned root. That supports the theory that at least one runtime-deps path is deriving a different package/version identity than the main gateway path.

Impact and severity

first user turn can hang for several minutes;
control UI calls such as models.list and node.list are delayed by ~50s;
gateway startup remains slow because active bundled plugins restage deps;
doctor --fix does not converge, making the recommended repair path unreliable;
users may need to restart pods to recover stuck turns;
production-style container deployments remain fragile despite the beta fix.

Additional information

The previous issue #71420 was closed as fixed on main / next release

extent analysis

TL;DR

The most likely fix involves ensuring that all plugin-registry/session-control/doctor paths derive the same stage-root identity and retained manifest state to prevent redundant staging of bundled runtime dependencies.

Guidance

Verify that the openclaw-unknown-* stage root is not being created/updating alongside the expected versioned root, as this suggests a different package/version identity is being derived.
Check the startup logs to confirm that the active bundled plugins are restaging deps, causing delays in control UI calls.
Run openclaw doctor --fix twice to see if the second run recognizes the staged deps as already satisfied, and investigate why it's not converging.
Investigate the plugin-runtime-deps directory to ensure that the manifests are being updated correctly and that the expected versioned root is being used.

Example

No code snippet is provided as the issue seems to be related to the deployment and configuration of OpenClaw rather than a specific code problem.

Notes

The issue seems to be related to the way OpenClaw handles bundled runtime dependencies in restricted containerized deployments. The fact that the openclaw-unknown-* stage root is being created alongside the expected versioned root suggests that there may be an issue with the way the stage-root identity is being derived.

Recommendation

Apply a workaround to ensure that all plugin-registry/session-control/doctor paths derive the same stage-root identity and retained manifest state, such as setting environment variables or configuring the plugin-runtime-deps directory to use a consistent versioned root.

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?

FAQ

Expected behavior

Bundled runtime deps should stage once into the configured/default writable external stage root, then be reused by later gateway, control/session, and doctor paths.

After the first successful staging/install:

first user turn should not trigger another broad bundled runtime-deps install pass;
models.list, node.list, and related control calls should not block for ~50s on dependency staging;
openclaw doctor --fix should converge, with a subsequent run reporting no missing bundled runtime deps;
all paths should derive the same stage-root identity and retained manifest state.

#api #cache issue #memory leak #API versioning #request timeout

Still need to ship something?

×6

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

openclaw - 💡(How to fix) Fix [Bug]: Bundled runtime deps still restage on first user turn in 2026.4.24-beta.2 [3 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Root Cause

Code Example

Bug type

Beta release blocker

Summary

Steps to reproduce

Expected behavior

Actual behavior

OpenClaw version

Operating system

Install method

Model

Provider / routing chain

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

Additional information

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING