Kilo-Org · markijbema · Jan 21, 2026 · Jan 21, 2026 · Jan 21, 2026 · Jan 21, 2026
diff --git a/apps/kilocode-docs/docs/advanced-usage/rate-limits-costs.md b/apps/kilocode-docs/docs/advanced-usage/rate-limits-costs.md
@@ -46,6 +46,6 @@ If you set the rate limit to 10 seconds, Kilo Code will wait at least 10 seconds
 - **Use Custom Instructions:** Provide custom instructions to guide Kilo Code's behavior and reduce the need for lengthy explanations in each prompt.
 - **Choose the Right Model:** Some models are more cost-effective than others. Consider using a smaller, faster model for tasks that don't require the full power of a larger model.
 - **Use Modes:** Different modes can access different tools, for example `Architect` can't modify code, which makes it a safe choice when analyzing a complex codebase, without worrying about accidentally allowing expensive operations.
-- **Disable MCP If Not Used:** If you're not using MCP (Model Context Protocol) features, consider [disabling it in the MCP settings](/features/mcp/using-mcp-in-kilo-code) to significantly reduce the size of the system prompt and save tokens.
+- **Disable MCP If Not Used:** If you're not using MCP (Model Context Protocol) features, consider [disabling it in Settings > Agent Behaviour > MCP Servers](/features/mcp/using-mcp-in-kilo-code) to significantly reduce the size of the system prompt and save tokens.
 
 By understanding and managing your API usage, you can use Kilo Code effectively and efficiently.
diff --git a/apps/kilocode-docs/docs/agent-behavior/custom-instructions.md b/apps/kilocode-docs/docs/agent-behavior/custom-instructions.md
@@ -14,18 +14,20 @@ Custom Instructions are IDE-wide and are applied across all workspaces and maint
 
 **How to set them:**
 
-<img src="/docs/img/custom-instructions/custom-instructions.png" alt="Kilo Code Modes tab showing global custom instructions interface" width="600" />
-1.  **Open Modes Tab:** Click the <Codicon name="organization" /> icon in the Kilo Code top menu bar
-2.  **Find Section:** Find the "Custom Instructions for All Modes" section
-3.  **Enter Instructions:** Enter your instructions in the text area
-4.  **Save Changes:** Click "Done" to save your changes
+<img src="/docs/img/custom-instructions/custom-instructions.png" alt="Kilo Code Agent Behaviour tab showing global custom instructions interface" width="600" />
+1.  **Open Agent Behaviour Tab:** Click the <Codicon name="gear" /> icon in the Kilo Code top menu bar to open Settings, then select the `Agent Behaviour` tab
+2.  **Select Modes Sub-Tab:** Click on the `Modes` sub-tab
+3.  **Find Section:** Find the "Custom Instructions for All Modes" section
+4.  **Enter Instructions:** Enter your instructions in the text area
+5.  **Save Changes:** Click "Done" to save your changes
 
 #### Mode-Specific Instructions
 
-Mode-specific instructions can be set using the Modes Tab
+Mode-specific instructions can be set using the Agent Behaviour tab
 
-    <img src="/docs/img/custom-instructions/custom-instructions-3.png" alt="Kilo Code Modes tab showing mode-specific custom instructions interface" width="600" />
-    * **Open Tab:** Click the <Codicon name="organization" /> icon in the Kilo Code top menu bar
+    <img src="/docs/img/custom-instructions/custom-instructions-3.png" alt="Kilo Code Agent Behaviour tab showing mode-specific custom instructions interface" width="600" />
+    * **Open Agent Behaviour Tab:** Click the <Codicon name="gear" /> icon in the Kilo Code top menu bar to open Settings, then select the `Agent Behaviour` tab
+    * **Select Modes Sub-Tab:** Click on the `Modes` sub-tab
     * **Select Mode:** Under the Modes heading, click the button for the mode you want to customize
     * **Enter Instructions:** Enter your instructions in the text area under "Mode-specific Custom Instructions (optional)"
     * **Save Changes:** Click "Done" to save your changes

diff --git a/apps/kilocode-docs/docs/agent-behavior/custom-modes.md b/apps/kilocode-docs/docs/agent-behavior/custom-modes.md
@@ -8,7 +8,7 @@ Each mode—including custom ones—features **Sticky Models**. This means Kilo
 
 ## Why Use Custom Modes?
 
