#How to register?

11 messages ยท Page 1 of 1 (latest)

kind chasm
#

lane task error: lane=main durationMs=96 error="Error: Context engine "lossless-claw" is not registered. Available engines: legacy"

west martenBOT
#

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
      }
    }
  }
}
kind chasm
#

During update I got duplicate, seems it might have broken the system then how do I fix this?

west martenBOT
#

Yeah, that sounds recoverable, not permanently broken.

What likely happened is one of these:

  • the update left two plugin records / paths
  • lossless-claw is selected in config, but the plugin is now disabled / missing
  • the slot points at lossless-claw, but only legacy is 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 --version
  • openclaw plugins doctor
  • openclaw plugins list --verbose
  • openclaw plugins inspect lossless-claw

Docs:

kind chasm
#

Yes have, went back to legacy and made openclaw to fix it