You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(custom-instructions): migrate custom instructions to file-based storage
See discussion: #4000
Migrated the storage of "Custom Instructions for All Modes" from VS Code's global state to a dedicated file: `...Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/custom_instructions.md`.
Key changes include:
- Implemented a migration utility to automatically move existing custom instructions from global state to the new file upon extension update.
- Introduced new commands and UI buttons within the Prompts view to:
- Open the `custom_instructions.md` file directly in the editor for easy editing.
- Refresh the custom instructions in the UI by re-reading them from the file, ensuring changes made directly to the file are reflected.
- The `updateCustomInstructions` function now writes/deletes the file instead of updating global state.
- The initial state and refreshes now read custom instructions directly from the file.
This change provides a more robust and user-friendly way to manage custom instructions, allowing for external editing and version control.
Copy file name to clipboardExpand all lines: webview-ui/src/i18n/locales/en/prompts.json
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,8 @@
48
48
"globalCustomInstructions": {
49
49
"title": "Custom Instructions for All Modes",
50
50
"description": "These instructions apply to all modes. They provide a base set of behaviors that can be enhanced by mode-specific instructions below. <0>Learn more</0>",
51
+
"openFile": "Open custom instructions file",
52
+
"refreshFile": "Refresh custom instructions from file",
51
53
"loadFromFile": "Instructions can also be loaded from the <span>.roo/rules/</span> folder in your workspace (.roorules and .clinerules are deprecated and will stop working soon)."
0 commit comments