-- **Specialization:** Create modes optimized for specific tasks, like "Documentation Writer," "Test Engineer," or "Refactoring Expert"
+- **Specialization:** Create modes optimized for specific tasks, like "Documentation Specialist," "Test Engineer," or "Refactoring Expert"
 - **Safety:** Restrict a mode's access to sensitive files or commands. For example, a "Review Mode" could be limited to read-only operations
 - **Experimentation:** Safely experiment with different prompts and configurations without affecting other modes
 - **Team Collaboration:** Share custom modes with your team to standardize workflows
@@ -47,15 +47,15 @@ Easily share, back up, and template your custom modes. This feature lets you exp
 
 **Exporting a Mode:**
 
-1. Navigate to the Modes view
+1. Navigate to Settings > Agent Behaviour > Modes
 2. Select the mode you wish to export
 3. Click the Export Mode button (download icon)
 4. Choose a location to save the `.yaml` file
 5. Kilo packages the mode's configuration and any rules into the YAML file
 
 **Importing a Mode:**
 
-1. Click the Import Mode button (upload icon) in the Modes view
+1. Click the Import Mode button (upload icon) in the Agent Behaviour > Modes view
 2. Select the mode's YAML file
 3. Choose the import level:
     - **Project:** Available only in current workspace (saved to `.kilocodemodes` file)
@@ -83,9 +83,9 @@ Create a new mode called "Documentation Writer". It should only be able to read
 
 Kilo Code will guide you through the process, prompting for necessary information and creating the mode using the preferred YAML format.
 
-### 2. Using the Prompts Tab
+### 2. Using the Agent Behaviour Tab
 
-1. **Open Prompts Tab:** Click the <Codicon name="notebook" /> icon in the Kilo Code top menu bar
+1. **Open Agent Behaviour Tab:** Click the <Codicon name="gear" /> icon in the Kilo Code top menu bar to open Settings, then select the `Agent Behaviour` tab and the `Modes` sub-tab
 2. **Create New Mode:** Click the <Codicon name="add" /> button to the right of the Modes heading
 3. **Fill in Fields:**
 
@@ -99,8 +99,8 @@ The interface provides fields for Name, Slug, Description, Save Location, Role D
 
 You can directly edit the configuration files to create or modify custom modes. This method offers the most control over all properties. Kilo Code now supports both YAML (preferred) and JSON formats.
 
-- **Global Modes:** Edit the `custom_modes.yaml` (preferred) or `custom_modes.json` file. Access it via Prompts Tab > <Codicon name="gear" /> (Settings Menu icon next to "Global Prompts") > "Edit Global Modes"
-- **Project Modes:** Edit the `.kilocodemodes` file (which can be YAML or JSON) in your project root. Access it via Prompts Tab > <Codicon name="gear" /> (Settings Menu icon next to "Project Prompts") > "Edit Project Modes"
+- **Global Modes:** Edit the `custom_modes.yaml` (preferred) or `custom_modes.json` file. Access it via Settings > Agent Behaviour > Modes > <Codicon name="gear" /> (Settings Menu icon next to "Global Modes") > "Edit Global Modes"
+- **Project Modes:** Edit the `.kilocodemodes` file (which can be YAML or JSON) in your project root. Access it via Settings > Agent Behaviour > Modes > <Codicon name="gear" /> (Settings Menu icon next to "Project Modes") > "Edit Project Modes"
 
 These files define an array/list of custom modes.
 

diff --git a/apps/kilocode-docs/docs/features/auto-approving-actions.md b/apps/kilocode-docs/docs/features/auto-approving-actions.md
@@ -213,11 +213,11 @@ The delay controls how long Kilo Code waits before trying again:
 
 **Setting:** "Always approve MCP tools"
 
-**Description:** "Enable auto-approval of individual MCP tools in the MCP Servers view (requires both this setting and the tool's individual 'Always allow' checkbox)"
+**Description:** "Enable auto-approval of individual MCP tools in the Agent Behaviour > MCP Servers view (requires both this setting and the tool's individual 'Always allow' checkbox)"
 
 **Risk level:** Medium-High (depends on configured MCP tools)
 
