Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: lossless-claw selected and enabled but not registered as context engine in 2026.5.2 [3 pull requests, 1 comments, 2 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#77063•Fetched 2026-05-05 05:52:51
View on GitHub
Comments
1
Participants
2
Timeline
13
Reactions
2
Author
EmpireCreatorEmpireCreator
Participants
clawsweeper[bot]clawsweeper[bot]EmpireCreatorEmpireCreator
Timeline (top)
cross-referenced ×5mentioned ×2subscribed ×2closed ×1

OpenClaw was configured with plugins.slots.contextEngine = "lossless-claw" and plugins.entries.lossless-claw.enabled = true, but the gateway repeatedly logged that lossless-claw was not registered and fell back to legacy.

Error Message

If plugins.slots.contextEngine = "lossless-claw" and plugins.entries.lossless-claw.enabled = true, OpenClaw should either register and use the lossless-claw context engine or surface a clear plugin registration/load error explaining why it cannot be registered.

Root Cause

OpenClaw was configured with plugins.slots.contextEngine = "lossless-claw" and plugins.entries.lossless-claw.enabled = true, but the gateway repeatedly logged that lossless-claw was not registered and fell back to legacy.

Fix Action

Fix / Workaround

  • plugins.slots.contextEngine = "lossless-claw" before workaround
  • plugins.entries.lossless-claw.enabled = true
  • Plugin installed at ~/.openclaw/extensions/lossless-claw/
  • Manifest declared:
    • id: lossless-claw
    • kind: context-engine
  • ~/.openclaw/plugins/installs.json showed resolvedVersion 0.9.2
  • ~/.openclaw/extensions/lossless-claw/package.json showed version 0.9.3
  • openclaw plugins list --json reported a persisted-registry-stale-source warning
  • lcm.db existed and contained data, but lossless-claw was not active as the registered context engine

OpenClaw version: 2026.5.2 Install: global npm at /opt/homebrew/lib/node_modules/openclaw Gateway: LaunchAgent-managed Config before workaround: plugins.slots.contextEngine = "lossless-claw" Config after workaround: plugins.slots.contextEngine = "legacy" Plugin path: ~/.openclaw/extensions/lossless-claw/ Plugin enabled: true Manifest id: lossless-claw Manifest kind: context-engine installs.json resolvedVersion: 0.9.2 package.json version on disk: 0.9.3 openclaw plugins list --json warning: persisted-registry-stale-source

Minimal workaround diff:

PR fix notes

PR #77076: fix(webchat): render read tool output and fix exec output overflow + migrateLinearTranscript idempotent

Description (problem / solution / changelog)

Summary

This PR contains two fixes:

Fix 1: WebChat session transcript overwritten every turn (fixes #77012)

Makes migrateLinearTranscriptToParentLinked idempotent by collecting existing IDs before processing.

Fix 2: Control UI webchat tool output issues (fixes #77054)

Bug 1 - read tool output not rendered:

  • extractToolText() in tool-cards.ts only handled item.text and item.content as strings
  • Modern tool results have item.content as array: [{ type: 'text', text: '...' }]
  • Added array content block handling to extract text from nested blocks

Bug 2 - exec output text clipped:

  • .chat-tool-card had overflow:hidden which clipped long content when max-height exceeded
  • Changed to overflow:auto to allow scrolling

Files Changed

  • ui/src/ui/chat/tool-cards.ts - extractToolText array handling
  • ui/src/styles/chat/tool-cards.css - overflow:hidden to overflow:auto
  • ui/src/ui/chat/tool-cards.test.ts - new tests

Changed files

  • extensions/telegram/src/probe.test.ts (modified, +72/-0)
  • extensions/telegram/src/probe.ts (modified, +11/-2)
  • src/config/sessions/transcript-append.ts (modified, +29/-2)
  • src/config/types.telegram.ts (modified, +8/-0)
  • src/config/zod-schema.providers-core.ts (modified, +9/-0)
  • src/context-engine/registry.ts (modified, +43/-0)
  • src/plugins/loader.ts (modified, +8/-0)
  • ui/src/styles/chat/tool-cards.css (modified, +1/-1)
  • ui/src/ui/chat/tool-cards.test.ts (modified, +42/-1)
  • ui/src/ui/chat/tool-cards.ts (modified, +18/-0)

PR #77092: fix: persist and restore registered context engines in plugin cache (fixes #77063)

Description (problem / solution / changelog)

Fixes #77063 - lossless-claw selected and enabled but not registered as context engine

Root cause: When a cached plugin registry is reused, context engines registered by plugins (like lossless-claw) are lost because the cached state restoration did not restore registered context engines.

Changes:

  • src/context-engine/registry.ts: Add RegisteredContextEngineEntry type, listRegisteredContextEngines(), and restoreRegisteredContextEngines() functions
  • src/plugins/loader.ts: Add contextEngines field to CachedPluginState, restore context engines when using cached state, and save contextEngines to cache

Changed files

  • extensions/telegram/src/probe.test.ts (modified, +72/-0)
  • extensions/telegram/src/probe.ts (modified, +11/-2)
  • src/config/sessions/transcript-append.ts (modified, +29/-2)
  • src/config/types.telegram.ts (modified, +8/-0)
  • src/config/zod-schema.providers-core.ts (modified, +9/-0)
  • src/context-engine/registry.ts (modified, +43/-0)
  • src/plugins/loader.ts (modified, +8/-0)
  • ui/src/styles/chat/tool-cards.css (modified, +1/-1)
  • ui/src/ui/chat/tool-cards.test.ts (modified, +42/-1)
  • ui/src/ui/chat/tool-cards.ts (modified, +18/-0)

PR #77091: fix(telegram): add httpTimeoutMs config for health probe timeout control (fixes #77060)

Description (problem / solution / changelog)

Fixes #77060 - Control UI menus freezing due to Telegram blocking health probe

Changed files

  • extensions/telegram/src/probe.test.ts (modified, +72/-0)
  • extensions/telegram/src/probe.ts (modified, +11/-2)
  • src/config/sessions/transcript-append.ts (modified, +29/-2)
  • src/config/types.telegram.ts (modified, +8/-0)
  • src/config/zod-schema.providers-core.ts (modified, +9/-0)
  • src/context-engine/registry.ts (modified, +43/-0)
  • src/plugins/loader.ts (modified, +8/-0)
  • ui/src/styles/chat/tool-cards.css (modified, +1/-1)
  • ui/src/ui/chat/tool-cards.test.ts (modified, +42/-1)
  • ui/src/ui/chat/tool-cards.ts (modified, +18/-0)

Code Example

[context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".

---

[context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".

---

Relevant repeated gateway log entry:


[context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".


Bounded diagnostic findings:


OpenClaw version: 2026.5.2
Install: global npm at /opt/homebrew/lib/node_modules/openclaw
Gateway: LaunchAgent-managed
Config before workaround: plugins.slots.contextEngine = "lossless-claw"
Config after workaround: plugins.slots.contextEngine = "legacy"
Plugin path: ~/.openclaw/extensions/lossless-claw/
Plugin enabled: true
Manifest id: lossless-claw
Manifest kind: context-engine
installs.json resolvedVersion: 0.9.2
package.json version on disk: 0.9.3
openclaw plugins list --json warning: persisted-registry-stale-source


Minimal workaround diff:


-      "contextEngine": "lossless-claw"
+      "contextEngine": "legacy"


After the workaround:


Gateway restarted cleanly.
PID changed after restart.
No new "lossless-claw is not registered" messages appeared after the restart timestamp.
Normal chat behavior was stable under legacy.
lcm.db and lcm-files remained preserved and untouched.

---

~/.openclaw/openclaw.json.bak-20260503-205746
~/.openclaw/lcm.db.bak-20260503-205753
~/.openclaw/lcm-files.bak-20260503-205757
~/.openclaw/state-backup-20260503-205800.tgz

---

PRAGMA integrity_check = ok

---

conversations: 26
messages: 26,850
summaries: 275
context_items: 1,625
large_files: 5
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

OpenClaw was configured with plugins.slots.contextEngine = "lossless-claw" and plugins.entries.lossless-claw.enabled = true, but the gateway repeatedly logged that lossless-claw was not registered and fell back to legacy.

Steps to reproduce

  1. Run OpenClaw with lossless-claw installed under ~/.openclaw/extensions/lossless-claw/.
  2. Configure ~/.openclaw/openclaw.json with plugins.slots.contextEngine = "lossless-claw".
  3. Confirm plugins.entries.lossless-claw.enabled = true.
  4. Start or restart the LaunchAgent-managed OpenClaw gateway.
  5. Use the agent normally.
  6. Observe repeated gateway log entries:
[context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".
  1. Change only plugins.slots.contextEngine from "lossless-claw" to "legacy" and restart the gateway.
  2. Observe that no new lossless-claw is not registered messages appear after the restart timestamp.

Expected behavior

If plugins.slots.contextEngine = "lossless-claw" and plugins.entries.lossless-claw.enabled = true, OpenClaw should either register and use the lossless-claw context engine or surface a clear plugin registration/load error explaining why it cannot be registered.

Actual behavior

The gateway repeatedly logged:

[context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".

The plugin appeared installed and enabled, but the selected context engine was not registered at runtime. After changing only plugins.slots.contextEngine to "legacy" and restarting the gateway, no new lossless-claw is not registered messages appeared.

OpenClaw version

2026.5.2 observed locally

Operating system

macOS 26.4.1

Install method

npm global

Model

xai/grok-4.3 primary; anthropic/claude-haiku-4-5 configured as lossless-claw summaryModel

Provider / routing chain

OpenClaw gateway using configured local providers; primary runtime model observed as xai/grok-4.3

Additional provider/model setup details

plugins.entries.lossless-claw.config.summaryModel was set to anthropic/claude-haiku-4-5.

Relevant observed plugin state:

  • plugins.slots.contextEngine = "lossless-claw" before workaround
  • plugins.entries.lossless-claw.enabled = true
  • Plugin installed at ~/.openclaw/extensions/lossless-claw/
  • Manifest declared:
    • id: lossless-claw
    • kind: context-engine
  • ~/.openclaw/plugins/installs.json showed resolvedVersion 0.9.2
  • ~/.openclaw/extensions/lossless-claw/package.json showed version 0.9.3
  • openclaw plugins list --json reported a persisted-registry-stale-source warning
  • lcm.db existed and contained data, but lossless-claw was not active as the registered context engine

Logs, screenshots, and evidence

Relevant repeated gateway log entry:


[context-engine] Context engine "lossless-claw" is not registered; falling back to default engine "legacy".


Bounded diagnostic findings:


OpenClaw version: 2026.5.2
Install: global npm at /opt/homebrew/lib/node_modules/openclaw
Gateway: LaunchAgent-managed
Config before workaround: plugins.slots.contextEngine = "lossless-claw"
Config after workaround: plugins.slots.contextEngine = "legacy"
Plugin path: ~/.openclaw/extensions/lossless-claw/
Plugin enabled: true
Manifest id: lossless-claw
Manifest kind: context-engine
installs.json resolvedVersion: 0.9.2
package.json version on disk: 0.9.3
openclaw plugins list --json warning: persisted-registry-stale-source


Minimal workaround diff:


-      "contextEngine": "lossless-claw"
+      "contextEngine": "legacy"


After the workaround:


Gateway restarted cleanly.
PID changed after restart.
No new "lossless-claw is not registered" messages appeared after the restart timestamp.
Normal chat behavior was stable under legacy.
lcm.db and lcm-files remained preserved and untouched.

Impact and severity

Affected users/systems/channels:

Single observed local OpenClaw installation using lossless-claw as the configured context engine.

Severity:

Medium to High. The configured context engine was unavailable at runtime, causing repeated context-engine fallback noise and requiring a manual switch to legacy.

Frequency:

Repeatedly observed before switching to legacy; no new occurrences observed after switching to legacy and restarting.

Consequence:

lossless-claw data remained preserved on disk, but the lossless-claw context engine was inactive. Legacy mode did not read lcm.db, so Lossless Claw memory was unavailable while using the workaround.

Additional information

This was observed and diagnosed on OpenClaw 2026.5.2, but I do not know whether 2026.5.2 is the first affected version. Similar symptoms may have existed earlier, so I am not filing this as a confirmed regression.

Backups were created before changing configuration:

~/.openclaw/openclaw.json.bak-20260503-205746
~/.openclaw/lcm.db.bak-20260503-205753
~/.openclaw/lcm-files.bak-20260503-205757
~/.openclaw/state-backup-20260503-205800.tgz

The lcm.db backup passed:

PRAGMA integrity_check = ok

Observed lcm.db contents before switching to legacy:

conversations: 26
messages: 26,850
summaries: 275
context_items: 1,625
large_files: 5

After switching to legacy, lcm.db stopped receiving new writes and remained preserved on disk.

Last known good version:

NOT_ENOUGH_INFO

First known bad version:

NOT_ENOUGH_INFO

extent analysis

TL;DR

The lossless-claw context engine is not registered due to a potential version mismatch or plugin registration issue, causing the gateway to fall back to the legacy engine.

Guidance

  • Verify the version consistency of the lossless-claw plugin by checking the ~/.openclaw/extensions/lossless-claw/package.json and ~/.openclaw/plugins/installs.json files.
  • Check the plugin registration by running openclaw plugins list --json and looking for any warnings or errors related to the lossless-claw plugin.
  • Try resolving the persisted-registry-stale-source warning by updating the plugin registry or reinstalling the lossless-claw plugin.
  • Consider checking the lcm.db file for any corruption or issues that might be preventing the lossless-claw context engine from registering.

Example

No code snippet is provided as the issue seems to be related to plugin registration and configuration rather than code.

Notes

The issue might be specific to the lossless-claw plugin or the OpenClaw version being used. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply a workaround by switching to the legacy context engine until the issue with the lossless-claw plugin is resolved, as it allows the gateway to function normally and preserves the lcm.db data.

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

If plugins.slots.contextEngine = "lossless-claw" and plugins.entries.lossless-claw.enabled = true, OpenClaw should either register and use the lossless-claw context engine or surface a clear plugin registration/load error explaining why it cannot be registered.

#installation#request error#file not found#serialization error#model compatibility

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]: lossless-claw selected and enabled but not registered as context engine in 2026.5.2 [3 pull requests, 1 comments, 2 participants]