Zoo-Code-Org · taltas · May 6, 2026 · May 8, 2026 · May 11, 2026 · May 11, 2026
@@ -1,6 +1,6 @@
-# Roo Code Docs
+# Zoo Code Docs
 
-This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator, and lives at https://docs.roocode.com
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator, and lives at https://docs.zoocode.dev
 
 ### Installation
 

@@ -1,18 +1,18 @@
 ---
-description: Learn how the access_mcp_resource tool retrieves data from Model Context Protocol servers for additional context in Roo Code tasks.
+description: Learn how the access_mcp_resource tool retrieves data from Model Context Protocol servers for additional context in Zoo Code tasks.
 keywords:
   - access_mcp_resource
   - MCP
   - Model Context Protocol
   - MCP resources
-  - Roo Code tools
+  - Zoo Code tools
   - context retrieval
   - API integration
 ---
 
 # access_mcp_resource
 
-The `access_mcp_resource` tool retrieves data from resources exposed by connected Model Context Protocol (MCP) servers. It allows Roo to access files, API responses, documentation, or system information that provides additional context for tasks.
+The `access_mcp_resource` tool retrieves data from resources exposed by connected Model Context Protocol (MCP) servers. It allows Zoo to access files, API responses, documentation, or system information that provides additional context for tasks.
 
 ---
 

@@ -6,7 +6,7 @@ keywords:
   - code modifications
   - fuzzy matching
   - diff tool
-  - Roo Code tools
+  - Zoo Code tools
   - multi-file edits
 ---
 
@@ -35,7 +35,7 @@ This tool applies targeted changes to existing files using fuzzy matching guided
 
 ## When is it used?
 
-- When Roo needs to make precise changes to existing code without rewriting entire files.
+- When Zoo needs to make precise changes to existing code without rewriting entire files.
 - When refactoring specific sections of code while maintaining surrounding context.
 - When fixing bugs in existing code with surgical precision.
 - When implementing feature enhancements that modify only certain parts of a file.

@@ -6,7 +6,7 @@ keywords:
   - unified diff
   - multi-file edits
   - file operations
-  - Roo Code tools
+  - Zoo Code tools
   - diff patches
 ---
 

@@ -1,10 +1,10 @@
 ---
-description: Enable interactive communication in Roo Code with the ask_followup_question tool for gathering clarification and user preferences.
+description: Enable interactive communication in Zoo Code with the ask_followup_question tool for gathering clarification and user preferences.
 keywords:
   - ask_followup_question
   - user interaction
   - interactive communication
-  - Roo Code tools
+  - Zoo Code tools
   - clarification
   - user feedback
 ---
@@ -26,16 +26,16 @@ The tool accepts these parameters:
 
 ## What It Does
 
-This tool creates a conversational interface between Roo and the user, allowing for gathering clarification, additional details, or user preferences when facing ambiguities or decision points. Each question can include suggested responses to streamline the interaction.
+This tool creates a conversational interface between Zoo and the user, allowing for gathering clarification, additional details, or user preferences when facing ambiguities or decision points. Each question can include suggested responses to streamline the interaction.
 
 ---
 
 ## When is it used?
 
 - When critical information is missing from the original request
-- When Roo needs to choose between multiple valid implementation approaches
+- When Zoo needs to choose between multiple valid implementation approaches
 - When technical details or preferences are required to proceed
-- When Roo encounters ambiguities that need resolution
+- When Zoo encounters ambiguities that need resolution
 - When additional context would significantly improve the solution quality
 
 ---
@@ -113,9 +113,9 @@ When the `ask_followup_question` tool is invoked, it follows this process:
 
 The question-answer cycle follows this sequence:
 
-1. **Information Gap Recognition**: Roo identifies missing information needed to proceed
-2. **Specific Question Creation**: Roo formulates a clear, targeted question
-3. **Suggestion Development**: Roo creates relevant suggested answers (optional but recommended)
+1. **Information Gap Recognition**: Zoo identifies missing information needed to proceed
+2. **Specific Question Creation**: Zoo formulates a clear, targeted question
+3. **Suggestion Development**: Zoo creates relevant suggested answers (optional but recommended)
 4. **Tool Invocation**: Assistant invokes the tool with question and optional suggestions
 5. **UI Presentation**: Question and suggestions are displayed to the user as interactive elements
 6. **User Response**: The user selects a suggestion or provides a custom answer
@@ -125,18 +125,18 @@ The question-answer cycle follows this sequence:
    - Maintains state consistency regardless of message chunking
 8. **Response Processing**: System wraps the response in `<answer>` tags and preserves images
 9. **Context Integration**: Response is added to the conversation history
