ReasoningEffort
How hard to think, and how much of that budget the run actually spent.
Install it:
npx shadcn add @ambientui/reasoning-effortLive
Behavior
- ·The control and the meter belong together: an effort setting with no spend reading is a preference with invisible consequences.
- ·A radiogroup, not a slider — the levels are named tiers, and a continuous control would imply precision the model does not offer.
- ·The meter fills on the surface motion role, so a spend that climbs during a run reads as accumulation rather than a jump.
- ·Omit spent/budget and the meter disappears; the control alone is still valid.
When to use
- ·Wherever the user pays for thinking — in tokens, in latency, or in both.
- ·In settings AND beside a run, so the choice can be learned from its result.
When not to
- ·When effort makes no observable difference; a control with no consequence teaches the user to ignore controls.