Skip to content
Oeiuwq Faith Blog OpenSource Porfolio

3timeslazy/nix-search-tv

Fuzzy search for Nix packages.

3timeslazy/nix-search-tv.json
{
"createdAt": "2025-01-29T09:30:56Z",
"defaultBranch": "main",
"description": "Fuzzy search for Nix packages.",
"fullName": "3timeslazy/nix-search-tv",
"homepage": "",
"language": "Go",
"name": "nix-search-tv",
"pushedAt": "2026-03-08T20:25:08Z",
"stargazersCount": 226,
"topics": [
"cli",
"fzf",
"nix",
"nixos",
"search",
"television"
],
"updatedAt": "2026-03-21T07:44:49Z",
"url": "https://github.com/3timeslazy/nix-search-tv"
}

Fuzzy search for NixOS packages.


asciicast

Out of the box, it is possible to search for things from:

Also, you can search for arbitrary modules options and/or web pages. See [Custom Search]!(#custom-search)

nix-search-tv does not do the search by itself, but rather integrates with other general purpose fuzzy finders, such as television and fzf. This way, you can use it by piping results into fzf, embed into NeoVim, Emacs or anything else. Some examples [here]!(#examples)

Add nix.toml file to your television cables directory with the content below:

[metadata]
name = "nix"
requirements = ["nix-search-tv"]
[source]
command = "nix-search-tv print"
[preview]
command = "nix-search-tv preview {}"

or use the Home Manager option:

programs.nix-search-tv.enableTelevisionIntegration = true;

The most straightforward integration might look like:

Terminal window
alias ns="nix-search-tv print | fzf --preview 'nix-search-tv preview {}' --scheme history"

There is also a [nixpkgs.sh]!(./nixpkgs.sh) script which provides more advanced fzf integration. It is the same search but with the following shortcuts:

  • Search only Nixpkgs or Home Manager
  • Jump to source code or homepage
  • Pipe preview to a pager to see documentation in full screen and select text
  • Search GitHub for snippets with the selected package/option
  • And more

You can install it like:

Terminal window
let
ns = pkgs.writeShellScriptBin "ns" (builtins.readFile ./path/to/nixpkgs.sh);
in {
environment.systemPackages = [ ns ]
}
environment.systemPackages = [ nix-search-tv ]

There are many ways how one can install a package from a flake, below is one:

{
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
nix-search-tv.url = "github:3timeslazy/nix-search-tv";
};
outputs = {
nixpkgs,
nix-search-tv,
...
}: {
nixosConfigurations.system = nixpkgs.lib.nixosSystem {
modules = [
{
environment.systemPackages = [
nix-search-tv.packages.x86_64-linux.default
];
}
];
};
};
}

by tonybtw.com

pkgs.writeShellApplication {
name = "ns";
runtimeInputs = with pkgs; [
fzf
nix-search-tv
];
text = builtins.readFile "${pkgs.nix-search-tv.src}/nixpkgs.sh";
}

By default, the configuration file is looked at $XDG_CONFIG_HOME/nix-search-tv/config.json

{
// What indexes to search by default
//
// default:
// linux: [nixpkgs, "home-manager", "nur", "nixos"]
// darwin: [nixpkgs, "home-manager", "nur", "darwin"]
"indexes": ["nixpkgs", "nixos", "home-manager", "nur", "noogle"],
// How often to look for updates and run
// indexer again
//
// default: 1 week (168h)
"update_interval": "3h2m1s",
// Where to store the index files
//
// default: $XDG_CACHE_HOME/nix-search-tv
"cache_dir": "path/to/cache/dir",
// Whether to show the banner when waiting for
// the indexing
//
// default: true
"enable_waiting_message": true,
// More about experimental below
"experimental": {
"render_docs_indexes": {
"plasma": "https://nix-community.github.io/plasma-manager/options.xhtml",
},
"options_file": {
"agenix": "<path to options.json>",
},
},
}

nix-search-tv can parse a documentation HTML page and extract options from it. How to tell if a page can be parsed? To understand that, check the links in the example below and if the documentation page looks exactly like one of them, it probably can be parsed.

{
"render_docs_indexes": {
// https://github.com/nix-community/plasma-manager
"plasma": "https://nix-community.github.io/plasma-manager/options.xhtml",
// Home Manager is also a valid page
// https://nix-community.github.io/home-manager/options.xhtml
},
}

The point of this search is to generate the options.json file at nix build time and point nix-search-tv to it. Internally, the tool compares previous and the new path and only re-indexes it if the path has changes.

{
"options_file": {
// https://github.com/ryantm/agenix
"agenix": "<path to built options.json>",
// https://jovian-experiments.github.io/Jovian-NixOS/index.html
"jovian": "<path to built options.json>",
},
}

Here’s one way to generate the options.json files for agenix and nixvim using unf and home-manager:

flake.nix
{
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
home-manager.url = "github:nix-community/home-manager";
agenix.url = "github:ryantm/agenix";
nixvim.url = "github:nix-community/nixvim";
unf = {
url = "git+https://git.atagen.co/atagen/unf";
inputs.nixpkgs.follows = "nixpkgs";
};
};
outputs = {
nixpkgs,
home-manager,
...
} @ inputs : let
# It's not required to use `unf`, but even though
# it brings some dependencies, I use it because its easy.
mkOpts = system: module:
inputs.unf.lib.json {
inherit self;
pkgs = nixpkgs.legacyPackages.${system};
# not all modules can be evaluated easily. If your module
# does not evaluate, try checking this NüschtOS file:
# https://github.com/NuschtOS/search.nuschtos.de/blob/main/flake.nix
modules = [module];
};
in {
nixosConfigurations.hostname = nixpkgs.lib.nixosSystem rec {
system = "x86_64-linux";
modules = [
home-manager.nixosModules.home-manager
{
# extraSpecialArgs is used here to pass the options files
# that depend on the flake inputs to home-manager modules,
# where configuration files are usually defined.
home-manager.extraSpecialArgs = {
inherit inputs;
agenixOptions = mkOpts system inputs.agenix.nixosModules.default;
# nixvim provides an options.json file already
nixvimOptions = inputs.nixvim.packages.${system}.options-json + /share/doc/nixos/options.json
};
}
];
};
};
}
# home.nix
{
pkgs,
lib,
...
} @ args : {
xdg.configFile."nix-search-tv/config.json".text = builtins.toJSON {
experimental = {
options_file = {
agenix = "${args.agenixOptions}";
nixvim = "${args.nixvimOptions}";
};
};
};
# or, with home-manager
programs.nix-search-tv = {
enable = true;
settings = {
experimental.options_file = {
agenix = "${args.agenixOptions}";
nixvim = "${args.nixvimOptions}";
};
};
};
}

Code and a demo here: https://github.com/3timeslazy/nix-search-tv/issues/20

Add nix-search-tv as an LLM agent skill

A niri shortcut to start nix-search-tv as a floating window

Mod+N { spawn-sh "ghostty --title=nix-search-tv -e path/to/nixpkgs.sh"; }
window-rule {
match title="nix-search-tv"
open-floating true
default-column-width { proportion 0.75; }
default-window-height { proportion 0.75; }
}

This project was inspired and wouldn’t exist without work done by nix-search contributors.