make opencode work w/ NixOS

[pmarreck]

Description

Installed OpenCode via 'npm install -g --prefix "$HOME/.local" opencode-ai@latest'.

Ran it and got this:

bash> opencode
Could not start dynamically linked executable: opencode
NixOS cannot run dynamically linked executables intended for generic
linux environments out of the box. For more information, see:
https://nix.dev/permalink/stub-ld

There is an "opencode" on nixpkgs but it is an extremely old version at this point.

Making assumptions about what's available on a linux install at runtime just because you're running on "a linux" is bad design. Neither codex nor gemini nor claude (all of which I have installed identically to the method above; they're available on nixpkgs, but the above method keeps them always at the bleeding edge) make this assumption and all run just fine.

Even better, perhaps someone should update the version on nixpkgs on a more regular basis, but none of the others do that either, so that's probably a big ask. ;)

https://search.nixos.org/packages?channel=25.05&show=opencode&query=opencode

OpenCode version

Latest

Steps to reproduce

1. be on the ultimate linux distro, NixOS
2. install opencode using npm
3. try to run it

Screenshot and/or share link

No response

Operating System

NixOS 25.05

Terminal

Wezterm

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• GLIBC_2.25 Required -> Need An Alternative #3045: Similar dynamic linking issue with GLIBC compatibility across different Linux distributions
• Installer should check if unzip is present #3501: Related installation issue where OpenCode makes assumptions about available Linux tools
• AUR install cannot resolve @parcel/watcher-linux-x64-glibc #3282: Linux distribution-specific installation issue related to glibc compatibility

Feel free to ignore if none of these address your specific case.

[rekram1-node]

yeah we should fix this

[xamcost]

I know it doesn't answer @pmarreck 's original question, but an opencode service is available in home-manager. I use this config, and it works like a charm:

{
  home.file = {
    ".config/opencode/agent/".source = ../../dotfiles/config/opencode/agent;
  };

  programs.opencode = {
    enable = true;
    settings = {
      theme = "tokyonight";
      autoupdate = true;
      mcp = {
        context7 = {
          type = "remote";
          url = "https://mcp.context7.com/mcp";
        };
      };
    };
  };
}

Just dropping this in case that helps.

[pmarreck]

@xamcost While I'm not yet on the home-manager train (long story: short time and LOTS of dotfiles), I do like how the declarative config for it is stored that way too, there.

[itpropro]

I know it doesn't answer @pmarreck 's original question, but an opencode service is available in home-manager. I use this config, and it works like a charm:

{
home.file = {
".config/opencode/agent/".source = ../../dotfiles/config/opencode/agent;
};

programs.opencode = {
enable = true;
settings = {
theme = "tokyonight";
autoupdate = true;
mcp = {
context7 = {
type = "remote";
url = "https://mcp.context7.com/mcp";
};
};
};
};
}

Just dropping this in case that helps.

This is also broken. Home-manager only provides an overlay for configs, but still uses the original opencode nixpkgs package. That one currently only displays Bun is a fast JavaScript runtime, package manager, bundler, and test runner. when you run it and the previous working version you could pin is far before 1.0.

[itpropro]

I think the best way forward would be to have a flake natively provided by the opencode team. This is how most fast moving projects do it to avoid having old versions in nixpkgs and to have the best experience for the users. You would also have full control over the build pipeline and dependencies, as the flake.nix would live here at the root of the repo.
A good example for this would be walker (https://github.com/abenz1267/walker) or the hyprland landscape.
Are there any plans to support Nix in the future @thdxr ?

[rekram1-node]

@itpropro I think what you are saying makes total sense, the issue we have had thus far is none of us use nix. That's partially why the "help-wanted" tag is on this issue because we are hoping someone in the community can help get this started and we will give them what they need to do so.

Keeping it first party supported makes sense

[rekram1-node]

Okay I think this may be good now?

nix run nixpkgs#opencode # or github:sst/opencode for latest dev branch