Skip to main content
Steer closes the loop on quality. It takes the scores Observe writes on your calls, plus the thumbs-up/down feedback your app sends, and uses them to pick the strongest few-shot examples and optimize your prompts. The more calls Observe scores, the better the signal Steer works from.

​
How it works

  • Quality scores. Every call an Observe rule judges gets a score and observation stored against it.
  • Feedback. Feedback you send from your SDK attaches a human signal to a call, alongside the judge’s scores.
  • Better outputs. Steer uses that signal to select few-shot examples from your top-scoring calls and to tune the prompt, so quality climbs as more calls come in.

​
The loop in practice

  1. Score the calls you care about with an Observe rule, and send thumbs-up/down feedback from your app where you have it.
  2. Accumulate signal. As scored calls and feedback build up, Steer learns which responses are your strongest.
  3. Improve. Steer selects few-shot examples from the top-scoring calls and tunes the prompt, so later calls to the same function start from better material.
  4. Watch it climb. Because Observe keeps scoring, you can see quality trend up over time in Analytics.
Steer works best on functions you call repeatedly with a consistent task — exactly the calls where a few good examples pay off on every request.

​
Requires Observe

Steer runs on the scores the Observe judge produces, so you need at least one Observe rule scoring the calls you want to improve. Once it’s scoring, open Controls → Steer to manage it.
Score the calls you care about with Observe and send feedback from your SDK. The more signal Steer has, the better the examples and prompts it picks.