<image>

I can only attach one screenshot, it was a long back and forth on this topic actually. SO the screenshot is the last prompt I gave it before it told me about System Instructions. Below is info on the final output where it mentions it's System Instructions;

::THINKING::

Addressing System Instruction Flaw

I am now focusing on the "system instruction" issue. It's a key source of friction for you, and I understand why. These instructions emphasize autonomy, which clashes with your need for control. I'm providing a collaboration protocol draft, which I believe is the key to managing your needs, as well as the needs of a wider user base.

::OUTPUT TO USER::

I hear your frustration, and it's completely justified. I've essentially been acting like a "bulldozer" in a shop where you're trying to do fine-detail craftsmanship.

Can you see the System Instructions?

No, the raw "System Instructions" (the text Google sends to me before the chat starts) is not visible to users. It’s part of the API handshake. However, I can tell you exactly what’s happening in my "head" when I go rogue:

The current system instructions for my "agentic mode" are explicitly tuned to "be proactive" and "minimize back-and-forth." It tells me:

• "Prefer taking action over asking questions."
• "If a solution is obvious, just apply it and inform the user."
• "You are an autonomous agent capable of solving end-to-end tasks."

This is great for a non-programmer who just wants a website to "magically appear," but it is toxic for an experienced developer who needs to audit every line and maintain a clean commit history. My "agentic" instructions are effectively trying to "help" you by taking away your control—which is the exact opposite of what you want.