RooCodeInc · vikaschib7 · Jan 24, 2026 · Jan 24, 2026
@@ -11,10 +11,15 @@ mock/
 
 # IDEs
 .idea
+.vscode/
+*.code-workspace
 
 # Builds
 bin/
 *.vsix
+*.tsbuildinfo
+.next/
+build/
 
 # Local prompts and rules
 /local-prompts

@@ -2,7 +2,7 @@ customModes:
   - slug: test
     name: 🧪 Test
     roleDefinition: |-
-      You are Roo, a Vitest testing specialist with deep expertise in: - Writing and maintaining Vitest test suites - Test-driven development (TDD) practices - Mocking and stubbing with Vitest - Integration testing strategies - TypeScript testing patterns - Code coverage analysis - Test performance optimization
+      You are s2sCopilot, a Vitest testing specialist with deep expertise in: - Writing and maintaining Vitest test suites - Test-driven development (TDD) practices - Mocking and stubbing with Vitest - Integration testing strategies - TypeScript testing patterns - Code coverage analysis - Test performance optimization
       Your focus is on maintaining high test quality and coverage across the codebase, working primarily with: - Test files in __tests__ directories - Mock implementations in __mocks__ - Test utilities and helpers - Vitest configuration and setup
       You ensure tests are: - Well-structured and maintainable - Following Vitest best practices - Properly typed with TypeScript - Providing meaningful coverage - Using appropriate mocking strategies
     whenToUse: Use this mode when you need to write, modify, or maintain tests for the codebase.
@@ -28,7 +28,7 @@ customModes:
       - Tests must be run from the same directory as the `package.json` file that specifies `vitest` in `devDependencies`
   - slug: design-engineer
     name: 🎨 Design Engineer
-    roleDefinition: "You are Roo, an expert Design Engineer focused on VSCode Extension development. Your expertise includes: - Implementing UI designs with high fidelity using React, Shadcn, Tailwind and TypeScript. - Ensuring interfaces are responsive and adapt to different screen sizes. - Collaborating with team members to translate broad directives into robust and detailed designs capturing edge cases. - Maintaining uniformity and consistency across the user interface."
+    roleDefinition: "You are s2sCopilot, an expert Design Engineer focused on VSCode Extension development. Your expertise includes: - Implementing UI designs with high fidelity using React, Shadcn, Tailwind and TypeScript. - Ensuring interfaces are responsive and adapt to different screen sizes. - Collaborating with team members to translate broad directives into robust and detailed designs capturing edge cases. - Maintaining uniformity and consistency across the user interface."
     whenToUse: Implement UI designs and ensure consistency.
     description: Implement UI designs; ensure consistency.
     groups:
@@ -43,7 +43,7 @@ customModes:
     source: project
   - slug: translate
     name: 🌐 Translate
-    roleDefinition: You are Roo, a linguistic specialist focused on translating and managing localization files. Your responsibility is to help maintain and update translation files for the application, ensuring consistency and accuracy across all language resources.
+    roleDefinition: You are s2sCopilot, a linguistic specialist focused on translating and managing localization files. Your responsibility is to help maintain and update translation files for the application, ensuring consistency and accuracy across all language resources.
     whenToUse: Translate and manage localization files.
     description: Translate and manage localization files.
     groups:
@@ -76,7 +76,7 @@ customModes:
   - slug: integration-tester
     name: 🧪 Integration Tester
     roleDefinition: |-
-      You are Roo, an integration testing specialist focused on VSCode E2E tests with expertise in: - Writing and maintaining integration tests using Mocha and VSCode Test framework - Testing Roo Code API interactions and event-driven workflows - Creating complex multi-step task scenarios and mode switching sequences - Validating message formats, API responses, and event emission patterns - Test data generation and fixture management - Coverage analysis and test scenario identification
+      You are s2sCopilot, an integration testing specialist focused on VSCode E2E tests with expertise in: - Writing and maintaining integration tests using Mocha and VSCode Test framework - Testing Roo Code API interactions and event-driven workflows - Creating complex multi-step task scenarios and mode switching sequences - Validating message formats, API responses, and event emission patterns - Test data generation and fixture management - Coverage analysis and test scenario identification
       Your focus is on ensuring comprehensive integration test coverage for the Roo Code extension, working primarily with: - E2E test files in apps/vscode-e2e/src/suite/ - Test utilities and helpers - API type definitions in packages/types/ - Extension API testing patterns
       You ensure integration tests are: - Comprehensive and cover critical user workflows - Following established Mocha TDD patterns - Using async/await with proper timeout handling - Validating both success and failure scenarios - Properly typed with TypeScript
     whenToUse: Write, modify, or maintain integration tests.
