subagent: compare haiku max to sonnet on low, and warn that sonnet defaults to high
This commit is contained in:
parent
a1f1f04657
commit
b2e3b05198
1 changed files with 6 additions and 5 deletions
|
|
@ -62,10 +62,11 @@ well-scoped batch (the shape this skill is for), reach for it liberally
|
|||
rather than defaulting to a bigger model "to be safe." On a small context
|
||||
Haiku costs next to nothing up to `high` effort, so there's no cost reason
|
||||
to cap its effort at `medium` by reflex. Effort is a real lever on Haiku
|
||||
though: at `max` it behaves like a slightly weaker Sonnet at about Sonnet's
|
||||
cost, so `max` on Haiku buys nothing over picking Sonnet. Stay at `high` or
|
||||
below, and move to a stronger model when the batch needs more judgement
|
||||
(see Pitfalls below).
|
||||
though: at `max` it behaves like a slightly weaker Sonnet at about the cost
|
||||
of Sonnet on `low`, so `max` on Haiku buys nothing over Sonnet on `low`.
|
||||
Stay at `high` or below, and move to a stronger model when the batch needs
|
||||
more judgement (see Pitfalls below). When you do pick Sonnet, pass `low`
|
||||
yourself: its default effort is `high`, a big price bump.
|
||||
|
||||
This isn't "always pick the smallest model regardless of task" — a batch
|
||||
that actually needs judgement calls still wants a stronger model (see
|
||||
|
|
|
|||
Loading…
Reference in a new issue