-
Notifications
You must be signed in to change notification settings - Fork 10k
Open
Labels
area/agentIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent QualityIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Qualitypriority/p3Backlog - a good idea but not currently a priority.Backlog - a good idea but not currently a priority.
Description
What happened?
I fairly consistently see Gemini CLI commit its own changes after running npm run preflight in this repository. While there is nothing functionality wrong with this, I don't think it's the ideal UX.
What did you expect to happen?
Ideally changes would be staged, but left uncommitted, making it seamless for the developer driving Gemini CLI to review the staged changes before committing them.
I personally use VS Code OSS based editor's line-by-line accept/reject of changes in the diff view to do a final quality pass prior to committing anything.
Client information
Client Information
Run gemini to enter the interactive CLI, then run the /about command.
> /about
│ │
│ About Gemini CLI │
│ │
│ CLI Version 0.20.2 │
│ Git Commit af894e468 │
│ Model auto │
│ Sandbox no sandbox │
│ OS darwin │
│ Auth Method gemini-api-key │
│ IDE Client Login information
Authenticated with API key.
Anything else we need to know?
No response
Metadata
Metadata
Assignees
Labels
area/agentIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent QualityIssues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Qualitypriority/p3Backlog - a good idea but not currently a priority.Backlog - a good idea but not currently a priority.