gemini-cli - 💡(How to fix) Fix Metapharsic Lifesciences ERP [1 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#25407Fetched 2026-04-15 06:44:52
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

What happened?

for the entire erp .

[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?

it should be bug free

Client information

  • CLI Version: 0.37.2
  • Git Commit: 545e956c3
  • Session ID: 0f866d25-55a4-4856-9bce-645561c484e8
  • Operating System: win32 v25.6.1
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 259.7 MB
  • Terminal Name: Unknown
  • Terminal Background: Unknown
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue is likely related to a bug in the current version of the CLI, and attaching the exported chat history JSON file may help diagnose the problem.

Guidance

  • The provided information suggests a potential issue with the current CLI version (0.37.2) or the auto-gemini-3 model version, but without more context, it's difficult to pinpoint the exact cause.
  • To help diagnose the issue, attaching the exported chat history JSON file as requested may provide valuable insights.
  • Reviewing the Git commit history (specifically commit 545e956c3) may also offer clues about recent changes that could be contributing to the problem.
  • Consider checking for any known issues or updates related to the CLI version, model version, or auth type (oauth-personal) that may be relevant to this problem.

Notes

The lack of information about what specifically happened or what was expected to happen makes it challenging to provide a more detailed analysis or solution. The guidance provided is based on the assumption that the issue is related to the CLI or model version.

Recommendation

Apply workaround: Since the issue is likely related to a bug, and without a clear path to a fix, the best course of action is to apply any available workarounds or patches for the current CLI version (0.37.2) and model version (auto-gemini-3), and to share the exported chat history JSON file for further diagnosis.

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