This ticket documents the implementation of a robust, automatic initialization process for Gemini agents within the repository. The goal is to ensure the agent follows the instructions in AGENTS.md at the start of every session.
The solution uses the CLI's default context-loading mechanism to provide a persistent "pre-flight checklist" to the agent on every turn.
- A new file,
.gemini/GEMINI.md, was created with a "Mandatory Pre-Response Check" that instructs the agent to read and perform the AGENTS.md initialization if it hasn't already done so in the current session.
- This file also includes a summary of the most critical enforcement rules (e.g., Ticket-First, Memory Core) to reinforce them on every turn.
- The
.gemini/settings.json file remains unchanged, as GEMINI.md is the default context file name and is loaded automatically.
This approach ensures that the agent will always perform the correct initialization sequence upon receiving the first user prompt of a session.
This ticket documents the implementation of a robust, automatic initialization process for Gemini agents within the repository. The goal is to ensure the agent follows the instructions in
AGENTS.mdat the start of every session.The solution uses the CLI's default context-loading mechanism to provide a persistent "pre-flight checklist" to the agent on every turn.
.gemini/GEMINI.md, was created with a "Mandatory Pre-Response Check" that instructs the agent to read and perform theAGENTS.mdinitialization if it hasn't already done so in the current session..gemini/settings.jsonfile remains unchanged, asGEMINI.mdis the default context file name and is loaded automatically.This approach ensures that the agent will always perform the correct initialization sequence upon receiving the first user prompt of a session.