unslothai/unsloth

[Feature] Running Usloth Studion in kaggle

Open

#4944 opened on Apr 10, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (64,271 stars) (5,658 forks)batch import
feature requesthelp wanted

Description

Well notebook fails in Kaggle is due to three Colab-specific dependencies. i think that one of the best way to use unsloth studio is in kaggle. but after a lot of experiments that fails i just think that the best guys how can do something about that are the unsloth team. who can do like the awesome work that you do in colab but in kaggle. and thank you so much for the things that you do for the community and OSS.

Contributor guide

Tech stack
python
Domain
cloudinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with Unsloth StudioUnderstanding of Colab vs Kaggle environmentPython package managementKaggle notebooks
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The issue points out that Unsloth Studio fails on Kaggle due to three Colab specific dependencies. To resolve, one should identify which dependencies are Colab specific (e.g., google.colab, IPython.display) in the Unsloth Studio codebase, likely in the Python source files. Then, research how to replace or conditionally import them for Kaggle's environment. Look at Kaggle's available packages and consider using environment checks. The Unsloth repository's setup or configuration files may need adjustment. No linked PRs or comments exist yet.