Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix bug report requested by app. [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#25566•Fetched 2026-04-17 08:55:03
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
daveylongshaftdaveylongshaft
Participants
daveylongshaftdaveylongshaftgemini-cli[bot]gemini-cli[bot]
Timeline (top)
labeled ×3commented ×1

Error Message

│ This is an unexpected error. Please file a bug report using the /bug tool. █│ │ Reason: Error: Custom plans directory 'c:\csc\ops\plans' resolves to 'c:\csc\ops\plans', which is outside the █│ │ Error: Custom plans directory 'c:\csc\ops\plans' resolves to 'c:\csc\ops\plans', which is outside the project █│

RAW_BUFFERClick to expand / collapse

What happened?

                                                                                                                  │

│ ℹ Detected terminal background color: #0c0c0c │ │ │ │ ✖ ========================================= │ │ This is an unexpected error. Please file a bug report using the /bug tool. █│ │ CRITICAL: Unhandled Promise Rejection! █│ │ ========================================= █│ │ Reason: Error: Custom plans directory 'c:\csc\ops\plans' resolves to 'c:\csc\ops\plans', which is outside the █│ │ project root 'C:\Users\davey'. █│ │ Stack trace: █│ │ Error: Custom plans directory 'c:\csc\ops\plans' resolves to 'c:\csc\ops\plans', which is outside the project █│ │ root 'C:\Users\davey'. █│ │ at _Storage.getPlansDir █│ │ (file:///C:/Users/davey/AppData/Roaming/npm/node_modules/@google/gemini-cli/bundle/chunk-ETUADTWF.js:42413:15) █│ │ at Config._initialize █│ │ (file:///C:/Users/davey/AppData/Roaming/npm/node_modules/@google/gemini-cli/bundle/chunk-ZTFHMKKJ.js:350264:37) █│ │ at async █│ │ file:///C:/Users/davey/AppData/Roaming/npm/node_modules/@google/gemini-cli/bundle/interactiveCli-EOCVNM6H.js:4791█│ │ 6:9 █│ │ ℹ Authenticated via "oauth-personal".

What did you expect to happen?

the console did not respond, pressed tab twice and got the above message. no reply needed. good day

Client information

  • CLI Version: 0.38.1
  • Git Commit: 7f5580034
  • Session ID: 538581cd-6a49-407c-bf62-1e23a174c08b
  • Operating System: win32 v24.13.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-2.5-flash-lite
  • Auth Type: oauth-personal
  • Memory Usage: 275.5 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue is likely due to the custom plans directory being outside the project root, and a workaround may involve adjusting the project root or the custom plans directory path.

Guidance

  • Verify the project root directory is set correctly, as the error message indicates a mismatch between the project root 'C:\Users\davey' and the custom plans directory 'c:\csc\ops\plans'.
  • Check the configuration for the custom plans directory to ensure it is set to a path within the project root.
  • Consider adjusting the project root or the custom plans directory path to resolve the issue.
  • Review the documentation for the @google/gemini-cli package to see if there are any specific requirements or restrictions for setting the project root and custom plans directory.

Notes

The issue seems to be related to a configuration or setup problem, and resolving it may require adjusting the project structure or configuration settings. Without more information about the project setup and configuration, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Adjust the project root or custom plans directory path to ensure they are compatible, as this is likely to resolve the issue.

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…
#vector store#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING