{{ message }}
Repository navigation
Studio: save a model's run settings without loading it - #10216
Merged
danielhanchen merged 15 commits intoSep 29, 2026
Merged
Conversation
NilayYadav
requested review from
Imagineer99 and
shimmyshimmer
as code owners
September 2, 2026 20:03
NilayYadav
force-pushed
the
save-settings-without-load
branch
from
September 2, 2026 20:04
a09d5bf to
1301cf7
Compare
NilayYadav
force-pushed
the
save-settings-without-load
branch
from
September 2, 2026 20:13
93c6fc2 to
0855d07
Compare
NilayYadav
force-pushed
the
save-settings-without-load
branch
from
September 7, 2026 14:25
725c63a to
3b2acad
Compare
This comment has been minimized.
This comment has been minimized.
for more information, see https://pre-commit.ci
This was referenced Sep 10, 2026
danielhanchen
added a commit
to Datta0/unsloth-staging-3
that referenced
this pull request
Sep 10, 2026
Member
Resolve conflicts with main's footer rework (primary action first, pill buttons) and the reasoning-budget reset options on syncModelOverride. Save settings now sits between Load and Reset in a stacked footer for both variants. Forget settings is no longer disabled by unloadable llama arguments, since it only deletes the stored entry. The reset step in the picker suite uses main's click_and_wait_for_commit instead of waiting for the native context, which never arrives when auto-fit caps it.
danielhanchen
pushed a commit
to danielhanchen/unsloth-staging-2
that referenced
this pull request
Sep 29, 2026
# Conflicts: # tests/studio/playwright_model_config.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Fixes #10168.
The run settings panel only let you save settings as part of loading the model. If you wanted to set up a model ahead of time, you had to load it every time.
This adds a Save settings button next to Load model. It stores the settings for that model, including the copy the API uses for its own loads, and leaves the model unloaded. The footer now wraps in the picker so the "Remember for this model" label is not cut off.
Tested in the browser against a fresh install of main and this branch. On main the button does not exist and nothing is saved. On this branch clicking it shows "Settings saved.", the server has the new settings, and the model stays unloaded.
Before / after
Run settings for an unloaded on-device GGUF (
gemma-3-270m-it-GGUFUD-Q4_K_XL), merge base7617fc398vs head332ed632e. Before, the footer only offers Load model and Reset. After, Save settings sits between them; clicking it shows "Settings saved.", stores the config, and no model is loaded.