Skip to main content
Training supports two methods: supervised fine-tuning (SFT) and prompt gisting. Both learn from conversations, but they solve different problems and produce different artifacts.

Compare the methods

Both methods publish a downloadable Model Version. The platform does not host or serve that Model Version.

Choose SFT

Choose supervised fine-tuning when examples should teach a model how to respond or classify. Each row ends with the assistant output the model should learn, such as a support-ticket label or a complete answer. SFT is also the method to use when:
  • You need a LoRA adapter rather than a full model.
  • You need one of the larger qwen3-32b or qwen3-235b Base models.
  • You want to continue adapting an earlier LoRA adapter.
SFT is the CLI default. You do not pass --method when creating an SFT Training.

Choose gisting

Choose gisting when the reusable part of the task is a long, static instruction prompt. Gisting learns soft tokens from that prompt and the example conversations. The dynamic user input stays in each conversation. Gisting is also the method to use when:
  • Prompt compression is the goal, rather than adapting model weights for a new response behavior.
  • You can use qwen3-4b or qwen3-8b.
  • You need a full Model Version rather than a LoRA adapter.
A gisting Training always needs --method gisting and --prompt-file.

Use the right product surface

Use the CLI or HTTP API for project Training. The web app’s Fine-tuning and Prompt gisting pages help you set up a coding agent. Fine-tune lab, where available, has separate runs and downloads; see Ways to work with Training.

Next steps