The agent has been failing to initialize its session state in approximately 50% of new sessions. This is not due to flaws in the AGENTS_STARTUP.md initialization file itself, but rather a failure to execute the file at all. The root cause is a lack of salience of the initial instructions within the agent's context window.
To solve this, we have replaced the previous instructions in .gemini/GEMINI.md with a new "FIRST ACTION PROTOCOL".
This new protocol is designed to be more robust by:
- Structural Positioning: Using a
STOP warning at the very top of the file to grab attention.
- Objective Detection: Providing a clear, verifiable check for Turn 1 (the absence of a
healthcheck tool call for the memory core).
- Imperative Framing: Using direct, unambiguous commands ("execute NOW", "Your first tool call must be...").
This change transforms the initialization from a passive, easily missed instruction into a direct, primary action. This ticket documents the implementation of this new protocol.
The agent has been failing to initialize its session state in approximately 50% of new sessions. This is not due to flaws in the
AGENTS_STARTUP.mdinitialization file itself, but rather a failure to execute the file at all. The root cause is a lack of salience of the initial instructions within the agent's context window.To solve this, we have replaced the previous instructions in
.gemini/GEMINI.mdwith a new "FIRST ACTION PROTOCOL".This new protocol is designed to be more robust by:
STOPwarning at the very top of the file to grab attention.healthchecktool call for the memory core).This change transforms the initialization from a passive, easily missed instruction into a direct, primary action. This ticket documents the implementation of this new protocol.