[Feature] Model Management in Unsloth Studio - Delete & Update Models
#5098 opened on Apr 18, 2026
Description
Apologies if this has been mentioned, I tried searching both open and closed issues and couldn't find something similar.
Is your feature request related to a problem? Please describe. There's no obvious way to delete models in Unsloth Studio. Once you download a model, it just sits there and you have to go digging in the filesystem to get rid of it, which kind of defeats the purpose of having a UI in the first place.
The other issue is updates. When a new model drops like Qwen3.5 or Gemma4, the first few weeks are always a bit chaotic. Quantizations get fixed, inference bugs get patched, configs get sorted out, and there are usually multiple revision bumps on Hugging Face in quick succession. Right now there's no way to know if what you downloaded is already stale, and the only way to get a newer version is to manually re-download it. I ran into this a lot with Qwen3.5 specifically and ended up downloading it multiple times in a short window.
Describe the solution you'd like Two things:
- Delete models - a simple delete button on each model in the model list. A confirm dialog is totally fine, just something that lets you remove a model from within the UI without having to hunt it down on disk.
- Update models - a way to check if a newer revision is available and pull it down. Even something basic like a "check for updates" button per model, or an indicator when your local version is behind what's on Hugging Face, would be really useful. Ideally it replaces the existing download in place rather than creating a duplicate.
Describe alternatives you've considered Manually deleting from the filesystem and re-downloading through the UI. It works but it's clunky, and it's easy to lose track of what version you actually have installed.
Additional context The update use case feels especially relevant right now given how fast new models are moving. It's pretty common to grab a model on day one and have it be meaningfully different from what's available a week later. Having some visibility into that and an easy way to refresh would save a lot of manual back and forth.