Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix Unable to use custom plan directories [2 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#26187•Fetched 2026-04-30 06:44:44
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
RobloxScripter-1RobloxScripter-1
Participants
jeropjeropRobloxScripter-1RobloxScripter-1
Timeline (top)
commented ×2closed ×1labeled ×1mentioned ×1

Error Message

When the plan_directory is set to a custom path (e.g., ~/.gemini/plans/), the application should successfully initialize, write, and read plan files from that specific location without returning an error, provided the directory exists and has the correct write permissions.

Code Example

> /about
# paste output here
 About Gemini CLI                              │
│                                               │
│ CLI Version     0.40.0                        │
│ Git Commit      3d5bdc052                     │
│ Model           gemini-3.1-flash-lite-preview │
│ Sandbox         no sandbox                    │
│ OS              linux                         │
│ Auth Method Signed in with Google             │
│             ()           │
│ Tier          Gemini Code Assist for          │
│               individuals
RAW_BUFFERClick to expand / collapse

What happened?

When I put the directory .gemini/plans (custom directory I made) it didn't work even tho Gemini made the file in it when I removed the directory making it set to default well it starting working Repro Steps Make a custom directory in .gemini and set the plan directory to it and ask Gemini to make a plan

What did you expect to happen?

When the plan_directory is set to a custom path (e.g., ~/.gemini/plans/), the application should successfully initialize, write, and read plan files from that specific location without returning an error, provided the directory exists and has the correct write permissions.

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
# paste output here
 About Gemini CLI                              │
│                                               │
│ CLI Version     0.40.0                        │
│ Git Commit      3d5bdc052                     │
│ Model           gemini-3.1-flash-lite-preview │
│ Sandbox         no sandbox                    │
│ OS              linux                         │
│ Auth Method Signed in with Google             │
│             ()           │
│ Tier          Gemini Code Assist for          │
│               individuals
</details>

Login information

Google account

Anything else we need to know?

First started appearing like version 0.39.0

extent analysis

TL;DR

The issue may be resolved by ensuring the custom directory has the correct write permissions or by using the default directory.

Guidance

  • Verify that the custom directory .gemini/plans has the correct write permissions for the application to create and write files.
  • Check the application's documentation or configuration options to see if there are any specific requirements or restrictions for custom directory paths.
  • Try setting the plan directory to a different custom path to see if the issue is specific to the .gemini/plans directory.
  • Review the application's logs or output to see if there are any error messages or hints about what might be causing the issue.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to a change introduced in version 0.39.0, but without more information, it's difficult to determine the exact cause.

Recommendation

Apply workaround: Use the default directory until the issue with custom directories is resolved, as it is reported to work correctly.

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…
#memory management#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

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

Back to top recommendations

TRENDING