Upstream v1.14.3

.eslintrc.json

@@ -15,6 +15,8 @@
 			}
 		],
 		"@typescript-eslint/semi": "off",
+		"no-unused-vars": "off",
+		"@typescript-eslint/no-unused-vars": "off",
 		"eqeqeq": "warn",
 		"no-throw-literal": "warn",
 		"semi": "off"

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,68 +1,80 @@
 name: Bug Report
-description: File a bug report
+description: Clearly report a bug with detailed repro steps
 labels: ["bug"]
 body:
-    - type: input
-      id: version
-      attributes:
-          label: Which version of the app are you using?
-          description: Please specify the app version you're using (e.g. v3.3.1)
-      validations:
-          required: true
-    - type: dropdown
-      id: provider
-      attributes:
-          label: Which API Provider are you using?
-          multiple: false
-          options:
-              - OpenRouter
-              - Anthropic
-              - Google Gemini
-              - DeepSeek
-              - OpenAI
-              - OpenAI Compatible
-              - GCP Vertex AI
-              - AWS Bedrock
-              - Glama
-              - VS Code LM API
-              - LM Studio
-              - Ollama
-      validations:
-          required: true
-    - type: input
-      id: model
-      attributes:
-          label: Which Model are you using?
-          description: Please specify the model you're using (e.g. Claude 3.7 Sonnet)
-      validations:
-          required: true
-    - type: textarea
-      id: what-happened
-      attributes:
-          label: What happened?
-          description: Also tell us, what did you expect to happen?
-          placeholder: Tell us what you see!
-      validations:
-          required: true
-    - type: textarea
-      id: steps
-      attributes:
-          label: Steps to reproduce
-          description: How do you trigger this bug? Please walk us through it step by step.
-          value: |
-              1.
-              2.
-              3.
-      validations:
-          required: true
-    - type: textarea
-      id: logs
-      attributes:
-          label: Relevant API REQUEST output
-          description: Please copy and paste any relevant output. This will be automatically formatted into code, so no need for backticks.
-          render: shell
-    - type: textarea
-      id: additional-context
-      attributes:
-          label: Additional context
-          description: Add any other context about the problem here, such as screenshots or related issues.
+  - type: input
+    id: version
+    attributes:
+      label: App Version
+      description: Specify exactly which version you're using (e.g., v3.3.1)
+    validations:
+      required: true
+
+  - type: dropdown
+    id: provider
+    attributes:
+      label: API Provider
+      description: Choose the API provider involved
+      multiple: false
+      options:
+        - OpenRouter
+        - Anthropic
+        - Google Gemini
+        - DeepSeek
+        - OpenAI
+        - OpenAI Compatible
+        - GCP Vertex AI
+        - Amazon Bedrock
+        - Requesty
+        - Glama
+        - VS Code LM API
+        - LM Studio
+        - Ollama
+    validations:
+      required: true
+
+  - type: input
+    id: model
+    attributes:
+      label: Model Used
+      description: Clearly specify the exact model (e.g., Claude 3.7 Sonnet)
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Actual vs. Expected Behavior
+      description: Clearly state what actually happened and what you expected instead.
+      placeholder: Provide precise details of the issue here.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Detailed Steps to Reproduce
+      description: |
+        List the exact steps someone must follow to reproduce this bug:
+        1. Starting conditions (software state, settings, environment)
+        2. Precise actions taken (every click, selection, input)
+        3. Clearly observe and report outcomes
+      value: |
+        1.
+        2.
+        3.
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant API Request Output
+      description: Paste relevant API logs or outputs here (formatted automatically as code)
+      render: shell
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Include extra details, screenshots, or related issues.

.github/workflows/code-qa.yml

@@ -62,7 +62,10 @@ jobs:
         run: npm run knip
 
   test-extension:
-    runs-on: ubuntu-latest
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest]
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
@@ -73,11 +76,16 @@ jobs:
           cache: 'npm'
       - name: Install dependencies
         run: npm run install:all
+      - name: Compile (to build and copy WASM files)
+        run: npm run compile
       - name: Run unit tests
         run: npx jest --silent
 
   test-webview:
-    runs-on: ubuntu-latest
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest]
     steps:
       - name: Checkout code
         uses: actions/checkout@v4

.gitignore

@@ -1,3 +1,4 @@
+.pnpm-store
 dist
 out
 out-*
@@ -31,7 +32,6 @@ docs/_site/
 
 #Logging
 logs
-.aider*
-.env
-# aider
-.aider*
+
+# Vite development
+.vite-port

.husky/pre-commit

@@ -12,4 +12,12 @@ else
   npx_cmd="npx"
 fi
 
-"$npx_cmd" lint-staged
+npm run generate-types
+
+if [ -n "$(git diff --name-only src/exports/roo-code.d.ts)" ]; then
+  echo "Error: There are unstaged changes to roo-code.d.ts after running 'npm run generate-types'."
+  echo "Please review and stage the changes before committing."
+  exit 1
+fi
+
+"$npx_cmd" lint-staged

.roo/rules-translate/001-general-rules.md

