Skip to content

Conversation

@elocke
Copy link

@elocke elocke commented Jan 30, 2026

Summary

  • Remove messages.queue.byProvider from generated config — upstream schema no longer accepts this key as of OpenClaw 2026.1.29
  • Remove the routing.queue.byProvider option definition from both instance and top-level module options
  • routing.queue.mode (still valid upstream) is preserved

Users needing per-channel queue overrides can use configOverrides:

configOverrides.messages.queue.byChannel.telegram = "interrupt";

Test plan

  • nix flake check --no-build passes
  • Verified no remaining references to byProvider in module
  • Generated config no longer includes the rejected key

Fixes #33

🤖 Generated with Claude Code

The upstream schema replaced byProvider with a typed byChannel submodule.
The module was unconditionally emitting byProvider causing config validation
failures. Users needing per-channel overrides can use configOverrides.

Fixes openclaw#33

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Module generates config keys rejected by OpenClaw 2026.1.29

1 participant