Presets

A preset is a named bundle of request defaults: model parameters (temperature, top-p, max tokens, …) and a system prompt. Presets live in your account.

Available now in the dashboard. Go to Settings → Presets (/dashboard/settings/presets) to save your current Chat parameters and system prompt as a named preset, then Apply it to load those settings into the chat in one click. You can keep several presets and delete any of them.

Why presets#

Without presets, every session carries the full configuration:

{
  "model": "anthropic/claude-opus-4.8",
  "temperature": 0.2,
  "max_tokens": 1024,
  "messages": [
    { "role": "system", "content": "You are a customer support agent for an e-commerce store. Reply in the user's language — Arabic, French, or English. Be concise." },
    { "role": "user", "content": "..." }
  ]
}

With a preset named support-agent, you set that configuration once and apply it whenever you need it. Change the model or tweak the system prompt once in the preset — every session using it picks up the update immediately.

Creating a preset#

Presets are managed from Settings → Presets: open Chat, set the parameters and system prompt you want, then save them under a name from the Presets page. Apply loads a preset back into the chat.

Preset fields#

Referencing a preset in an API request#

Not yet available. A "preset": "<name>" request field — expanded server-side so your code carries only the preset name while explicit request values win — is tracked to be built. Until it ships, the field is ignored: keep sending full request configuration from your code.

Best practices#

• One preset per use case. Give each distinct product feature or application component its own preset so you can tune them independently.
• Keep system prompts in presets, not in code. This lets you iterate on prompt wording without touching code or redeploying.
• Name clearly. Use descriptive names like support-ar, summariser-short, code-review-strict rather than preset-1.