One latent issue, explicitly not a default-path cause
buildPromptContext calls getFolderStructure(cwd) per request with no memoization and injects the result into the cached system block (packages/core/src/core/prompts.ts:429-442). A live directory listing inside BP1 means a coding agent invalidates its own cache every time it creates or deletes a file.
However, includeFolderStructure initializes to false and requires the include-folder-structure setting, so this does not explain default-path burn. Flagging it as a real hazard for anyone who enables it, not as the root cause.
This is a vestigial part of gemini-cli we disabled long ago
One latent issue, explicitly not a default-path cause
buildPromptContext calls getFolderStructure(cwd) per request with no memoization and injects the result into the cached system block (packages/core/src/core/prompts.ts:429-442). A live directory listing inside BP1 means a coding agent invalidates its own cache every time it creates or deletes a file.
However, includeFolderStructure initializes to false and requires the include-folder-structure setting, so this does not explain default-path burn. Flagging it as a real hazard for anyone who enables it, not as the root cause.
This is a vestigial part of gemini-cli we disabled long ago