dy Install Libs is built to make installing libraries smooth and simple, with the stated goal of avoiding manual edits and broken installs. It ships as a shelf toolset for Houdini, aimed at the everyday stuff artists actually do: bring in a library, make sure it loads, and move on with their lives. The headline feature in v1.3 is Library Manager, a custom UI tool to download, install, enable, and disable local libraries. Version v1.3 is dated March 24, 2026, with a follow up v1.3.1 dated March 26, 2026.
The part you came for: Library Manager
Library Manager adds a single interface for discovering, installing, and managing open-source and commercial Houdini libraries. That matters because library installs rarely fail in exciting ways. They fail in slow, petty ways, like a missing file, a wrong path, or a package file that loads everywhere except the one machine that counts.
This release frames Library Manager as an evolution and combination of the earlier toolkit tools. The idea is simple: fewer trips into the filesystem, fewer chances to fat finger a package entry, and more time spent actually using the tools you installed.
There is also an explicit caveat: it may not work for installing render engines, since they typically require a custom JSON package file to set up environment variables and paths. In other words, the tool targets the library side of life, while heavyweight integrations can still demand a hand-tuned setup.
What dy Install Libs does around the manager
The toolkit includes several functions that cover the library lifecycle, from bringing in data to keeping package files aligned with where the library lives. Library from JSON imports a downloaded library using its JSON file and automatically copies and updates the package file in your library folder. This is the one for when a library arrives with its own packaging info and you want it to just land cleanly.
Install Library generates a new JSON package from scratch tied to your library folder. That means you can start from nothing and still end up with a package file that points where it should. Library from GitHub clones and installs libraries straight from a GitHub URL, which is handy when the library lives as a repo instead of a zip. It also supports downloading repository releases. That support is listed in v1.1 dated August 5, 2025.
Create Library builds a library scaffold with templates and auto-generates the package file, which aims at standardizing how a library starts its life on disk. Restart Houdini to reload everything with one click, when you want the tool to do the classic on-and-off ritual for you.
GitHub reality: releases, missing packages, and relative paths
Git based libraries come with their own quirks. The release notes for v1.1 include a fix for cases where a repo does not have a package file, replacing an older path JSON variable with hpath. It also adds support for relative paths using the $HOUDINI_PACKAGE_PATH variable in installed package files.
That combo matters because repos vary wildly in structure. Some ship a tidy package file. Some ship nothing but hope. Tooling that acknowledges those differences tends to be more usable in real production setups, where you do not control every library you need to install.
Small fix, big impact
v1.3.1 lists support for the enable key from package files when it appears as a string, while it should be a boolean. It also lists a URL key fix for when a library from a database is installed manually as a standalone library, along with small fixes and improvements.
Pricing and the practical bit
The tool is free to download, with a Gumroad listing shown as $0+. Pricing beyond that is pay what you tink it is worth.
Pipeline advice that still counts
Even if Library Manager makes installs feel effortless, new tools and innovations should be tested before use in porudction. Try it in a clean preferences setup first, confirm your package behavior matches expectations, and then let it anywhere near a show.
