gogcli plugin conflicts with gateway bin/gog in buildEnv

[jerome-benoit]

Summary

When gogcli is enabled as a bundled plugin alongside the gateway, home-manager-path fails with a buildEnv conflict: both gogcli-0.9.0/bin/gog and openclaw-2.0.0-beta5/bin/gog provide the same bin/gog path.

Root cause

The openclaw-gateway package bundles gog in its own bin/ output. The gogcli plugin from nix-steipete-tools also installs a standalone bin/gog. When both are added to home.packages by the Home Manager module, pkgs.buildEnv detects the conflicting subpath.

Reproduction

programs.openclaw = {
  enable = true;
  instances.default = { };
  bundledPlugins.gogcli.enable = true;
};

pkgs.buildEnv error: two given paths contain a conflicting subpath:
  /nix/store/...-gogcli-0.9.0/bin/gog and
  /nix/store/...-openclaw-2.0.0-beta5/bin/gog

Environment

• nix-openclaw rev d9bf224
• nix-steipete-tools rev 52ca15a
• nixpkgs unstable, Home Manager standalone
• x86_64-linux (GitHub Actions)

Workaround

Disable the gogcli plugin — the gateway already provides bin/gog:

bundledPlugins.gogcli.enable = false;

[joshp123]

[codex 🤖]: Thanks for submitting an issue. This issue has been automatically closed by Codex.

The LLM thinks that this issue is no longer needed because:
The gateway package no longer exposes bin/gog, so the gogcli collision this issue described is gone. Verified in the current green state at ecfb1dc.
If you still have broken stuff, please jump on #golden-path-deployments in Discord. We're not actively monitoring GitHub issues any more.