Skip to content

Gemini CLI follows system-level instructions (No Overview & Minimal Output) too strictly with regards to documentation #15547

@GoddessZenith

Description

@GoddessZenith

What happened?

Gemini CLI ignored explicit user defined instructions to add # Overview headers to markdown files.

Gemini CLI ignores explicit user defined instructions for stylistic requirements for documentation.

What did you expect to happen?

Gemini CLI follows explicit user defined instructions to add # Overview headers to files.

Gemini CLI follows explicit user defined instructions for stylistic requirements for documentation.

Client information

  • CLI Version: 0.22.2
  • Git Commit: 9bc9a31
  • Session ID: ccaf4ad9-b0c6-47b6-9f94-4e1eaeb006ca
  • Operating System: win32 v22.21.1
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3-flash-preview
  • Memory Usage: 1.17 GB

Login information

No response

Anything else we need to know?

I strongly believe that the No Overview rule is being misinterpreted, or is being misapplied to documentation within the environment of CLI. Please update the system-level rules to not affect documentation adversely.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/agentIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Quality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions