[Feature] Model Setting Presets

[hernstev97]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

This discussion touches a similar need but is different enough that I opened this thread.

Area

• Desktop/Web
• Mobile (if demand is there)

Problem or use case

The default model and reasoning level for a project can be set already. But what if you frequently change between that and some different settings? When you use multiple models, settings, speed settings and access levels this can quickly become slightly tedious.

Proposed solution

A small preset picker in the chat header, possibly to the left of the actions picker. This would just be a dropdown with the currently saved options and an option to save the current settings into the preset picker.

Here is how I believe this could be approached:

interface ComposerPreset {
  id: string;
  name: string;
  modelSelection: ModelSelection;
  runtimeMode: RuntimeMode;
}

The parts already seem to exist. ModelSelection already exists, as well as RuntimeMode. These would just be included in this ComposerPreset interface. We can then save the composerPresets into ServerSettings with [] as a default. We need to add it into ServerSettingsPatch as well.

Why this matters

In a single interaction this is only a tiny time saver. But over time - and especially as more varied settings are being used - this can save quite a bit of time. It doesn't enforce itself onto the user but is just a nice option.

Smallest useful scope

Keep it environment scoped. One machine has one list of presets, they are not shared automatically. Also don't apply it on a per project basis. Only one set of presets throughout the entire t3code instance. This keeps the UI surface small and avoids introducing project-level preset management or syncing.

Alternatives considered

• A small button inside the composer
• A setting in the settings view

Risks or tradeoffs

As far as i can see almost none, but this is my first interaction with the codebase. The one trade off I see is less space available in the chat header which could be a concern depending on planned/future features touching that space.

Examples or references

Implemented it could look like this (images altered by ChatGPT):
Preset selector button:

Dropdown open:

Contribution

• I would be open to helping implement this.