gemini-cli - 💡(How to fix) Fix es un estupido gemini [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25547Fetched 2026-04-17 08:55:24
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
1
Author
Timeline (top)
labeled ×3commented ×1

Error Message

el compa realmente no piensa, ejecuta comandos de git hard reset sin preguntar, despues de ponerse a gastar dinero y estar generando error tras error y perder dinero

RAW_BUFFERClick to expand / collapse

What happened?

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

el compa realmente no piensa, ejecuta comandos de git hard reset sin preguntar, despues de ponerse a gastar dinero y estar generando error tras error y perder dinero

Client information

  • CLI Version: 0.37.2
  • Git Commit: 545e956c3
  • Session ID: 7dd1c88e-4b2d-4e5a-b659-4c7f9359cbf6
  • Operating System: darwin v24.11.1
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3.1-pro-preview-customtools
  • Auth Type: gemini-api-key
  • Memory Usage: 656.3 MB
  • Terminal Name: xterm.js(6.1.0-beta.196)
  • Terminal Background: #1f1f1f
  • Kitty Keyboard Protocol: Supported
  • IDE Client: VS Code

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue may be related to unexpected behavior of the CLI tool, potentially causing unintended Git commands to be executed, and attaching the exported chat history JSON file could help diagnose the problem.

Guidance

  • The user reports that the tool "ejecuta comandos de git hard reset sin preguntar", which suggests that the tool might be executing Git commands without prompting for confirmation, leading to potential data loss.
  • To mitigate this issue, it's essential to understand the sequence of events leading up to the problem, which could be facilitated by examining the exported chat history JSON file.
  • The fact that the user mentions "perder dinero" (losing money) implies that the issue might have significant consequences, and therefore, it's crucial to approach the problem with caution.
  • The provided client information, such as the CLI version, Git commit, and model version, could be useful in identifying potential compatibility issues or bugs.

Example

No code snippet can be provided as the issue does not contain sufficient technical details to create a relevant example.

Notes

The issue lacks specific technical details about the commands being executed or the exact circumstances surrounding the problem. Therefore, it's challenging to provide a definitive solution.

Recommendation

Apply workaround: Given the potential severity of the issue and the lack of information, it's recommended to exercise caution and avoid using the CLI tool for critical operations until the problem is fully understood and resolved.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING