From f7bd5c7af13b0ba74bde261efc3a824037cae9c2 Mon Sep 17 00:00:00 2001
From: Joshua Lambert <25085430+lambertjosh@users.noreply.github.com>
Date: Thu, 26 Feb 2026 09:26:16 -0500
Subject: [PATCH] Apply suggestion from @lambertjosh

---
 packages/kilo-docs/pages/automate/mcp/using-in-cli.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/kilo-docs/pages/automate/mcp/using-in-cli.md b/packages/kilo-docs/pages/automate/mcp/using-in-cli.md
index 52c75255ea3..7daac1e1fca 100644
--- a/packages/kilo-docs/pages/automate/mcp/using-in-cli.md
+++ b/packages/kilo-docs/pages/automate/mcp/using-in-cli.md
@@ -20,7 +20,7 @@ The CLI accepts several config filenames. The recommended file is `kilo.json`:
 | **Global**  | `~/.config/kilo/kilo.json`            | `kilo.jsonc`, `config.json`                           |
 | **Project** | `./kilo.json` or `./.kilo/kilo.json`  | `kilo.jsonc`                                          |
 
-Project-level configuration takes precedence over global settings. The CLI walks up from the project directory to the git worktree root, so config files in parent directories are also loaded.
+Project-level configuration takes precedence over global settings. 
 
 MCP servers configured in VS Code are **not** automatically available in the CLI. You must configure them separately.