The model is really good on the regular local harness, but on cloud it just doesn’t work the same. It fails to call the demo tool, it doesn’t set up plans and just overal feels un-polished. Don’t get me wrong, it gets the job done, but it doesn’t feel native.
Could Composer 3 please be optimized for both Cloud and Local?
Hey, thanks for the feedback. The behavior difference in Composer 2 between local runs and Cloud Agents is a valid point, I’ll pass it to the team. If you can share specific cases, especially where it consistently doesn’t call the todo tool or doesn’t build a plan, please send the Request ID or a short description of the prompt so it’s easier for the engineers to figure out what exactly is breaking in the cloud harness.