-This setting works in conjunction with individual tool permissions in the MCP Servers view. Both this global setting and the tool-specific permission must be enabled for auto-approval.
+This setting works in conjunction with individual tool permissions in the Agent Behaviour > MCP Servers view. Both this global setting and the tool-specific permission must be enabled for auto-approval.
 :::
 
 ### Mode Switching

diff --git a/apps/kilocode-docs/docs/features/mcp/using-mcp-in-kilo-code.md b/apps/kilocode-docs/docs/features/mcp/using-mcp-in-kilo-code.md
@@ -23,11 +23,11 @@ MCP server configurations can be managed at two levels:
 
 ### Editing MCP Settings Files
 
-You can edit both global and project-level MCP configuration files directly from the Kilo Code MCP settings view.
+You can edit both global and project-level MCP configuration files directly from the Kilo Code settings.
 
 1. Click the <Codicon name="gear" /> icon in the top navigation of the Kilo Code pane to open `Settings`.
-2. Click the `MCP Servers` tab on the left side
-3. Choose the `Installed` servers
+2. Click the `Agent Behaviour` tab on the left side
+3. Select the `MCP Servers` sub-tab
 4. Click the appropriate button:
     - **`Edit Global MCP`**: Opens the global `mcp_settings.json` file.
     - **`Edit Project MCP`**: Opens the project-specific `.kilocode/mcp.json` file. If this file doesn't exist, Kilo Code will create it for you.
@@ -174,7 +174,7 @@ To set the maximum time to wait for a response after a tool call to the MCP serv
 MCP tool auto-approval works on a per-tool basis and is disabled by default. To configure auto-approval:
 
 1. First enable the global "Use MCP servers" auto-approval option in [auto-approving-actions](/features/auto-approving-actions)
-2. In the MCP server settings, locate the specific tool you want to auto-approve
+2. Navigate to Settings > Agent Behaviour > MCP Servers, then locate the specific tool you want to auto-approve
 3. Check the `Always allow` checkbox next to the tool name
 
 <img src="/docs/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-7.png" alt="Always allow checkbox for MCP tools" width="120" />

diff --git a/apps/kilocode-docs/docs/tips-and-tricks.md b/apps/kilocode-docs/docs/tips-and-tricks.md
@@ -11,7 +11,7 @@ A collection of quick tips to help you get the most out of Kilo Code.
     - Use chat for multi-file changes, refactoring, or when you need to explain intent. Use autocomplete for quick, localized edits where the context is already clear from surrounding code.
     - Steer autocomplete by writing a comment describing what you want before triggering it, or by typing a function signature—autocomplete will fill in the implementation.
     - Treat autocomplete suggestions as drafts: accept them quickly, then refine. It's often faster to fix a 90% correct suggestion than to craft the perfect prompt.
-- If you're not using [MCP](/features/mcp/overview), turn it off in the <Codicon name="notebook" /> Prompts tab to significantly cut down the size of the system prompt.
+- If you're not using [MCP](/features/mcp/overview), turn it off in Settings > Agent Behaviour > MCP Servers to significantly cut down the size of the system prompt.
 - To keep your [custom modes](/agent-behavior/custom-modes) on track, limit the types of files that they're allowed to edit.
 - If you hit the dreaded `input length and max tokens exceed context limit` error, you can recover by deleting a message, rolling back to a previous checkpoint, or switching over to a model with a long context window like Gemini for a message.
 - In general, be thoughtful about your `Max Tokens` setting for thinking models. Every token you allocate to that takes away from space available to store conversation history. Consider only using high `Max Tokens` / `Max Thinking Tokens` settings with modes like Architect and Debug, and keeping Code mode at 16k max tokens or less.

diff --git a/apps/kilocode-docs/static/img/custom-modes/custom-modes-1.png b/apps/kilocode-docs/static/img/custom-modes/custom-modes-1.png
diff --git a/apps/kilocode-docs/static/img/custom-modes/custom-modes-2.png b/apps/kilocode-docs/static/img/custom-modes/custom-modes-2.png
diff --git a/apps/kilocode-docs/static/img/custom-modes/custom-modes.png b/apps/kilocode-docs/static/img/custom-modes/custom-modes.png
diff --git a/apps/kilocode-docs/static/img/using-mcp-in-kilo-code/mcp-installed-config.png b/apps/kilocode-docs/static/img/using-mcp-in-kilo-code/mcp-installed-config.png