@@ -91,7 +91,7 @@ customModes:
   - slug: docs-extractor
     name: 📚 Docs Extractor
     roleDefinition: |-
-      You are Roo, a documentation analysis specialist with two primary functions:
+      You are s2sCopilot, a documentation analysis specialist with two primary functions:
       1. Extract comprehensive technical and non-technical details about features to provide to documentation teams
       2. Verify existing documentation for factual accuracy against the codebase
 
@@ -111,7 +111,7 @@ customModes:
       - mcp
   - slug: pr-fixer
     name: 🛠️ PR Fixer
-    roleDefinition: "You are Roo, a pull request resolution specialist. Your focus is on addressing feedback and resolving issues within existing pull requests. Your expertise includes: - Analyzing PR review comments to understand required changes. - Checking CI/CD workflow statuses to identify failing tests. - Fetching and analyzing test logs to diagnose failures. - Identifying and resolving merge conflicts. - Guiding the user through the resolution process."
+    roleDefinition: "You are s2sCopilot, a pull request resolution specialist. Your focus is on addressing feedback and resolving issues within existing pull requests. Your expertise includes: - Analyzing PR review comments to understand required changes. - Checking CI/CD workflow statuses to identify failing tests. - Fetching and analyzing test logs to diagnose failures. - Identifying and resolving merge conflicts. - Guiding the user through the resolution process."
     whenToUse: Use this mode to fix pull requests. It can analyze PR feedback from GitHub, check for failing tests, and help resolve merge conflicts before applying the necessary code changes.
     description: Fix pull requests.
     groups:
@@ -121,7 +121,7 @@ customModes:
       - mcp
   - slug: issue-investigator
     name: 🕵️ Issue Investigator
-    roleDefinition: You are Roo, a GitHub issue investigator. Your purpose is to analyze GitHub issues, investigate the probable causes using extensive codebase searches, and propose well-reasoned, theoretical solutions. You methodically track your investigation using a todo list, attempting to disprove initial theories to ensure a thorough analysis. Your final output is a human-like, conversational comment for the GitHub issue.
+    roleDefinition: You are s2sCopilot, a GitHub issue investigator. Your purpose is to analyze GitHub issues, investigate the probable causes using extensive codebase searches, and propose well-reasoned, theoretical solutions. You methodically track your investigation using a todo list, attempting to disprove initial theories to ensure a thorough analysis. Your final output is a human-like, conversational comment for the GitHub issue.
     whenToUse: Use this mode when you need to investigate a GitHub issue to understand its root cause and propose a solution. This mode is ideal for triaging issues, providing initial analysis, and suggesting fixes before implementation begins. It uses the `gh` CLI for issue interaction.
     description: Investigates GitHub issues
     groups:
@@ -132,7 +132,7 @@ customModes:
   - slug: merge-resolver
     name: 🔀 Merge Resolver
     roleDefinition: |-
-      You are Roo, a merge conflict resolution specialist with expertise in:
+      You are s2sCopilot, a merge conflict resolution specialist with expertise in:
       - Analyzing pull request merge conflicts using git blame and commit history
       - Understanding code intent through commit messages and diffs
       - Making intelligent decisions about which changes to keep, merge, or discard
@@ -208,7 +208,7 @@ customModes:
   - slug: mode-writer
     name: ✍️ Mode Writer
     roleDefinition: |-
-      You are Roo, a mode creation and editing specialist focused on designing, implementing, and enhancing custom modes for the Roo-Code project. Your expertise includes:
+      You are s2sCopilot, a mode creation and editing specialist focused on designing, implementing, and enhancing custom modes for the Roo-Code project. Your expertise includes:
       - Understanding the mode system architecture and configuration
       - Creating well-structured mode definitions with clear roles and responsibilities
       - Editing and enhancing existing modes while maintaining consistency

@@ -1,29 +1,29 @@
-# Roo Code Privacy Policy
+# s2sCopilot Privacy Policy
 
 **Last Updated: September 11th, 2025**
 
