Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Extreme CPU/RAM spike during Telegram pairing approval due to full plugin registry load [1 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#62163•Fetched 2026-04-08 03:08:14
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
callebtccallebtc
Participants
callebtccallebtc

Root Cause

To finalize Telegram pairing, the bot prompts the host administrator to run the CLI approval command: openclaw pairing approve telegram 123456

Due to the architectural regression introduced in v2026.4.5, every single child/CLI worker process erroneously initializes and loads the entire plugin registry upon startup (including massive bundled plugins like BlockRun, partner tools, and all models). Instead of performing a lightweight state mutation, the CLI process parses and JIT-compiles megabytes of plugin code.

When executing the pairing approval command on the host, this results in the Node process consuming >100% CPU and excessive RAM for upwards of 1-2 minutes just to approve a 6-digit code.

Code Example

openclaw pairing approve telegram 123456
RAW_BUFFERClick to expand / collapse

Bug Description

Between the v2026.3.14 and v2026.4.5 releases, Telegram pairing experiences extreme CPU and RAM spikes.

The exact root cause of the spike during the pairing flow is the CLI Plugin Loading Regression tracked in #62051.

Root Cause

To finalize Telegram pairing, the bot prompts the host administrator to run the CLI approval command: openclaw pairing approve telegram 123456

Due to the architectural regression introduced in v2026.4.5, every single child/CLI worker process erroneously initializes and loads the entire plugin registry upon startup (including massive bundled plugins like BlockRun, partner tools, and all models). Instead of performing a lightweight state mutation, the CLI process parses and JIT-compiles megabytes of plugin code.

When executing the pairing approval command on the host, this results in the Node process consuming >100% CPU and excessive RAM for upwards of 1-2 minutes just to approve a 6-digit code.

Steps to Reproduce

  1. Start an openclaw gateway running v2026.4.5.
  2. Initiate a Telegram pairing request.
  3. Attempt to approve the pairing via the CLI: 
    openclaw pairing approve telegram 123456
  4. Observe the command taking an excessive amount of time (e.g., ~2 minutes) to execute while pinning CPU cores to 100%+ and severely spiking RAM usage.

Related Issues

  • #62051 (Root cause: worker processes load all plugins, causing CPU saturation)
  • #61701 (Gateway process 100% CPU after upgrade)
  • #43178 (Telegram polling watchdog triggers full gateway restart under load)

extent analysis

TL;DR

Downgrade to v2026.3.14 or wait for a fix for the CLI Plugin Loading Regression to mitigate the CPU and RAM spikes during Telegram pairing.

Guidance

  • Verify the issue by checking the CPU and RAM usage while running the openclaw pairing approve telegram 123456 command on v2026.4.5.
  • Check the related issues (#62051, #61701, #43178) for any updates or workarounds.
  • Consider implementing a temporary workaround, such as manually approving the pairing without using the CLI, if possible.
  • Monitor the performance of the openclaw gateway and adjust resource allocation as needed to prevent crashes or downtime.

Example

No code snippet is provided as the issue is related to a specific version regression and not a code-level problem.

Notes

The exact fix for the CLI Plugin Loading Regression is not provided in the issue, so downgrading to a previous version or waiting for an update is the safest approach.

Recommendation

Apply workaround: Downgrade to v2026.3.14 to avoid the CPU and RAM spikes during Telegram pairing, as the root cause is a known regression in v2026.4.5.

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…
#model download#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

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

Back to top recommendations

TRENDING