Merge remote-tracking branch 'origin/main' into vscode-lm-provider

Author: mrubens

.clinerules

@@ -4,165 +4,12 @@
    - Before attempting completion, always make sure that any code changes have test coverage
    - Ensure all tests pass before submitting changes
 
-2. Git Commits:
-   - When finishing a task, always output a git commit command
-   - Include a descriptive commit message that follows conventional commit format
-
-3. Documentation:
-   - Update README.md when making significant changes, such as:
-     * Adding new features or settings
-     * Changing existing functionality
-     * Updating system requirements
-     * Adding new dependencies
-   - Include clear descriptions of new features and how to use them
-   - Keep the documentation in sync with the codebase
-   - Add examples where appropriate
-
-4. Lint Rules:
+2. Lint Rules:
    - Never disable any lint rules without explicit user approval
    - If a lint rule needs to be disabled, ask the user first and explain why
    - Prefer fixing the underlying issue over disabling the lint rule
    - Document any approved lint rule disabling with a comment explaining the reason
 
 # Adding a New Setting
 
-To add a new setting that persists its state, follow these steps:
-
-## For All Settings
-
-1. Add the setting to ExtensionMessage.ts:
-   - Add the setting to the ExtensionState interface
-   - Make it required if it has a default value, optional if it can be undefined
-   - Example: `preferredLanguage: string`
-
-2. Add test coverage:
-   - Add the setting to mockState in ClineProvider.test.ts
-   - Add test cases for setting persistence and state updates
-   - Ensure all tests pass before submitting changes
-
-## For Checkbox Settings
-
-1. Add the message type to WebviewMessage.ts:
-   - Add the setting name to the WebviewMessage type's type union
-   - Example: `| "multisearchDiffEnabled"`
-
-2. Add the setting to ExtensionStateContext.tsx:
-   - Add the setting to the ExtensionStateContextType interface
-   - Add the setter function to the interface
-   - Add the setting to the initial state in useState
-   - Add the setting to the contextValue object
-   - Example:
-     ```typescript
-     interface ExtensionStateContextType {
-       multisearchDiffEnabled: boolean;
-       setMultisearchDiffEnabled: (value: boolean) => void;
-     }
-     ```
-
-3. Add the setting to ClineProvider.ts:
-   - Add the setting name to the GlobalStateKey type union
-   - Add the setting to the Promise.all array in getState
-   - Add the setting to the return value in getState with a default value
-   - Add the setting to the destructured variables in getStateToPostToWebview
-   - Add the setting to the return value in getStateToPostToWebview
-   - Add a case in setWebviewMessageListener to handle the setting's message type
-   - Example:
-     ```typescript
-     case "multisearchDiffEnabled":
-       await this.updateGlobalState("multisearchDiffEnabled", message.bool)
-       await this.postStateToWebview()
-       break
-     ```
-
-4. Add the checkbox UI to SettingsView.tsx:
-   - Import the setting and its setter from ExtensionStateContext
-   - Add the VSCodeCheckbox component with the setting's state and onChange handler
-   - Add appropriate labels and description text
-   - Example:
-     ```typescript
-     <VSCodeCheckbox 
-       checked={multisearchDiffEnabled} 
-       onChange={(e: any) => setMultisearchDiffEnabled(e.target.checked)}
-     >
-       <span style={{ fontWeight: "500" }}>Enable multi-search diff matching</span>
-     </VSCodeCheckbox>
-     ```
-
-5. Add the setting to handleSubmit in SettingsView.tsx:
-   - Add a vscode.postMessage call to send the setting's value when clicking Done
-   - Example:
-     ```typescript
-     vscode.postMessage({ type: "multisearchDiffEnabled", bool: multisearchDiffEnabled })
-     ```
-
-## For Select/Dropdown Settings
-
-1. Add the message type to WebviewMessage.ts:
-   - Add the setting name to the WebviewMessage type's type union
-   - Example: `| "preferredLanguage"`
-
-2. Add the setting to ExtensionStateContext.tsx:
-   - Add the setting to the ExtensionStateContextType interface
-   - Add the setter function to the interface
-   - Add the setting to the initial state in useState with a default value
-   - Add the setting to the contextValue object
-   - Example:
-     ```typescript
-     interface ExtensionStateContextType {
-       preferredLanguage: string;
-       setPreferredLanguage: (value: string) => void;
-     }
-     ```
-
-3. Add the setting to ClineProvider.ts:
-   - Add the setting name to the GlobalStateKey type union
-   - Add the setting to the Promise.all array in getState
-   - Add the setting to the return value in getState with a default value
-   - Add the setting to the destructured variables in getStateToPostToWebview
-   - Add the setting to the return value in getStateToPostToWebview
-   - Add a case in setWebviewMessageListener to handle the setting's message type
-   - Example:
-     ```typescript
-     case "preferredLanguage":
-       await this.updateGlobalState("preferredLanguage", message.text)
-       await this.postStateToWebview()
-       break
-     ```
-
-4. Add the select UI to SettingsView.tsx:
-   - Import the setting and its setter from ExtensionStateContext
-   - Add the select element with appropriate styling to match VSCode's theme
-   - Add options for the dropdown
-   - Add appropriate labels and description text
-   - Example:
-     ```typescript
-     <select
-       value={preferredLanguage}
-       onChange={(e) => setPreferredLanguage(e.target.value)}
-       style={{
-         width: "100%",
-         padding: "4px 8px",
-         backgroundColor: "var(--vscode-input-background)",
-         color: "var(--vscode-input-foreground)",
-         border: "1px solid var(--vscode-input-border)",
-         borderRadius: "2px"
-       }}>
-       <option value="English">English</option>
-       <option value="Spanish">Spanish</option>
-       ...
-     </select>
-     ```
-
-5. Add the setting to handleSubmit in SettingsView.tsx:
-   - Add a vscode.postMessage call to send the setting's value when clicking Done
-   - Example:
-     ```typescript
-     vscode.postMessage({ type: "preferredLanguage", text: preferredLanguage })
-     ```
-
-These steps ensure that:
-- The setting's state is properly typed throughout the application
-- The setting persists between sessions
-- The setting's value is properly synchronized between the webview and extension
-- The setting has a proper UI representation in the settings view
-- Test coverage is maintained for the new setting
+To add a new setting that persists its state, follow the steps in cline_docs/settings.md

.github/workflows/marketplace-publish.yml

@@ -36,7 +36,9 @@ jobs:
       - name: Package and Publish Extension
         env:
           VSCE_PAT: ${{ secrets.VSCE_PAT }}
+          OVSX_PAT: ${{ secrets.OVSX_PAT }}
         run: |
           current_package_version=$(node -p "require('./package.json').version")
           npm run publish:marketplace
           echo "Successfully published version $current_package_version to VS Code Marketplace"
+

.gitignore

@@ -1,7 +1,7 @@
 out
 dist
 node_modules
-.vscode-test/
+coverage/
 
 .DS_Store
 
@@ -13,4 +13,5 @@ roo-cline-*.vsix
 /local-prompts
 
 # Test environment
-.test_env
+.test_env
+.vscode-test/

CHANGELOG.md

@@ -1,5 +1,34 @@
 # Roo Cline Changelog
 
+## [3.1.1]
+
+-   Visual fixes to chat input and settings for the light+ themes
+
+## [3.1.0]
+
+-   You can now customize the role definition and instructions for each chat mode (Code, Architect, and Ask), either through the new Prompts tab in the top menu or mode-specific .clinerules-mode files. Prompt Enhancements have also been revamped: the "Enhance Prompt" button now works with any provider and API configuration, giving you the ability to craft messages with fully customizable prompts for even better results.
+-   Add a button to copy markdown out of the chat
+
+## [3.0.3]
+
+-   Update required vscode engine to ^1.84.0 to match cline
+
+## [3.0.2]
+
+-   A couple more tiny tweaks to the button alignment in the chat input
+
+## [3.0.1]
+
+-   Fix the reddit link and a small visual glitch in the chat input
+
+## [3.0.0]
+
+-   This release adds chat modes! Now you can ask Roo Cline questions about system architecture or the codebase without immediately jumping into writing code. You can even assign different API configuration profiles to each mode if you prefer to use different models for thinking vs coding. Would love feedback in the new Roo Cline Reddit! https://www.reddit.com/r/roocline
+
+## [2.2.46]
+
+-   Only parse @-mentions in user input (not in files)
+
 ## [2.2.45]
 
 -   Save different API configurations to quickly switch between providers and settings (thanks @samhvw8!)

README.md

@@ -1,9 +1,47 @@
-# Roo-Cline
+# Roo Cline
 
 A fork of Cline, an autonomous coding agent, with some additional experimental features. It’s been mainly writing itself recently, with a light touch of human guidance here and there.
 
