tempusfrangit

100% agree. They are complimentary. Brew handles specific things far better and mise handle polygot and some things where many versions need to been handled on the same system.

But my list of brew items keeps getting shorter.

You can also tell Claude to either run everything mise x or refresh its shell and it will do the zsh re-exec and that reloads the mise shims consistently.

These days also trivial to restart Claude ;)

I just added a post-checkout hook for my team:

`mise trust`

Resolves that trust issue right away and is scoped to your repo (not global). We also have a make setup that helps the folks still doing make things get all setup and trusted on the main work tree.

At a past job we had a local `doctor` script that did this.

I am a huge advocate of mise and all the en suite.

Two jobs in a row I’ve migrated most of our workflows to using mise. Thanks for the amazing work (and I finally get to sponsor the project!)

Mise and Brew are a powerful pairing.