Very cool.
Curious if the results are better for certain domains vs others and if there's a sweet spot in terms of number of turns in the convos.
What have you seen deploying this in the wild so far?
We’re actively looking for more use cases because we want to understand where the approach breaks down.
We haven't seen a clear domain specific sweet spot yet. What surprises us is that it becomes seems to get better as the complexity / turn count increases.
It adopts very well to multi turn sessions, scheduled runs and even trigger based Agentic systems that don't involve human in the loop.
We don’t yet have enough data to say something like “10–20 turns is optimal,” though. That’s one of the things we’re hoping to learn as we get it into more production systems.