{option}`programs.neovim.initLua` through neovim wrapper arguments instead. [2/2]

The module `programs.neovim` now writes to {file}`$XDG_CONFIG_HOME/nvim/init.lua` by default. If you want to manage {file}`$XDG_CONFIG_HOME/nvim/init.lua` yourself, you can set {option}`programs.neovim.sideloadInitLua` to `true` to load the content of [1/2]
#NixOS #Nix #HomeManager

Added new option for yazi: programs.yazi.vfs Yazi provides a vfs.toml config file to manage virtual file systems, which can now be managed with programs.yazi.vfs
#NixOS #Nix #HomeManager

prevents the Syncthing API key from changing unnecessarily, so other tools such as Syncthing Tray do not need to reconfigure the API key as often. [3/3]

`services.syncthing.guiCredentials.passwordFile` and `services.syncthing.guiCredentials.username`. As a benefit, using `services.syncthing.guiCredentials` will only change the Syncthing login configuration if credentials have actually changed, rather than configuring them unconditionally. This [2/3]

The `services.syncthing.passwordFile` option has been removed, as configuring it would not add any authentication requirements to the Syncthing GUI, but in most circumstances would suppress the warnings about the GUI not being secured. Instead, configure [1/3]
#NixOS #Nix #HomeManager

A new module is available: `services.syshud`. A simple system status indicator for Wayland compositors.
#NixOS #Nix #HomeManager

skill-directory workflow supported by the other assistant modules. [4/4]

assistant modules: `programs.claude-code.skills` now accepts either an attribute set or a directory path, and `programs.claude-code.skillsDir` was changed to `programs.claude-code.skills`. The `programs.gemini-cli.skills` option now also accepts a directory path, matching the bulk [3/4]

`programs.claude-code.memory.source` were changed to `programs.claude-code.context` - `programs.codex.custom-instructions` was renamed to `programs.codex.context` - `programs.opencode.rules` was renamed to `programs.opencode.context` Claude Code skills were also unified with the other [2/4]

The Claude Code, Codex, and OpenCode modules now expose a canonical `context` option for configuring their global assistant instructions. The old option names still work for now and emit migration warnings: - `programs.claude-code.memory.text` and [1/4]
#NixOS #Nix #HomeManager

configuration, see idursun.github.io/jjui/customization/confi... [3/3]

idursun.github.io/jjui/customization/confi... New module options are available: - `configLua` to configure the top-level Lua configuration, and - `plugins` to define Lua plugins. Remember to import and set up the defined plugins in `configLua`. For documentation on Lua [2/3]

The `programs.jjui` module has been updated to the latest jjui configuration options. To adhere to the jjui defaults, `configDir` on Darwin now defaults to `~/.config/jjui/` from the previous `~/Library/Application Support/jjui/`. See [1/3]
#NixOS #Nix #HomeManager

A new module is available: 'programs.feedr' Feedr is a modern terminal-based RSS/Atom feed reader with advanced filtering, categorization, and search capabilities. It supports both RSS and Atom feeds with compression handling and provides an intuitive TUI interface.
#NixOS #Nix #HomeManager

provide a way to install PipeWire, as that should be done through your NixOS config (or system package manager). [2/2]

A new module is available: `services.pipewire`. The module provides options for configuring the PipeWire server, the client library, the PulseAudio and JACK emulators, the WirePlumber session manager, and the LV2 plugins for use in filter chains. The module does *not* [1/2]
#NixOS #Nix #HomeManager

vimPlugins.fugitive-vim; config = "# some viml"; } ]; Fix it with: programs.neovim.plugins = [ { plugin = vimPlugins.fugitive-vim; config = "# some viml"; type = "viml"; } ]; [4/4]

less than "26.05". To silence this warning and keep legacy behavior, set: programs.neovim.plugins.PLUGIN.type = "viml"; To adopt the new default behavior, set: programs.neovim.plugins.PLUGIN.type = "lua"; which can be triggered for instance by: programs.neovim.plugins = [ { plugin = [3/4]

"config" is assumed to be written as lua instead of viml. You may see the following warning: evaluation warning: The default value of `programs.neovim.plugins.PLUGIN.type` has changed from `"viml"` to `"lua"`. You are currently using the legacy default (`"viml"`) because `home.stateVersion` is [2/4]

We are changing neovim plugin "config" default type from `viml` to `lua`. When the option was introduced neovim lua support was not as popular or robust as in 0.12. Lua configuration seems to be the most popular these days so starting from 26.05, neovim default plugin [1/4]
#NixOS #Nix #HomeManager

`programs.gemini-cli.settings.mcpServers` when `enableMcpIntegration` is enabled. Any servers explicitly defined in `programs.gemini-cli.settings.mcpServers` will take precedence over those from the global MCP configuration. [2/2]

The `programs.gemini-cli.enableMcpIntegration` and `programs.gemini-cli.skills` options have been added to support configuring the Gemini CLI MCP servers and managing agent skills. The global MCP servers from `programs.mcp.servers` are now integrated directly into [1/2]
#NixOS #Nix #HomeManager

programs.opencode.tui for your settings to take effect. Home Manager will show a deprecation warning during rebuild. See https://opencode.ai/docs/config#tui for more information [3/3]

'tui' in 'programs.opencode.settings', you should move them to 'programs.opencode.tui': programs.opencode.tui = { theme = "tokyonight"; keybinds.leader = "alt+b"; }; For OpenCode v1.2.15+, theme, keybinds, and tui fields in the old location will be ignored. You must migrate to [2/3]

OpenCode TUI configuration support has been added via the 'programs.opencode.tui' option. Since OpenCode v1.2.15, TUI-specific settings like 'theme' and 'keybinds' must be in a separate tui.json file instead of config.json. If you currently have 'theme', 'keybinds', or [1/3]
#NixOS #Nix #HomeManager

such as allowing recurring safe escalations without prompting every time. [2/2]

The `programs.codex.rules` option was added to manage Codex `.rules` files declaratively. Each rule is written under `CODEX_HOME/rules/`, with attribute names mapped to `.rules` filenames automatically. Codex uses these rules for persistent command-prefix decisions [1/2]
#NixOS #Nix #HomeManager

'programs.tmux.tmuxinator.package'. [2/2]

The tmuxinator integration in 'programs.tmux.tmuxinator' now supports declaring projects via 'programs.tmux.tmuxinator.projects'. Each project is written to '$HOME/.config/tmuxinator/<name>.yaml'. The tmuxinator package can be customised via [1/2]
#NixOS #Nix #HomeManager