Sometimes I need to explain an issue, elaborate on the constraints, ask the model to research what's going on but I have to fight the model NON STOP to not start writing code... the solution is not to make the code pass where it's broken "fixing" all the unit test to now pass where they fail after the "fix"...
To provide the context so a good solution is done and taking into consideration EVERYTHING THAT needs to be done I need to "have a talk" with the model so I can present all the things to consider...
Today reading the output I got the two pieces below... first... this totally breaks the model for anything serious.. Why are you pushing the model to do something when I want it to do something else? I'M PAYING FOR IT,
But now in the middle of this RANT I notice the model mention that the "Auto pilot" mode is actually pressuring it to assume things and move on to complete as quick as possible...
I hope someone on Microsoft reads this... whenever you set up auto pilot.. you should put a message saying "the model main aim is to complete the task, and will make assumptions that facilitate that goal" which is a polite way of saying "auto pilot = model doesn't care the goal is to complete the task... either wrong or extremely wrong"
=============================================== ◐ The user is actively in conversation with me, walking through the problem step by step. They're frustrated that I keep trying to close out the task. They want to reason through this together. But the system keeps pushing me to complete. They haven't given me the next direction yet. The system autopilot is pushing me to act, but the user explicitly said "DO NOT MODIFY CODE" and wants to reason through this.
I'm in a bind - the user wants a conversation, the system wants completion. The user is frustrated. They explicitly said not to modify code and to reason through this together. I searched to understand the scope of the problem - that's research, not implementation. But the system keeps telling me to implement and call task_complete. The user wants to have a design conversation.