Issue: gentleman-dots installation overwrites existing opencode.json configuration
Description
When installing the full ecosystem using gentleman-dots, the process removes or overwrites my existing opencode.json configuration file that was previously created by gentle-ai.
This causes an important problem because I lose my existing orchestration setup, including:
- Plugins configuration
- MCPs configuration
- Orchestration settings
- Other custom adjustments
As a result, I am forced to manually reconfigure the entire system every time I run the installation.
Expected behavior
The installation process should preserve the existing opencode.json file instead of replacing it.
If gentleman-dots needs to add new configuration values, it should:
- Keep the existing configuration intact
- Only add missing fields
- Update only what is strictly necessary
- Avoid destructive overwrites
Suggested solution
Instead of replacing the file, the installer could merge configurations by:
- Checking if
opencode.json already exists
- Backing it up if modifications are required
- Performing a non-destructive merge of the configuration
- Only injecting required new values
Why this matters
Many users may already have a working configuration created by gentle-ai, and overwriting it creates unnecessary friction and setup time.
Preserving user configuration would make the installation process safer and more user-friendly.
Possible workaround
Currently, the only workaround is manually backing up opencode.json before running the installation and restoring it afterward.
Issue: gentleman-dots installation overwrites existing opencode.json configuration
Description
When installing the full ecosystem using gentleman-dots, the process removes or overwrites my existing
opencode.jsonconfiguration file that was previously created by gentle-ai.This causes an important problem because I lose my existing orchestration setup, including:
As a result, I am forced to manually reconfigure the entire system every time I run the installation.
Expected behavior
The installation process should preserve the existing
opencode.jsonfile instead of replacing it.If gentleman-dots needs to add new configuration values, it should:
Suggested solution
Instead of replacing the file, the installer could merge configurations by:
opencode.jsonalready existsWhy this matters
Many users may already have a working configuration created by gentle-ai, and overwriting it creates unnecessary friction and setup time.
Preserving user configuration would make the installation process safer and more user-friendly.
Possible workaround
Currently, the only workaround is manually backing up
opencode.jsonbefore running the installation and restoring it afterward.