@@ -0,0 +1,104 @@
+# 1. SUPPORTED LANGUAGES AND LOCATION
+
+- Localize all strings into the following locale files: ca, de, en, es, fr, hi, it, ja, ko, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW
+- The VSCode extension has two main areas that require localization:
+    - Core Extension: src/i18n/locales/ (extension backend)
+    - WebView UI: webview-ui/src/i18n/locales/ (user interface)
+
+# 2. VOICE, STYLE AND TONE
+
+- Always use informal speech (e.g., "du" instead of "Sie" in German) for all translations
+- Maintain a direct and concise style that mirrors the tone of the original text
+- Carefully account for colloquialisms and idiomatic expressions in both source and target languages
+- Aim for culturally relevant and meaningful translations rather than literal translations
+- Preserve the personality and voice of the original content
+- Use natural-sounding language that feels native to speakers of the target language
+- Don't translate the word "token" as it means something specific in English that all languages will understand
+- Don't translate domain-specific words (especially technical terms like "Prompt") that are commonly used in English in the target language
+
+# 3. CORE EXTENSION LOCALIZATION (src/)
+
+- Located in src/i18n/locales/
+- NOT ALL strings in core source need internationalization - only user-facing messages
+- Internal error messages, debugging logs, and developer-facing messages should remain in English
+- The t() function is used with namespaces like 'core:errors.missingToolParameter'
+- Be careful when modifying interpolation variables; they must remain consistent across all translations
+- Some strings in formatResponse.ts are intentionally not internationalized since they're internal
+- When updating strings in core.json, maintain all existing interpolation variables
+- Check string usages in the codebase before making changes to ensure you're not breaking functionality
+
+# 4. WEBVIEW UI LOCALIZATION (webview-ui/src/)
+
+- Located in webview-ui/src/i18n/locales/
+- Uses standard React i18next patterns with the useTranslation hook
+- All user interface strings should be internationalized
+- Always use the Trans component with named components for text with embedded components
+
+<Trans> example:
+
+`"changeSettings": "You can always change this at the bottom of the <settingsLink>settings</settingsLink>",`
+
+```
+  <Trans
+    i18nKey="welcome:telemetry.changeSettings"
+    components={{
+      settingsLink: <VSCodeLink href="#" onClick={handleOpenSettings} />
+    }}
+  />
+```
+
+# 5. TECHNICAL IMPLEMENTATION
+
+- Use namespaces to organize translations logically
+- Handle pluralization using i18next's built-in capabilities
+- Implement proper interpolation for variables using {{variable}} syntax
+- Don't include defaultValue. The `en` translations are the fallback
+- Always use apply_diff instead of write_to_file when editing existing translation files (much faster and more reliable)
+- When using apply_diff, carefully identify the exact JSON structure to edit to avoid syntax errors
+- Placeholders (like {{variable}}) must remain exactly identical to the English source to maintain code integration and prevent syntax errors
+
+# 6. WORKFLOW AND APPROACH
+
+- First add or modify English strings, then ask for confirmation before translating to all other languages
+- Use this process for each localization task:
+    1. Identify where the string appears in the UI/codebase
+    2. Understand the context and purpose of the string
+    3. Update English translation first
+    4. Create appropriate translations for all other supported languages
+    5. Validate your changes with the missing translations script
+- Flag or comment if an English source string is incomplete ("please see this...") to avoid truncated or unclear translations
+- For UI elements, distinguish between:
+    - Button labels: Use short imperative commands ("Save", "Cancel")
+    - Tooltip text: Can be slightly more descriptive
+- Preserve the original perspective: If text is a user command directed at the software, ensure the translation maintains this direction, avoiding language that makes it sound like an instruction from the system to the user
+
+# 7. COMMON PITFALLS TO AVOID
+
+- Switching between formal and informal addressing styles - always stay informal ("du" not "Sie")
+- Translating or altering technical terms and brand names that should remain in English
+- Modifying or removing placeholders like {{variable}} - these must remain identical
+- Translating domain-specific terms that are commonly used in English in the target language
+- Changing the meaning or nuance of instructions or error messages
+- Forgetting to maintain consistent terminology throughout the translation
+
+# 8. QUALITY ASSURANCE
+
+- Maintain consistent terminology across all translations
+- Respect the JSON structure of translation files
+- Watch for placeholders and preserve them in translations
+- Be mindful of text length in UI elements when translating to languages that might require more characters
+- Use context-aware translations when the same string has different meanings
+- Always validate your translation work by running the missing translations script:
+    ```
+    node scripts/find-missing-translations.js
+    ```
+- Address any missing translations identified by the script to ensure complete coverage across all locales
+
+# 9. TRANSLATOR'S CHECKLIST
+
+- ✓ Used informal tone consistently ("du" not "Sie")
+- ✓ Preserved all placeholders exactly as in the English source
+- ✓ Maintained consistent terminology with existing translations
+- ✓ Kept technical terms and brand names unchanged where appropriate
+- ✓ Preserved the original perspective (user→system vs system→user)
+- ✓ Adapted the text appropriately for UI context (buttons vs tooltips)

.roo/rules-translate/instructions-de.md

@@ -0,0 +1,14 @@
+# German (de) Translation Guidelines
+
+**Key Rule:** Always use informal speech ("du" form) in all German translations without exception.
+
+## Quick Reference
+
+| Category    | Formal (Avoid)            | Informal (Use)      | Example           |
+| ----------- | ------------------------- | ------------------- | ----------------- |
+| Pronouns    | Sie                       | du                  | you               |
+| Possessives | Ihr/Ihre/Ihrem            | dein/deine/deinem   | your              |
+| Verbs       | können Sie, müssen Sie    | kannst du, musst du | you can, you must |
+| Imperatives | Geben Sie ein, Wählen Sie | Gib ein, Wähle      | Enter, Choose     |
+
+**Technical terms** like "API", "token", "prompt" should not be translated.