#How to register?
11 messages ยท Page 1 of 1 (latest)
That error usually means your config is pointing at contextEngine: "lossless-claw", but that engine plugin never got loaded, so only the built-in legacy engine exists.
First, can you paste:
openclaw --version
openclaw plugins inspect lossless-claw
openclaw plugins doctor
Likely fix:
openclaw plugins install @martian-engineering/lossless-claw
openclaw plugins enable lossless-claw
openclaw gateway restart
And make sure your config looks like this:
{
plugins: {
slots: {
contextEngine: "lossless-claw"
},
entries: {
"lossless-claw": {
enabled: true
}
}
}
}
Important: the slot value must match the engine's registered id exactly, not just the npm package name.
If you just want to get unstuck immediately, set it back to legacy for now:
plugins: {
slots: {
contextEngine: "legacy"
}
}
Docs:
If you paste the 3 command outputs above, I can tell you exactly which part is missing.
During update I got duplicate, seems it might have broken the system then how do I fix this?
Yeah, that sounds recoverable, not permanently broken.
What likely happened is one of these:
- the update left two plugin records / paths
lossless-clawis selected in config, but the plugin is now disabled / missing- the slot points at
lossless-claw, but onlylegacyis actually loaded
Iโd fix it like this:
openclaw --version
openclaw plugins doctor
openclaw plugins list --verbose
openclaw plugins inspect lossless-claw
If that shows duplicate/odd plugin state, do a clean reset of just that plugin:
openclaw plugins uninstall lossless-claw
openclaw plugins install @martian-engineering/lossless-claw
openclaw plugins enable lossless-claw
openclaw gateway restart
And make sure config ends up like:
{
plugins: {
slots: {
contextEngine: "lossless-claw"
},
entries: {
"lossless-claw": {
enabled: true
}
}
}
}
If you want the fastest temporary recovery, switch back to builtin first:
plugins: {
slots: {
contextEngine: "legacy"
}
}
Then restart the gateway. That should get the system responding again while you clean up lossless-claw.
One extra gotcha: if you previously used a linked/local plugin path, the duplicate may be coming from plugins.load.paths, not just the installed package. openclaw plugins doctor usually calls that out.
Paste the outputs from these 4 commands and I can tell you the exact cleanup path:
openclaw --versionopenclaw plugins doctoropenclaw plugins list --verboseopenclaw plugins inspect lossless-claw
Docs:
If this fixes it, please right-click the solution message โ Apps โ โ Mark Solution, so Answer Overflow can index it.
Yes have, went back to legacy and made openclaw to fix it