-10. **Task Continuation**: Roo proceeds with the task using the new information
+10. **Task Continuation**: Zoo proceeds with the task using the new information
 
 ---
 
 ## Examples When Used
 
-- When developing a web application, Roo might ask about preferred styling frameworks (Bootstrap, Tailwind, custom CSS)
-- When creating an API, Roo might ask about authentication methods (JWT, OAuth, API keys)
-- When refactoring code, Roo might ask about prioritizing performance vs. readability
-- When setting up a database, Roo might ask about specific schema design preferences
-- When creating a custom feature, Roo might ask about specific behavior expectations
-- When troubleshooting errors, Roo might ask about specific environment details
+- When developing a web application, Zoo might ask about preferred styling frameworks (Bootstrap, Tailwind, custom CSS)
+- When creating an API, Zoo might ask about authentication methods (JWT, OAuth, API keys)
+- When refactoring code, Zoo might ask about prioritizing performance vs. readability
+- When setting up a database, Zoo might ask about specific schema design preferences
+- When creating a custom feature, Zoo might ask about specific behavior expectations
+- When troubleshooting errors, Zoo might ask about specific environment details
 
 ---
 

@@ -3,15 +3,15 @@ description: Learn about context poisoning in AI coding assistants, its symptoms
 keywords:
   - context poisoning
   - AI accuracy
-  - Roo Code troubleshooting
+  - Zoo Code troubleshooting
   - LLM context management
   - session recovery
 ---
 
 # Context Poisoning
 
 :::info
-Context poisoning is a persistent issue within a given session. Once a chat session's context is compromised, treat that session as disposable. Starting fresh with a clean context is crucial for maintaining the accuracy and effectiveness of your Roo Code agent.
+Context poisoning is a persistent issue within a given session. Once a chat session's context is compromised, treat that session as disposable. Starting fresh with a clean context is crucial for maintaining the accuracy and effectiveness of your Zoo Code agent.
 :::
 
 Context poisoning occurs when inaccurate or irrelevant data contaminates the language model's active context. This leads the model to draw incorrect conclusions, provide erroneous information to tools, and progressively deviate from the intended task with each interaction.

@@ -1,29 +1,29 @@
 ---
-description: Learn strategies for effectively using Roo Code with large codebases. Manage context limits, optimize token usage, and handle complex refactoring tasks.
+description: Learn strategies for effectively using Zoo Code with large codebases. Manage context limits, optimize token usage, and handle complex refactoring tasks.
 keywords:
   - large projects
   - context management
   - token optimization
   - codebase refactoring
-  - Roo Code scalability
+  - Zoo Code scalability
 ---
 
 # Working with Large Projects
 
-Roo Code can be used with projects of any size, but large projects require some extra care to manage context effectively. Here are some tips for working with large codebases:
+Zoo Code can be used with projects of any size, but large projects require some extra care to manage context effectively. Here are some tips for working with large codebases:
 
 ---
 
 ## Understanding Context Limits
 
-Roo Code uses large language models (LLMs) that have a limited "context window."  This is the maximum amount of text (measured in tokens) that the model can process at once.  If the context is too large, the model may not be able to understand your request or generate accurate responses.
+Zoo Code uses large language models (LLMs) that have a limited "context window."  This is the maximum amount of text (measured in tokens) that the model can process at once.  If the context is too large, the model may not be able to understand your request or generate accurate responses.
 
 The context window includes:
 
-*   The system prompt (instructions for Roo Code).
+*   The system prompt (instructions for Zoo Code).
 *   The conversation history.
 *   The content of any files you mention using `@`.
-*   The output of any commands or tools Roo Code uses.
+*   The output of any commands or tools Zoo Code uses.
 
 ---
 
@@ -37,7 +37,7 @@ The context window includes:
 
 4.  **Summarize:**  If you need to refer to a large amount of code, consider summarizing the relevant parts in your prompt instead of including the entire code.
 
-5.  **Prioritize Recent History:** Roo Code automatically truncates older messages in the conversation history to stay within the context window. Be mindful of this, and re-include important context if needed.
+5.  **Prioritize Recent History:** Zoo Code automatically truncates older messages in the conversation history to stay within the context window. Be mindful of this, and re-include important context if needed.
 
 6.  **Use Prompt Caching (if available):** Some API providers like Anthropic, OpenAI, OpenRouter and Requesty support "prompt caching". This caches your prompts for use in future tasks and helps reduce the cost and latency of requests.
 
@@ -59,4 +59,4 @@ Let's say you need to refactor a large TypeScript file (`src/components/MyCompon
 
 3.  **Iterative Changes:**  Make small, incremental changes, reviewing and approving each step.
 
-By breaking down the task and providing specific context, you can work effectively with large files even with a limited context window.
+By breaking down the task and providing specific context, you can work effectively with large files even with a limited context window.
@@ -1,9 +1,9 @@
 ---