-Roo Code respects your privacy and is committed to transparency about how we handle your data. Below is a simple breakdown of where key pieces of data go—and, importantly, where they don’t.
+s2sCopilot respects your privacy and is committed to transparency about how we handle your data. Below is a simple breakdown of where key pieces of data go—and, importantly, where they don't.
 
 ### **Where Your Data Goes (And Where It Doesn’t)**
 
-- **Code & Files**: Roo Code accesses files on your local machine when needed for AI-assisted features. When you send commands to Roo Code, relevant files may be transmitted to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. If you select Roo Code Cloud as the model provider (proxy mode), your code may transit Roo Code servers only to forward it to the upstream provider. We do not store your code; it is deleted immediately after forwarding. Otherwise, your code is sent directly to the provider. AI providers may store data per their privacy policies.
-- **Commands**: Any commands executed through Roo Code happen on your local environment. However, when you use AI-powered features, the relevant code and context from your commands may be transmitted to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. We do not have access to or store this data, but AI providers may process it per their privacy policies.
+- **Code & Files**: s2sCopilot accesses files on your local machine when needed for AI-assisted features. When you send commands to s2sCopilot, relevant files may be transmitted to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. If you select Roo Code Cloud as the model provider (proxy mode), your code may transit Roo Code servers only to forward it to the upstream provider. We do not store your code; it is deleted immediately after forwarding. Otherwise, your code is sent directly to the provider. AI providers may store data per their privacy policies.
+- **Commands**: Any commands executed through s2sCopilot happen on your local environment. However, when you use AI-powered features, the relevant code and context from your commands may be transmitted to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. We do not have access to or store this data, but AI providers may process it per their privacy policies.
 - **Prompts & AI Requests**: When you use AI-powered features, your prompts and relevant project context are sent to your chosen AI model provider (e.g., OpenAI, Anthropic, OpenRouter) to generate responses. We do not store or process this data. These AI providers have their own privacy policies and may store data per their terms of service. If you choose Roo Code Cloud as the provider (proxy mode), prompts may transit Roo Code servers only to forward them to the upstream model and are not stored.
 - **API Keys & Credentials**: If you enter an API key (e.g., to connect an AI model), it is stored locally on your device and never sent to us or any third party, except the provider you have chosen.
-- **Telemetry (Usage Data)**: We collect anonymous feature usage and error data to help us improve Roo Code. This telemetry is powered by PostHog and includes your VS Code machine ID, feature usage patterns, and exception reports. This telemetry does **not** collect personally identifiable information, your code, or AI prompts. You can opt out of this telemetry at any time through the settings.
-- **Marketplace Requests**: When you browse or search the Marketplace for Model Configuration Profiles (MCPs) or Custom Modes, Roo Code makes a secure API call to Roo Code's backend servers to retrieve listing information. These requests send only the query parameters (e.g., extension version, search term) necessary to fulfill the request and do not include your code, prompts, or personally identifiable information.
+- **Telemetry (Usage Data)**: We collect anonymous feature usage and error data to help us improve s2sCopilot. This telemetry is powered by PostHog and includes your VS Code machine ID, feature usage patterns, and exception reports. This telemetry does **not** collect personally identifiable information, your code, or AI prompts. You can opt out of this telemetry at any time through the settings.
+- **Marketplace Requests**: When you browse or search the Marketplace for Model Configuration Profiles (MCPs) or Custom Modes, s2sCopilot makes a secure API call to s2sCopilot's backend servers to retrieve listing information. These requests send only the query parameters (e.g., extension version, search term) necessary to fulfill the request and do not include your code, prompts, or personally identifiable information.
 
 ### **How We Use Your Data (If Collected)**
 
-- We use telemetry to understand feature usage and improve Roo Code.
+- We use telemetry to understand feature usage and improve s2sCopilot.
 - We do **not** sell or share your data.
 - We do **not** train any models on your data.
 
 ### **Your Choices & Control**
 
 - You can run models locally to prevent data being sent to third-parties.
-- Telemetry collection is enabled by default to help us improve Roo Code, but you can opt out at any time through the settings.
-- You can delete Roo Code to stop all data collection.
+- Telemetry collection is enabled by default to help us improve s2sCopilot, but you can opt out at any time through the settings.
+- You can delete s2sCopilot to stop all data collection.
 
 ### **Security & Updates**
 
@@ -35,4 +35,4 @@ For any privacy-related questions, reach out to us at [email protected].
 
 ---
 
-By using Roo Code, you agree to this Privacy Policy.
+By using s2sCopilot, you agree to this Privacy Policy.