+## New in 3.1: Chat Mode Prompt Customization & Prompt Enhancements
+
+Hot off the heels of **v3.0** introducing Code, Architect, and Ask chat modes, one of the most requested features has arrived: **customizable prompts for each mode**! 🎉
+
+You can now tailor the **role definition** and **custom instructions** for every chat mode to perfectly fit your workflow. Want to adjust Architect mode to focus more on system scalability? Or tweak Ask mode for deeper research queries? Done. Plus, you can define these via **mode-specific `.clinerules-[mode]` files**. You’ll find all of this in the new **Prompts** tab in the top menu.
+
+The second big feature in this release is a complete revamp of **prompt enhancements**. This feature helps you craft messages to get even better results from Cline. Here’s what’s new:  
+- Works with **any provider** and API configuration, not just OpenRouter.  
+- Fully customizable prompts to match your unique needs.  
+- Same simple workflow: just hit the ✨ **Enhance Prompt** button in the chat input to try it out.
+
+Whether you’re using GPT-4, other APIs, or switching configurations, this gives you total control over how your prompts are optimized.
+
+As always, we’d love to hear your thoughts and ideas! What features do you want to see in **v3.2**? Drop by https://www.reddit.com/r/roocline and join the discussion - we're building Roo Cline together. 🚀  
+
+## New in 3.0 - Chat Modes!
+
+You can now choose between different prompts for Roo Cline to better suit your workflow. Here’s what’s available:
+
+- **Code:** (existing behavior): The default mode where Cline helps you write code and execute tasks.
+
+- **Architect:** "You are Cline, a software architecture expert..." Ideal for thinking through high-level technical design and system architecture. Can’t write code or run commands.
+
+- **Ask:** "You are Cline, a knowledgeable technical assistant..." Perfect for asking questions about the codebase or digging into concepts. Also can’t write code or run commands.
+
+**Switching Modes:**
+It’s super simple! There’s a dropdown in the bottom left of the chat input to switch modes. Right next to it, you’ll find a way to switch between the API configuration profiles associated with the current mode (configured on the settings screen).
+
+**Why Add This?**
+- It keeps Cline from being overly eager to jump into solving problems when you just want to think or ask questions.
+- Each mode remembers the API configuration you last used with it. For example, you can use more thoughtful models like OpenAI o1 for Architect and Ask, while sticking with Sonnet or DeepSeek for coding tasks.
+- It builds on research suggesting better results when separating "thinking" from "coding," explained well in this very thoughtful [article](https://aider.chat/2024/09/26/architect.html) from aider.
+
+Right now, switching modes is a manual process. In the future, we’d love to give Cline the ability to suggest mode switches based on context. For now, we’d really appreciate your feedback on this feature.
+
+Give it a try and let us know what you think in the reddit: https://www.reddit.com/r/roocline 🚀
+
 ## Experimental Features
 
+- Different chat modes for coding, architecting code, and asking questions about the codebase
 - Drag and drop images into chats
 - Delete messages from chats
 - @-mention Git commits to include their context in the chat
@@ -12,6 +50,7 @@ A fork of Cline, an autonomous coding agent, with some additional experimental f
 - Sound effects for feedback
 - Option to use browsers of different sizes and adjust screenshot quality
 - Quick prompt copying from history
+- Copy markdown from chat messages
 - OpenRouter compression support
 - Includes current time in the system prompt
 - Uses a file system watcher to more reliably watch for file system changes
@@ -40,7 +79,7 @@ Here's an example of Roo-Cline autonomously creating a snake game with "Always a
 https://github.com/user-attachments/assets/c2bb31dc-e9b2-4d73-885d-17f1471a4987
 
 ## Contributing
-To contribute to the project, start by exploring [open issues](https://github.com/RooVetGit/Roo-Cline/issues) or checking our [feature request board](https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop). We'd also love to have you join our [Discord](https://discord.gg/cline) to share ideas and connect with other contributors.
+To contribute to the project, start by exploring [open issues](https://github.com/RooVetGit/Roo-Cline/issues) or checking our [feature request board](https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop). We'd also love to have you join the [Roo Cline Reddit](https://www.reddit.com/r/roocline/) and the [Cline Discord](https://discord.gg/cline) to share ideas and connect with other contributors.
 
 <details>
 <summary>Local Setup</summary>