-description: Learn how to set up Roo Code for local development, build from source, and contribute to the project. Complete developer setup guide.
+description: Learn how to set up Zoo Code for local development, build from source, and contribute to the project. Complete developer setup guide.
 keywords:
   - local development
   - build from source
-  - Roo Code development
+  - Zoo Code development
   - contribute
   - developer setup
 sidebar_label: Local Development Setup
@@ -12,19 +12,19 @@ sidebar_label: Local Development Setup
 ## Local Setup & Development
 
 :::note Developer Information Only
-This section is for developers contributing to Roo Code or those who wish to build and run the extension from source.
+This section is for developers contributing to Zoo Code or those who wish to build and run the extension from source.
 :::
 
-To set up Roo Code for local development:
+To set up Zoo Code for local development:
 
 1.  **Clone the repository:**
     ```bash
-    git clone https://github.com/RooCodeInc/Roo-Code.git
+    git clone https://github.com/Zoo-Code-Org/Zoo-Code.git
     cd Roo-Code
     ```
 
 2.  **Install dependencies:**
-    Roo Code uses `pnpm` for package management.
+    Zoo Code uses `pnpm` for package management.
     ```bash
     pnpm install
     ```
@@ -34,7 +34,7 @@ To set up Roo Code for local development:
 
     *   **Directly in VS Code (Recommended for active development):**
         *   Open the cloned `Roo-Code` folder in VS Code.
-        *   Press `F5` (or select **Run** → **Start Debugging** from the menu). This opens a new VS Code window (Extension Development Host) with Roo Code running.
+        *   Press `F5` (or select **Run** → **Start Debugging** from the menu). This opens a new VS Code window (Extension Development Host) with Zoo Code running.
         *   Changes to the webview code (under `webview-ui/`) will often update live.
         *   Changes to the core extension code (under `src/`) typically require restarting the Extension Development Host window.
 
@@ -59,4 +59,4 @@ To set up Roo Code for local development:
                 *   Browse to and select the generated `.vsix` file from the `bin/` directory.
 
                 <img src="/img/installing/installing-2.png" alt="VS Code's Install from VSIX dialog" width="600" />
-                *Installing a development VSIX using VS Code's "Install from VSIX..." dialog.*
+                *Installing a development VSIX using VS Code's "Install from VSIX..." dialog.*
@@ -1,5 +1,5 @@
 ---
-description: Learn how to run Roo Code with local AI models using Ollama and LM Studio. Complete setup guide for offline AI coding assistance.
+description: Learn how to run Zoo Code with local AI models using Ollama and LM Studio. Complete setup guide for offline AI coding assistance.
 keywords:
   - local models
   - Ollama
@@ -12,10 +12,10 @@ keywords:
 
 # Using Local Models
 
-Roo Code supports running language models locally on your own machine using [Ollama](https://ollama.com/) and [LM Studio](https://lmstudio.ai/).  This offers several advantages:
+Zoo Code supports running language models locally on your own machine using [Ollama](https://ollama.com/) and [LM Studio](https://lmstudio.ai/).  This offers several advantages:
 
 *   **Privacy:** Your code and data never leave your computer.
-*   **Offline Access:**  You can use Roo Code even without an internet connection.
+*   **Offline Access:**  You can use Zoo Code even without an internet connection.
 *   **Cost Savings:**  Avoid API usage fees associated with cloud-based models.
 *   **Customization:**  Experiment with different models and configurations.
 
@@ -30,7 +30,7 @@ Roo Code supports running language models locally on your own machine using [Oll
 
 ## Supported Local Model Providers
 
-Roo Code currently supports two main local model providers:
+Zoo Code currently supports two main local model providers:
 
 1.  **Ollama:**  A popular open-source tool for running large language models locally.  It supports a wide range of models.
 2.  **LM Studio:**  A user-friendly desktop application that simplifies the process of downloading, configuring, and running local models.  It also provides a local server that emulates the OpenAI API.
@@ -49,7 +49,7 @@ Both providers offer similar capabilities but with different user interfaces and
 
 ## Troubleshooting
 
-*   **"No connection could be made because the target machine actively refused it":**  This usually means that the Ollama or LM Studio server isn't running, or is running on a different port/address than Roo Code is configured to use.  Double-check the Base URL setting.
+*   **"No connection could be made because the target machine actively refused it":**  This usually means that the Ollama or LM Studio server isn't running, or is running on a different port/address than Zoo Code is configured to use.  Double-check the Base URL setting.
 
 *   **Slow Response Times:** Local models can be slower than cloud-based models, especially on less powerful hardware.  If performance is an issue, try using a smaller model.