> ## Documentation Index
> Fetch the complete documentation index at: https://goldengoose.zue.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Model Presets

> Use named presets to add team members quickly and keep roles consistent.

Model presets are **named shortcuts** that describe how to spin up a team member: which model to use (and, when supported, how much “thinking effort” to allocate).

Presets exist to make team composition repeatable. Instead of re-picking the same model settings over and over, you pick **“planner”** or **“frontend”** and get a consistent setup.

## When presets are used

* Adding members to a team (especially when you want quick “specialist” threads).
* Creating repeatable team templates (“always add a reviewer + docs helper”).

You can still override model choices per thread — presets are convenience, not a restriction.

## Default presets (shipped with gg)

gg ships with a small set of defaults you can customize:

* `planner` → `gpt-5.3-codex` (effort: `high`)
* `designer` → `claude-opus-4-6` (effort: `high`)
* `frontend` → `gpt-5.3-codex` (effort: `high`)

These are starting points — the “right” presets depend on your workflow.

## Thinking effort (what it means)

Some providers/models support an effort/depth setting (often `low`, `medium`, `high`).

In practice:

* Higher effort can improve planning and correctness, but usually costs more and takes longer.
* Lower effort can be great for routine edits, refactors, and quick iterations.

If a provider/model doesn’t support effort, gg will ignore the field.

## Best practices

* Create presets for your real roles: `reviewer`, `docs`, `refactor`, `infra`, `tests`.
* Keep names short and “typeable” — they often show up in tool surfaces.
* Prefer a small curated set (3–8) rather than dozens.