openclaw/nix-openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/nix-openclaw.git synced 2026-07-25 05:35:30 -04:00
Code Issues 31 Packages Projects Releases Wiki Activity

Module generates config keys rejected by OpenClaw 2026.1.29 #13

New Issue
Closed
opened 2026-02-15 17:04:29 -05:00 by yindo · 2 comments
yindo commented 2026-02-15 17:04:29 -05:00
Owner
Copy Link
Copy Source

Originally created by @elocke on GitHub (Jan 30, 2026).

The home-manager module generates a messages.queue.byProvider key in the output JSON config that OpenClaw 2026.1.29 rejects as unrecognized:

Invalid config at ~/.openclaw/openclaw.json:

  • messages.queue: Unrecognized key: "byProvider"

This causes openclaw status to report the config as invalid and openclaw doctor to recommend running --fix to remove the key.

Root Cause

In nix/modules/home-manager/openclaw.nix, mkRoutingConfig unconditionally emits messages.queue.byProvider:

  mkRoutingConfig = inst: {                                                                                                                                        
      messages = {                                                                                                                                                 
        queue = {                                                                                                                                                  
          mode = inst.routing.queue.mode;                                                                                                                          
          byProvider = inst.routing.queue.byProvider;                                                                                                              
        };                                                                                                                                                         
      };                                                                                                                                                           
    };

The default value is always included even though OpenClaw's schema no longer accepts it.

Additionally

The following keys that were previously valid top-level config are also rejected by 2026.1.29 if passed via configOverrides:

  • gateway.host
  • webchat (top-level)
  • bridge (top-level)

Expected Behavior

The module should either:

  1. Stop emitting messages.queue.byProvider if the upstream schema no longer supports it
  2. Or conditionally emit it only when the user explicitly sets a non-default value

Environment

  • OpenClaw: 2026.1.29
  • nix-openclaw: 4731fa63ad
  • Platform: Linux (NixOS LXC)
Originally created by @elocke on GitHub (Jan 30, 2026). The home-manager module generates a messages.queue.byProvider key in the output JSON config that OpenClaw 2026.1.29 rejects as unrecognized: Invalid config at ~/.openclaw/openclaw.json: - messages.queue: Unrecognized key: "byProvider" This causes openclaw status to report the config as invalid and openclaw doctor to recommend running --fix to remove the key. Root Cause In `nix/modules/home-manager/openclaw.nix`, mkRoutingConfig unconditionally emits messages.queue.byProvider: ``` mkRoutingConfig = inst: { messages = { queue = { mode = inst.routing.queue.mode; byProvider = inst.routing.queue.byProvider; }; }; }; ``` The default value is always included even though OpenClaw's schema no longer accepts it. Additionally The following keys that were previously valid top-level config are also rejected by 2026.1.29 if passed via configOverrides: - gateway.host - webchat (top-level) - bridge (top-level) Expected Behavior The module should either: 1. Stop emitting messages.queue.byProvider if the upstream schema no longer supports it 2. Or conditionally emit it only when the user explicitly sets a non-default value Environment - OpenClaw: 2026.1.29 - nix-openclaw: 4731fa63ad163538cacc084e609f78ad5bfd95b2 - Platform: Linux (NixOS LXC)
yindo closed this issue 2026-02-15 17:04:29 -05:00
yindo commented 2026-02-15 17:04:29 -05:00
Author
Owner
Copy Link
Copy Source

@joshp123 commented on GitHub (Jan 31, 2026):

should be fixed in latest master 952a04f

@joshp123 commented on GitHub (Jan 31, 2026): should be fixed in latest master 952a04f
yindo commented 2026-02-15 17:04:29 -05:00
Author
Owner
Copy Link
Copy Source

@joshp123 commented on GitHub (Feb 3, 2026):

[🤖 this message brought to you by codex] should be fixed in 952a04f3 (schema-only config + strip nulls). Closing for now — come and yell at me in #golden-path-deployments on discord if you're still having issues! Stability work continues; we are making this better every week.

@joshp123 commented on GitHub (Feb 3, 2026): [🤖 this message brought to you by codex] should be fixed in 952a04f3 (schema-only config + strip nulls). Closing for now — come and yell at me in #golden-path-deployments on discord if you're still having issues! Stability work continues; we are making this better every week.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
maintainer-roadmap
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/nix-openclaw#13
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?