ahmadassaf

Years ago I forked bash-it into gaudi-bash and rewrote large parts of it, cleaner architecture, async theme rendering, better component management, and a curated set of plugins that actually work well together. It became my daily driver for bash.

Then I started using zsh more. And I hit a gap.

The zsh ecosystem has plenty of frameworks and plugin managers oh-my-zsh, prezto, antidote, zinit, zplug, sheldon, zgenom, antigen, among others. But they all solve a different problem: they manage zsh-specific plugin installation and loading. None of them give you the workflow I was used to; an intuitive enable plugin fzf / disable alias git CLI, symlink-based component management, profiles to save and switch configurations, or a single search command to find what's available across aliases, plugins, and completions. And critically, none of them work across shells.

On the bash side, the options are even more limited. bash-it (which gaudi-bash forked from) is essentially the only framework with a comparable component management approach.

I found myself context-switching between two completely different mental models depending on which shell I opened. Different config patterns, different commands, different plugin ecosystems.

gaudi-shell closes that gap. One framework, one CLI, one set of components across bash and zsh.

pinning the version is the way to go with at least for now. Github Actions not supporting lockfiles is a huge missing feature