@quick-window-91705 I'd love your 👀 on this: https://github.com/OpenHands/OpenHands/pull/12983 If the PR code doesn't look good, by all means we can give it up - I do think we need to fix the underlying issue

Code LGTM! Although if I recall previously we'd made the decision to move resolver related instructions out of the user message, because it felt misleading (user sent one message and sees a bunch of other things in the UI) If UX seems ok we can merge this

Unfortunately LLMs APIs still don't have another

role

that we could use here, like `environment message`` But the UI can adapt and display differently. Do you mean the PR needs to wait until someone tests it on staging?

I'll test it in the next day or so and merge it!

Thank you, I appreciate it! We can iterate on the way it looks, but the LLM receiving a too strong instruction makes the resolver difficult to use - which is UX lolsob