The Modelfile editor

Opens in the same window as the chat, with the chat list still visible, so tuning never loses your place.

Form and raw, side by side

The editor shows two views of the same Modelfile:

• Form — the common fields, each labelled with the Modelfile keyword it maps to: base model (FROM), system prompt (SYSTEM), temperature and top-p (PARAMETER), context length (PARAMETER num_ctx), stop sequences, and the template.
• Raw — the exact Modelfile text sent to ollama create.

The raw text is the source of truth; the form is a projection of it. Editing a form field regenerates only the lines it owns — comments, LICENSE, ADAPTER, MESSAGE and anything else the form doesn't model round-trip byte for byte. Editing the raw text re-parses into the form. Content the form can't represent is never silently dropped.

Save and Save as…

Save overwrites the current model's Modelfile. Save as… asks directly for a name and a directory, writes the Modelfile there, and registers a new tuned variant with ollama create <name> -f <path> — optionally quantising on the way in. A tuned variant is a real, editable file on disk, not just an opaque entry in ~/.ollama.

Either action then stops the running model and reloads it with the new Modelfile — create, unload, warm request — shown as a "stopping → reloading" toast. The reloaded model becomes the loaded model, so any open or new chat uses it immediately.

Revert discards unsaved edits back to the last-loaded Modelfile.

Modelfile history

Every successful save writes a snapshot: the raw text, what changed since the previous snapshot, and whether it came from a Save or a Restore. The history pane shows a timeline on the left and a diff against the previous snapshot on the right.

If a Modelfile was hand-edited outside Remuda, the history notes the drift rather than pretending its own record is complete.