Per-Model Folder Settings for Obsidian Copilot

[logicsec]

Feature Request: Per-Model Folder Settings for Obsidian Copilot

Description:

Currently, Obsidian Copilot uses a single global folder for storing model-specific data, such as API keys and configuration settings. This can be limiting for users who want to manage different models with separate configurations.

This feature request proposes adding the ability to specify a per-model folder, allowing users to organize and manage their models more effectively.

Proposed Implementation:

1. General Settings Toggle: Introduce a new toggle switch in the Obsidian Copilot general settings, labeled "Enable Per-Model Folders".

2. Model Settings Input: When the toggle is enabled, each model settings page (where API keys are entered) will display a new input field for specifying a folder path.

3. Folder Path Resolution: When a user changes the model in the chat window, Obsidian Copilot will:

   • Check if a folder path is specified for the selected model.
   • If a folder path is found, use it to load model-specific data.
   • If no folder path is specified, default to the global folder path.

Benefits:

• Improved Organization: Allows users to organize their models and their associated data in a more structured way.
• Enhanced Flexibility: Provides greater control over model-specific settings and configurations.
• Reduced Conflicts: Prevents potential conflicts between different models sharing the same data.

Example Use Case:

A user might have two different models: one for generating code and another for writing creative content. By enabling per-model folders, they can store the API keys and configuration settings for each model separately, ensuring that they don't interfere with each other.

Conclusion:

Implementing per-model folder settings would significantly enhance the flexibility and organization of Obsidian Copilot, providing users with greater control over their models and their associated data. This feature would be a valuable addition to the plugin, improving the overall user experience.

[logancyang]

I believe this is close to what I have in mind as "Profile". Profile is use case specific and it will have "model, params, system prompt" presets.

[logancyang]

Related #459