TL;DR

Update the save_config_value() function to always write user-initiated changes to the user_config_path, creating it if necessary, instead of targeting the project fallback cli-config.yaml when ~/.hermes/config.yaml does not exist.

Guidance

• Modify the logic in cli.py:1525-1528 to prioritize writing to user_config_path even if it does not exist, ensuring user settings are stored in the user's home directory.
• Introduce a check to create the user_config_path directory and file if it does not exist before writing to it, to handle first-run scenarios or environments where the file is absent.
• Update the save_config_value() function to handle the case where user_config_path needs to be created, possibly using a try-except block to manage potential file system errors.
• Consider adding a regression test to ensure the function behaves correctly when ~/.hermes/config.yaml is missing, as suggested in the issue.

Example

import os
from pathlib import Path

def save_config_value(key, value):
    user_config_path = Path("~/.hermes/config.yaml").expanduser()
    # Create the directory and file if they do not exist
    user_config_path.parent.mkdir(parents=True, exist_ok=True)
    # Proceed with writing to the user_config_path
    # ...

Notes

This solution assumes that the user_config_path is correctly determined and that the issue lies in the logic of choosing where to write the configuration changes. The exact implementation details may vary based on the existing code structure and requirements.

Recommendation

Apply the workaround by updating the save_config_value() function to always write to the user_config_path, creating it if necessary, to ensure user settings are stored correctly and do not overwrite the project fallback configuration.