google-gemini
Refresh custom /commands and extensions without restarting Gemini CLI
What happened?
Developers benefit significantly from the features offered by custom slash commands and extensions.
However, when adding a custom command, built with Gemini CLI itself sometimes, the developer needs to restart the CLI for the changes to take effect. Context would be lost during a restart.
To alleviate this, there is the workaround of
- /chat save "tag"
- exit
- restart
- /chat restore "tag"
Same is valid for extensions
cc: @jacob314 @jackwotherspoon
What did you expect to happen?
Expectation would be to have a command /chat:refresh or /context:refresh which would automate the steps of saving the context, restarting and resuming from that tag.
Client information
CLI Version 0.4.0
│ Git Commit 89213699
│ Model gemini-2.5-pro
│ Sandbox no sandbox
│ OS darwin
│ Auth Method vertex-ai
│ GCP Project ...
│ IDE Client VS Code
Login information
Google Credentials
Anything else we need to know?
No response
This is a feature request to improve the developer experience by allowing custom commands and extensions to be refreshed without restarting the CLI.
![gemini-cli[bot] avatar](https://avatars.githubusercontent.com/in/1473539?v=4 "Published by a pub.dev verified publisher"){kind=small}
@gemini-cli Is there an update about this issue? This feature would improve the development of the custom commands in our organization, too.
Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports.
It looks like this issue hasn't been active for a while, so we are closing it for now. However, if you are still experiencing this bug on the latest stable build, please feel free to comment on this issue or create a new one with updated details.
Thank you for your contribution!
Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports.
It looks like this issue hasn't been active for a while, so we are closing it for now. However, if you are still experiencing this bug on the latest stable build, please feel free to comment on this issue or create a new one with updated details.
Thank you for your contribution!