Hey! Our primary objective for now is to provide the open source community with cool and useful tooling - we found closed source to be much more popular because of better tooling!

We have much much in the pipeline!!

Some of it is Apache

Hey will check ASAP and fix - sorry about that

Agree with you, a slightly more maintainable way to use it now is with "uv" or mise. i've used `uv tool install unsloth` for this one.

Hey we're still working on making installation much better - appreciate the feedback!

We come from Python land mainly so packaging and distribution is all very new to us - homebrew will definitely be next!

I recommend installing uv first, then you can install any Python code you want inside a virtual environment to keep it isolated from the rest of the system.

Uv helps you up though. Use a pyproject.toml and uv sync. Everything will be put into the venv only, nothing spread across the whole system.

The pyproject.toml can even handles build env for you, so you no longer need a setup.sh that installs 10 tool in specific order with specific flag to produce working environment. A single uv sync, and the job is done.

Plus the result is reproducible, so if this time uv sync work, then it also work next time.

Highly recommend if you are still on pip.

Note: Take a example that I used to install unsloth with rocm setup that based on unreleased git version dependencies and graphic card specific build flag, all of them can be handled with one command 'uv sync'. This will require a big pile of shell script if doing another way. https://github.com/unslothai/unsloth/issues/4280#issuecommen...

Would pipx solve the problem?

https://pipx.pypa.io/stable/installation/

Ah yes, came to say something similar, Python dependencies are an absolute nightmare, even with uv it feels like there's always a battle to make other peoples Python apps install.

Update: It looks like it doesn't work with the current Python version, you might have to downgrade to Python 3.13 (however even then I still get `error: unexpected argument '--torch-backend' found`)

I know the whole package system across most languages is a dumpster fire but for Python, uv solves a lot of problems.

uv init

uv add unsloth

uv run main.py % or whatever

On my linux systems I use venv to not affect system packages, is that not an option for this situation?

Agreed, feels like a vibe-coded frontend based on already given backend features.

Also, never saw any Unsloth related software in production to this day. Feels strongly like a non-essential tool for hobby LLM wizards.

Oh will check and fix - thanks

Thank you! We're still iterating on it so any suggestions are welcome!

Thank you for your continued support - we have much more planned for it!

IDK how it did but it detected my LM studio downloaded models I have on a spinning drive (they're not in the default location).

You would be surprised! Nearly every Fortune 500 company has utilized either our RL fine-tuning package or used our quants and models - the UI was primarily a culmination of pain points folks had when doing either training or inference!

We're complimentary to LM Studio - they have a great tool as well!

you just answered your own question, "AI hobbyists who has 4090 at home". And they are pretty much targeted user of Unsloth since the start.

From the homepage looks like it: “Training: Works on NVIDIA GPUs: RTX 30, 40, 50, Blackwell, DGX Spark/Station etc.”

I am unaware lm studio is being used for fine tuning. I believe it only does inference.

Happy to see unsloth making it even easier for people like me to get going with fine tuning. Not that I am unable to I'm just lazy.

Fine tuning with a UI is definitely targeted towards hobbyists. Sadly I'll have to wait for AMD ROCm support.