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

Plugin auto-enable writes to config file in Nix mode #25

New Issue
Open
opened 2026-02-15 17:04:36 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:04:36 -05:00
Owner
Copy Link
Copy Source

Originally created by @ioitiki on GitHub (Feb 8, 2026).

Bug

When running the gateway with OPENCLAW_NIX_MODE=1 (set by the home-manager module), the applyPluginAutoEnable code path on gateway startup writes to openclaw.json unconditionally — replacing the read-only nix store symlink with a regular file.

Expected behavior

In Nix mode, the config file is managed declaratively and should not be written to at runtime. The legacy config migration already has an isNixMode guard:

// gateway-cli — initializeGateway
if (configSnapshot.legacyIssues.length > 0) {
    if (isNixMode) throw new Error("Legacy config entries detected...");
    // ...
}

But the plugin auto-enable path does not:

const autoEnable = applyPluginAutoEnable({
    config: configSnapshot.config,
    env: process.env
});
if (autoEnable.changes.length > 0) try {
    await writeConfigFile(autoEnable.config);  // writes even in Nix mode

Impact

On every gateway startup, the symlink ~/.openclaw/openclaw.json → /nix/store/... gets replaced with a regular file. This causes home-manager switch to fail on subsequent runs with:

Existing file '/home/andy/.openclaw/openclaw.json' would be clobbered

Workaround: setting home.file.".openclaw/openclaw.json".force = true in the home-manager config.

Suggested fix

Guard the writeConfigFile call in the auto-enable path with an isNixMode check, consistent with the legacy migration path. In Nix mode, plugins should be declared in the Nix config rather than auto-enabled at runtime.

Environment

  • openclaw-gateway 2026.1.8-2
  • NixOS, home-manager standalone mode
  • nix-openclaw home-manager module
Originally created by @ioitiki on GitHub (Feb 8, 2026). ## Bug When running the gateway with `OPENCLAW_NIX_MODE=1` (set by the home-manager module), the `applyPluginAutoEnable` code path on gateway startup writes to `openclaw.json` unconditionally — replacing the read-only nix store symlink with a regular file. ## Expected behavior In Nix mode, the config file is managed declaratively and should not be written to at runtime. The legacy config migration already has an `isNixMode` guard: ```javascript // gateway-cli — initializeGateway if (configSnapshot.legacyIssues.length > 0) { if (isNixMode) throw new Error("Legacy config entries detected..."); // ... } ``` But the plugin auto-enable path does not: ```javascript const autoEnable = applyPluginAutoEnable({ config: configSnapshot.config, env: process.env }); if (autoEnable.changes.length > 0) try { await writeConfigFile(autoEnable.config); // writes even in Nix mode ``` ## Impact On every gateway startup, the symlink `~/.openclaw/openclaw.json → /nix/store/...` gets replaced with a regular file. This causes `home-manager switch` to fail on subsequent runs with: ``` Existing file '/home/andy/.openclaw/openclaw.json' would be clobbered ``` Workaround: setting `home.file.".openclaw/openclaw.json".force = true` in the home-manager config. ## Suggested fix Guard the `writeConfigFile` call in the auto-enable path with an `isNixMode` check, consistent with the legacy migration path. In Nix mode, plugins should be declared in the Nix config rather than auto-enabled at runtime. ## Environment - openclaw-gateway 2026.1.8-2 - NixOS, home-manager standalone mode - `nix-openclaw` home-manager module
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#25
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?