hermes - 💡(How to fix) Fix [Feature] User Approval Before Auto-Saving Skills [1 comments, 2 participants]

Feature Request: User Approval Before Auto-Saving Skills

Description

Currently, Hermes automatically saves successful operations as skills without user consent. This feature request proposes adding user approval/confirmation before auto-saving skills.

Problem

• Users have no control over what gets saved as a skill
• Privacy concerns: sensitive operations might be saved automatically
• No way to opt-out of auto-saving behavior
• Users discover auto-saved skills through system messages after the fact

Proposed Solution

Add a configuration option to require user approval before auto-saving skills:

# In config.yaml
skills:
  auto_save: false  # or 'prompt' to ask each time
  # Options:
  #   true  - current behavior (auto-save without asking)
  #   false - disable auto-saving completely
  #   prompt - ask for user confirmation before saving

User Experience

When auto_save: prompt is set:

1. After completing a task that could be saved as a skill
2. System shows: "Would you like to save this workflow as a skill for future use? [Y/n]"
3. User can approve, decline, or customize the skill name
4. Only saves if user explicitly approves

Benefits

• Privacy: Users control what gets saved
• Transparency: Clear notification before saving
• Customization: Users can name/describe skills before saving
• Control: Easy to disable auto-saving entirely

Implementation Notes

• Add auto_save config option to skills section
• Modify auto-save logic to check config before saving
• Add confirmation prompt in CLI/TUI interfaces
• Update system messages to reflect new behavior

Use Case

When processing sensitive documents (like ID cards), users may not want the workflow automatically saved as a skill. This feature gives users control over their data and workflows.

Submitted via Hermes Agent