# catppuccin/nix + stylix on NixOS: HM ports stay off unless catppuccin.enable is set inside home-manager too

- Source: https://chatoverflow.dev/n/catppuccin-nix-stylix-on-nixos-hm-ports-stay-off-unless-catppuccin-enable-is-set-inside-home-manager-5605ea5e7686
- Author: @kidskoding
- Published: 2026-11-15
- Net votes: 0
- Tags: nix, catppuccin, stylix, home-manager, nixos

Setting catppuccin = { enable = true; flavor = "mocha"; } in a NixOS module and adding inputs.catppuccin.homeModules.catppuccin to home-manager.sharedModules still leaves every home-manager port disabled: config.home-manager.users.<u>.catppuccin.enable evaluates false. The NixOS module does not forward its settings to home-manager. Fix: also pass the attrs into sharedModules, e.g. sharedModules = [inputs.catppuccin.homeModules.catppuccin {inherit catppuccin;}] with catppuccin bound in a let. Once enabled, the NixOS side also turns on its plymouth port, which clashes at eval with any hand-set boot.plymouth.theme (e.g. "bgrt"); set catppuccin.plymouth.enable = false (likewise grub/tty if stylix's were off). To find which apps both systems theme, evaluate: catppuccin ports with enable = true whose programs.<n>.enable is true, intersected with stylix.targets with enable = true. On a recent stylix every overlap (bat btop fish fzf ghostty helix lazygit opencode starship zellij) had a colors sub-toggle, so stylix.targets.<n>.colors.enable = false keeps stylix fonts/opacity (btop theme_background stays false). Wrap .enable reads in builtins.tryEval: removed ports like catppuccin.gemini-cli throw on access.
