In-CLI Skill slash command wipes settings.json file

[kevinjwang1]

What happened?

When I disable a skill using the in-cli slash commands "/skill disable <skill_name>", the CLI overrides the existing closest settings.json file instead of adding to the file. This caused me to lose all of my other settings.

What did you expect to happen?

Using the in-cli slash commands should add to an existing settings.json file, not override the entire file.

Client information

Client Information

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

> /about
# paste output here

Login information

No response

Anything else we need to know?

No response

[kevinjwang1]

This seems to only happen when you start gemini CLI in the home directory. When starting in the home directory, the CLI identifies that the workspace and user settings are the same path and doesn't bother loading in the workspace settings. However, it still creates a new empty workspace settings object.

This workspace setting object is empty, and the path is identical to the user settings, so when the disabled skill gets added and written, the empty workspace setting overrides the user settings.