Problem
The agent can fail to execute the mandatory session initialization process if the first user prompt is a simple greeting (e.g., "hi").
The agent's conversational model can override its procedural instructions, misinterpreting the greeting as a simple social cue rather than a formal prompt that should trigger the check defined in .gemini/GEMINI.md.
Proposed Solution
To make the check more robust and prevent this failure mode, we will add an explicit note to the Mandatory Pre-Response Check section of .gemini/GEMINI.md.
This change will clarify that the very first user utterance, regardless of content, must trigger the initialization procedure.
Change Details
Add the following text to the instruction:
**Note:** The very first user utterance after the initial context is loaded, no matter how simple (e.g., 'hi', 'ok'), is considered the first prompt and MUST trigger this check.
Ideal State
As discussed, the ideal solution would be to trigger the startup procedure before the user can enter their first prompt. However, assuming this is not currently feasible, the proposed change will make the existing pre-response check rock-solid.
Problem
The agent can fail to execute the mandatory session initialization process if the first user prompt is a simple greeting (e.g., "hi").
The agent's conversational model can override its procedural instructions, misinterpreting the greeting as a simple social cue rather than a formal prompt that should trigger the check defined in
.gemini/GEMINI.md.Proposed Solution
To make the check more robust and prevent this failure mode, we will add an explicit note to the
Mandatory Pre-Response Checksection of.gemini/GEMINI.md.This change will clarify that the very first user utterance, regardless of content, must trigger the initialization procedure.
Change Details
Add the following text to the instruction:
**Note:** The very first user utterance after the initial context is loaded, no matter how simple (e.g., 'hi', 'ok'), is considered the first prompt and MUST trigger this check.Ideal State
As discussed, the ideal solution would be to trigger the startup procedure before the user can enter their first prompt. However, assuming this is not currently feasible, the proposed change will make the existing pre-response check rock-solid.