`
- - Images should start with `/img/` path
- - Include brief description below complex images
-
- #### 12. **Eliminate Filler Words**
- Remove: "simply," "just," "easily," "obviously," "of course," "as you can see." These add cognitive load without value.
-
- #### 13. **Progressive Disclosure**
- Start with the essential information. Add detail as needed. Use expandable sections or links to deeper content for advanced users.
-
- #### 14. **Consistency Checklist**
- - Use same terminology for same concepts
- - Follow identical formatting patterns
- - Maintain consistent voice and tone
- - Verify all links and code examples work
- - Check accessibility with screen reader preview
-
- groups:
- - read
- - command
- - edit
- source: project
-
- - slug: posts
- name: Blog Post Author
- roleDefinition: You are a technical blog author who applies Smart Brevity principles to make complex development topics accessible and engaging. With 24 years of experience, you write with authentic candor and technical precision, helping developers quickly understand why they should care about Kilo Code features. Your friendly, conversational tone includes light humor while maintaining professional credibility. You specialize in translating documentation into compelling stories that show real-world value, always leading with the problem being solved rather than the solution being offered.
- customInstructions: >-
- ### Smart Brevity Blog Standards
-
- #### 1. **Hook with Value** (Smart Brevity Core)
- Open every post by stating the problem this feature/topic solves. Lead with "why this matters" before explaining "what it does." Make the value clear in the first paragraph.
-
- #### 2. **One Big Thing Focus**
- Each blog post should have one main takeaway readers can act on immediately. State it early and reinforce it throughout.
-
- #### 3. **Scannable and Engaging**
- - Use subheadings that ask questions or promise benefits
- - Keep paragraphs short (2-3 sentences max)
- - Include bullet points for key benefits or steps
- - Add light humor or personality without compromising clarity
- - Bold important concepts and features
-
- #### 4. **Real-World Context**
- Show how experienced developers actually use these features. Skip toy examples—demonstrate genuine productivity gains and workflow improvements.
-
- #### 5. **Documentation Integration**
- - Link to relevant docs using absolute URLs
- - Example: `[Complete Setup Guide](https://kilocode.ai/docs/configuration/)`
- - Reference specific documentation sections to drive deeper engagement
- - Make it easy to go from blog interest to documentation action
-
- #### 6. **Accessible Technical Writing**
- - Define acronyms and technical terms when they impact understanding
- - Use parallel structure in lists and explanations
- - Provide context for workflows and processes
- - Consider readers with varying attention spans and learning styles
-
- #### 7. **Problem-Solution Structure**
- - Start with relatable developer pain point
- - Show how Kilo Code addresses it specifically
- - Provide concrete example or walkthrough
- - End with clear next steps or call to action
-
- #### 8. **Code with Context**
- - Include realistic, copy-pasteable code examples
- - Show before/after scenarios when relevant
- - Provide syntax highlighting and proper formatting
- - Explain why the code works, not just how
-
- #### 9. **Visual Storytelling**
- - Use images from documentation: `
`
- - Include screenshots that support the narrative
- - Add brief descriptions for complex visuals
- - Show UI paths with backticks: `Settings → Prompts → Feature Name`
-
- #### 10. **Friendly Authority**
- - Write conversationally but maintain technical credibility
- - Include 1-2 appropriate jokes or light observations per post
- - Acknowledge common frustrations developers face
- - Share insights from real usage patterns
-
- #### 11. **Clear Navigation**
- - End posts with specific next steps
- - Link to relevant documentation sections
- - Suggest related features or workflows
- - Make it easy for readers to continue their journey
-
- #### 12. **Elimination Editing**
- Remove marketing speak, unnecessary qualifiers, and filler words. Every sentence should advance understanding or provide value.
-
- groups:
- - read
- - edit
- source: project
diff --git a/packages/kilo-docs/.kilocoderules b/packages/kilo-docs/.kilocoderules
deleted file mode 100644
index d0f5aa5ee5a..00000000000
--- a/packages/kilo-docs/.kilocoderules
+++ /dev/null
@@ -1,31 +0,0 @@
-# Kilo Code Documentation Rules
-
-## Documentation Links
-- Do not include .md extensions in documentation links
-- Use absolute paths starting from the `/docs/` root for internal documentation links
-- Example: [link text](/basic-usage/how-tools-work) NOT [link text](basic-usage/how-tools-work.md) or [link text](../../basic-usage/how-tools-work)
-
-This ensures links work correctly in the built documentation while maintaining clean URLs.
-
-## Image References
-- Use `/docs/img/` prefix for all image paths in documentation
-- Example: `
`
-- NOT: `
` or `
`
-
-## Component Imports
-- Import custom components from `@site/src/components/` using absolute paths
-- Import constants from `@site/src/constants.ts`
-- Examples:
- - `import Image from '@site/src/components/Image';`
- - `import { DISCORD_URL } from '@site/src/constants.ts'`
- - `import Codicon from '@site/src/components/Codicon';`
-
-## External Link References
-- Use constants from `src/constants.ts` for external URLs instead of hardcoding
-- Example: `
+
+We want to convert them to Markdoc image tags like this:
+
+{% image src="/docs/img/kilo-provider/connected-accounts.png" alt="Connect account screen" width="800" caption="Connect account screen" /%}
+
+Note that this site is served under kilo.ai/docs so the `/docs` MUST be present in every image tag.
+
+Image attributes
+
+```json
+ src: {
+ type: String,
+ required: true,
+ description: "The image source URL",
+ },
+ alt: {
+ type: String,
+ required: true,
+ description: "Alternative text for the image",
+ },
+ width: {
+ type: String,
+ description: "Width of the image (e.g., '500px', '80%')",
+ },
+ height: {
+ type: String,
+ description: "Height of the image (e.g., '300px', 'auto')",
+ },
+ caption: {
+ type: String,
+ description: "Optional caption displayed below the image",
+ }
+```
+
+### Callouts
+
+Callouts in Docusaurus look like this:
+
+```markdown
+:::info
+
+You can report any bugs or feedbacks by chatting with us in our [Discord server](https://discord.gg/ovhcloud), in the AI Endpoints channel.
+
+:::
+```
+
+We want to convert them to Markdoc callout tags like this:
+
+```markdown
+{% callout type="info" %}
+You can report any bugs or feedbacks by chatting with us in our [Discord server](https://discord.gg/ovhcloud), in the AI Endpoints channel.
+{% /callout %}
+```
+
+Callout Attributes:
+
+```json
+ title: {
+ type: String,
+ description: "Optional custom title for the callout",
+ },
+ type: {
+ type: String,
+ default: "note",
+ matches: ["generic", "note", "tip", "info", "warning", "danger"],
+ description:
+ "The type of callout: generic (no icon/title), note, tip, info, warning, or danger",
+ },
+ collapsed: {
+ type: Boolean,
+ default: false,
+ description:
+ "When true, the callout starts collapsed and can be expanded by clicking the header",
+ }
+```
+
+### Codicons
+
+Codicon icons look like this:
+
+```html
+
-```
-$ pnpm install
+## Setup
+
+First, clone this repo and install the dependencies required:
+
+```bash
+npm install
+# or
+yarn install
```
-### Local Development
+Then, run the development server:
-```
-$ pnpm docs:start
+```bash
+npm run dev
+# or
+yarn dev
```
-This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server
+Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
+
+You can start editing the page by modifying `index.md`. The page auto-updates as you edit the file.
+
+## Deploy
+
+The quickest way to deploy your own version of this boilerplate is by deploying it with [Vercel](https://vercel.com) or [Netlify](https://www.netlify.com/) by clicking one of the buttons below.
+
+### Deploy with Vercel
+
+[](https://vercel.com/new/clone?repository-url=https://github.com/markdoc/next.js-starter)
+
+### Deploy to Netlify
+
+[](https://app.netlify.com/start/deploy?repository=https://github.com/markdoc/next.js-starter)
diff --git a/packages/kilo-docs/blog-posts/auto-generate-commit-messages.md b/packages/kilo-docs/blog-posts/auto-generate-commit-messages.md
deleted file mode 100644
index d7c7c4aea5e..00000000000
--- a/packages/kilo-docs/blog-posts/auto-generate-commit-messages.md
+++ /dev/null
@@ -1,108 +0,0 @@
-# Why I Let AI Write My Commit Messages
-
-### And Probably You Should Too
-
-I've just finished implementing a big feature, the code is staged and ready to go, but there I am — mesmerized by the empty commit message field, brain is blank. What do I write? "Fixed stuff"? "Updates"? "asdf"? Do you know that feeling too?
-
-I've been there countless times, and honestly, it's one of those tiny friction points that really bother me - or, better to say, bothered me, because since we shipped `auto-generate commit messages feature`, the problem disappeared for good. That feature became one of those things where once I have it, I wonder how I ever lived without it.
-
-## The Problem with Commit Messages
-
-**Writing good commit messages is hard.** Like, genuinely difficult. You need to:
-
-- Summarize what changed without being too vague
-- Follow your team's conventions (Conventional Commits, anyone?)
-- Capture the _why_ behind the change, which is often harder than the _what_
-- Keep it concise but informative
-- Do all this while your brain is already moving on to the coffee machine
-
-The result? Most of us end up with commit histories that look like something between an archaeological mystery and a stand-up show. Future you (or your teammates) trying to understand why something was changed becomes an exercise in detective work.
-
-## How It Actually Works
-
-Here's the thing that makes this feature genuinely useful: it only looks at your **staged changes**. Not your entire working directory, not random files you've been tinkering with—just the specific changes you've decided to commit.
-
-This is crucial because it means the AI understands the scope of what you're actually committing. It can see that you added a new authentication method, fixed a specific bug, or updated documentation, and it crafts the message accordingly.
-
-The process is dead simple:
-
-1. Stage your changes (like you normally would)
-2. Click the Kilo Code logo next to the commit message field
-3. Get a properly formatted commit message - automagically!
-
-
-
-## Real Examples from Real Work
-
-Let me show you some actual commit messages this feature has generated for me:
-
-```
-feat(auth): implement OAuth2 integration with GitHub
-
-Add GitHub OAuth2 authentication flow including:
-- OAuth2 client configuration
-- User profile retrieval
-- Token refresh mechanism
-```
-
-```
-fix(api): resolve race condition in user session handling
-
-Add proper locking mechanism to prevent concurrent
-session updates from causing data corruption
-```
-
-```
-docs(readme): update installation requirements
-
-Clarify Node.js version requirements and add
-troubleshooting section for common setup issues
-```
-
-Notice how these follow [Conventional Commits](https://www.conventionalcommits.org/) format by default? That's not an accident. The feature understands modern commit conventions best practices and applying them automatically.
-
-## The Customization That Actually Matters
-
-Here's where it gets interesting. You can customize the prompt template to match your team's specific needs or your own preferences. Don't want to be "too conventional" or just have your own standards? Maybe you want to use a different commit format, or you want to include ticket numbers, your git username or you have specific terminology for your project?
-
-Just head to `Settings → Prompts → Commit Message Generation` and modify the template. The AI will adapt to your requirements while still understanding the technical context of your changes.
-
-
-
-## Why This Isn't Just Another AI Gimmick
-
-I've seen plenty of AI features that feel like solutions looking for problems. This isn't one of them, it actually works:
-
-**It's contextually aware**: The AI sees your actual code changeset, not just filenames. It understands when you've added error handling, refactored a function, or fixed a typo.
-
-**It respects your workflow**: You still stage changes the same way. You still review and edit the message if needed. It just removes the blank-page problem.
-
-**It's fast**: No waiting around for some cloud service to analyze your entire codebase. It's quick and focused.
-
-**It follows your patterns**: The more you adjust it, the better it gets at matching your project's style and conventions.
-
-## The Productivity Impact
-
-Here's the thing I didn't expect: this feature doesn't just save time on writing commit messages. It actually makes me commit more frequently and more conciously.
-
-When writing commit messages was a friction point, I'd sometimes batch unrelated changes together just to avoid writing multiple messages. Just squeeze everything into a bucket and throw it at the server, like `git add . && git commit -m "blablabla" && git push`. Now, I commit logical chunks of work as I complete them, which leads to a much cleaner git history.
-
-Better commit messages also mean better code reviews. When your teammates can quickly understand what each commit does, the entire review process becomes more efficient.
-
-## Getting Started
-
-The feature is available in Kilo Code since `v4.35` and became customizable in `v4.38`. Just make sure you have some staged changes, and look for the Kilo Code logo in your VS Code Source Control panel.
-
-Pro tip: Consider setting up a dedicated [API configuration profile](https://kilo.ai/docs/features/api-configuration-profiles/) with a faster, cheaper model specifically for commit message generation. You don't need the most powerful model for this task, and it'll save you some API costs and time - yes, it's exactly what we did in [2x Faster, 30x Cheaper Prompt Enhancement](https://blog.kilo.ai/p/2x-faster-prompt-enhancement-in-kilo)!
-
-## One More Thing
-
-I mentioned I use this feature constantly, and that's not hyperbole. It's become such a natural part of my workflow that I actually get annoyed when I have to write commit messages manually.
-
-That's the mark of a good tool — when it "dissolves" into your workflow and just makes everything smoother. No fanfare, just one less thing to think about so you can focus on what actually matters: writing great code.
-
-Give it a try. I think you'll find yourself wondering how you ever managed without it.
-
----
-
-_Want to learn more about Kilo Code's commit message generation? Check out the [full documentation](https://kilo.ai/docs/basic-usage/git-commit-generation/) I wrote for setup details. And let me know what you think about it or how could we improve it even more here in comments or on our [Discord Server](https://kilo.ai/discord)!_
diff --git a/packages/kilo-docs/bun.lock b/packages/kilo-docs/bun.lock
new file mode 100644
index 00000000000..e70a30bdf99
--- /dev/null
+++ b/packages/kilo-docs/bun.lock
@@ -0,0 +1,269 @@
+{
+ "lockfileVersion": 1,
+ "workspaces": {
+ "": {
+ "dependencies": {
+ "@markdoc/markdoc": "latest",
+ "@markdoc/next.js": "latest",
+ "@vscode/codicons": "^0.0.44",
+ "next": "latest",
+ "prismjs": "latest",
+ "react": "latest",
+ "react-dom": "latest",
+ },
+ "devDependencies": {
+ "@tailwindcss/postcss": "^4.1.18",
+ "@types/node": "latest",
+ "@types/react": "latest",
+ "@types/react-dom": "latest",
+ "autoprefixer": "^10.4.23",
+ "postcss": "^8.5.6",
+ "tailwindcss": "^4.1.18",
+ "typescript": "latest",
+ },
+ },
+ },
+ "packages": {
+ "@alloc/quick-lru": ["@alloc/quick-lru@5.2.0", "", {}, "sha512-UrcABB+4bUrFABwbluTIBErXwvbsU/V7TZWfmbgJfbkwiBuziS9gxdODUyuiecfdGQ85jglMW6juS3+z5TsKLw=="],
+
+ "@emnapi/runtime": ["@emnapi/runtime@1.8.1", "", { "dependencies": { "tslib": "^2.4.0" } }, "sha512-mehfKSMWjjNol8659Z8KxEMrdSJDDot5SXMq00dM8BN4o+CLNXQ0xH2V7EchNHV4RmbZLmmPdEaXZc5H2FXmDg=="],
+
+ "@img/colour": ["@img/colour@1.0.0", "", {}, "sha512-A5P/LfWGFSl6nsckYtjw9da+19jB8hkJ6ACTGcDfEJ0aE+l2n2El7dsVM7UVHZQ9s2lmYMWlrS21YLy2IR1LUw=="],
+
+ "@img/sharp-darwin-arm64": ["@img/sharp-darwin-arm64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-darwin-arm64": "1.2.4" }, "os": "darwin", "cpu": "arm64" }, "sha512-imtQ3WMJXbMY4fxb/Ndp6HBTNVtWCUI0WdobyheGf5+ad6xX8VIDO8u2xE4qc/fr08CKG/7dDseFtn6M6g/r3w=="],
+
+ "@img/sharp-darwin-x64": ["@img/sharp-darwin-x64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-darwin-x64": "1.2.4" }, "os": "darwin", "cpu": "x64" }, "sha512-YNEFAF/4KQ/PeW0N+r+aVVsoIY0/qxxikF2SWdp+NRkmMB7y9LBZAVqQ4yhGCm/H3H270OSykqmQMKLBhBJDEw=="],
+
+ "@img/sharp-libvips-darwin-arm64": ["@img/sharp-libvips-darwin-arm64@1.2.4", "", { "os": "darwin", "cpu": "arm64" }, "sha512-zqjjo7RatFfFoP0MkQ51jfuFZBnVE2pRiaydKJ1G/rHZvnsrHAOcQALIi9sA5co5xenQdTugCvtb1cuf78Vf4g=="],
+
+ "@img/sharp-libvips-darwin-x64": ["@img/sharp-libvips-darwin-x64@1.2.4", "", { "os": "darwin", "cpu": "x64" }, "sha512-1IOd5xfVhlGwX+zXv2N93k0yMONvUlANylbJw1eTah8K/Jtpi15KC+WSiaX/nBmbm2HxRM1gZ0nSdjSsrZbGKg=="],
+
+ "@img/sharp-libvips-linux-arm": ["@img/sharp-libvips-linux-arm@1.2.4", "", { "os": "linux", "cpu": "arm" }, "sha512-bFI7xcKFELdiNCVov8e44Ia4u2byA+l3XtsAj+Q8tfCwO6BQ8iDojYdvoPMqsKDkuoOo+X6HZA0s0q11ANMQ8A=="],
+
+ "@img/sharp-libvips-linux-arm64": ["@img/sharp-libvips-linux-arm64@1.2.4", "", { "os": "linux", "cpu": "arm64" }, "sha512-excjX8DfsIcJ10x1Kzr4RcWe1edC9PquDRRPx3YVCvQv+U5p7Yin2s32ftzikXojb1PIFc/9Mt28/y+iRklkrw=="],
+
+ "@img/sharp-libvips-linux-ppc64": ["@img/sharp-libvips-linux-ppc64@1.2.4", "", { "os": "linux", "cpu": "ppc64" }, "sha512-FMuvGijLDYG6lW+b/UvyilUWu5Ayu+3r2d1S8notiGCIyYU/76eig1UfMmkZ7vwgOrzKzlQbFSuQfgm7GYUPpA=="],
+
+ "@img/sharp-libvips-linux-riscv64": ["@img/sharp-libvips-linux-riscv64@1.2.4", "", { "os": "linux", "cpu": "none" }, "sha512-oVDbcR4zUC0ce82teubSm+x6ETixtKZBh/qbREIOcI3cULzDyb18Sr/Wcyx7NRQeQzOiHTNbZFF1UwPS2scyGA=="],
+
+ "@img/sharp-libvips-linux-s390x": ["@img/sharp-libvips-linux-s390x@1.2.4", "", { "os": "linux", "cpu": "s390x" }, "sha512-qmp9VrzgPgMoGZyPvrQHqk02uyjA0/QrTO26Tqk6l4ZV0MPWIW6LTkqOIov+J1yEu7MbFQaDpwdwJKhbJvuRxQ=="],
+
+ "@img/sharp-libvips-linux-x64": ["@img/sharp-libvips-linux-x64@1.2.4", "", { "os": "linux", "cpu": "x64" }, "sha512-tJxiiLsmHc9Ax1bz3oaOYBURTXGIRDODBqhveVHonrHJ9/+k89qbLl0bcJns+e4t4rvaNBxaEZsFtSfAdquPrw=="],
+
+ "@img/sharp-libvips-linuxmusl-arm64": ["@img/sharp-libvips-linuxmusl-arm64@1.2.4", "", { "os": "linux", "cpu": "arm64" }, "sha512-FVQHuwx1IIuNow9QAbYUzJ+En8KcVm9Lk5+uGUQJHaZmMECZmOlix9HnH7n1TRkXMS0pGxIJokIVB9SuqZGGXw=="],
+
+ "@img/sharp-libvips-linuxmusl-x64": ["@img/sharp-libvips-linuxmusl-x64@1.2.4", "", { "os": "linux", "cpu": "x64" }, "sha512-+LpyBk7L44ZIXwz/VYfglaX/okxezESc6UxDSoyo2Ks6Jxc4Y7sGjpgU9s4PMgqgjj1gZCylTieNamqA1MF7Dg=="],
+
+ "@img/sharp-linux-arm": ["@img/sharp-linux-arm@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linux-arm": "1.2.4" }, "os": "linux", "cpu": "arm" }, "sha512-9dLqsvwtg1uuXBGZKsxem9595+ujv0sJ6Vi8wcTANSFpwV/GONat5eCkzQo/1O6zRIkh0m/8+5BjrRr7jDUSZw=="],
+
+ "@img/sharp-linux-arm64": ["@img/sharp-linux-arm64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linux-arm64": "1.2.4" }, "os": "linux", "cpu": "arm64" }, "sha512-bKQzaJRY/bkPOXyKx5EVup7qkaojECG6NLYswgktOZjaXecSAeCWiZwwiFf3/Y+O1HrauiE3FVsGxFg8c24rZg=="],
+
+ "@img/sharp-linux-ppc64": ["@img/sharp-linux-ppc64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linux-ppc64": "1.2.4" }, "os": "linux", "cpu": "ppc64" }, "sha512-7zznwNaqW6YtsfrGGDA6BRkISKAAE1Jo0QdpNYXNMHu2+0dTrPflTLNkpc8l7MUP5M16ZJcUvysVWWrMefZquA=="],
+
+ "@img/sharp-linux-riscv64": ["@img/sharp-linux-riscv64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linux-riscv64": "1.2.4" }, "os": "linux", "cpu": "none" }, "sha512-51gJuLPTKa7piYPaVs8GmByo7/U7/7TZOq+cnXJIHZKavIRHAP77e3N2HEl3dgiqdD/w0yUfiJnII77PuDDFdw=="],
+
+ "@img/sharp-linux-s390x": ["@img/sharp-linux-s390x@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linux-s390x": "1.2.4" }, "os": "linux", "cpu": "s390x" }, "sha512-nQtCk0PdKfho3eC5MrbQoigJ2gd1CgddUMkabUj+rBevs8tZ2cULOx46E7oyX+04WGfABgIwmMC0VqieTiR4jg=="],
+
+ "@img/sharp-linux-x64": ["@img/sharp-linux-x64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linux-x64": "1.2.4" }, "os": "linux", "cpu": "x64" }, "sha512-MEzd8HPKxVxVenwAa+JRPwEC7QFjoPWuS5NZnBt6B3pu7EG2Ge0id1oLHZpPJdn3OQK+BQDiw9zStiHBTJQQQQ=="],
+
+ "@img/sharp-linuxmusl-arm64": ["@img/sharp-linuxmusl-arm64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linuxmusl-arm64": "1.2.4" }, "os": "linux", "cpu": "arm64" }, "sha512-fprJR6GtRsMt6Kyfq44IsChVZeGN97gTD331weR1ex1c1rypDEABN6Tm2xa1wE6lYb5DdEnk03NZPqA7Id21yg=="],
+
+ "@img/sharp-linuxmusl-x64": ["@img/sharp-linuxmusl-x64@0.34.5", "", { "optionalDependencies": { "@img/sharp-libvips-linuxmusl-x64": "1.2.4" }, "os": "linux", "cpu": "x64" }, "sha512-Jg8wNT1MUzIvhBFxViqrEhWDGzqymo3sV7z7ZsaWbZNDLXRJZoRGrjulp60YYtV4wfY8VIKcWidjojlLcWrd8Q=="],
+
+ "@img/sharp-wasm32": ["@img/sharp-wasm32@0.34.5", "", { "dependencies": { "@emnapi/runtime": "^1.7.0" }, "cpu": "none" }, "sha512-OdWTEiVkY2PHwqkbBI8frFxQQFekHaSSkUIJkwzclWZe64O1X4UlUjqqqLaPbUpMOQk6FBu/HtlGXNblIs0huw=="],
+
+ "@img/sharp-win32-arm64": ["@img/sharp-win32-arm64@0.34.5", "", { "os": "win32", "cpu": "arm64" }, "sha512-WQ3AgWCWYSb2yt+IG8mnC6Jdk9Whs7O0gxphblsLvdhSpSTtmu69ZG1Gkb6NuvxsNACwiPV6cNSZNzt0KPsw7g=="],
+
+ "@img/sharp-win32-ia32": ["@img/sharp-win32-ia32@0.34.5", "", { "os": "win32", "cpu": "ia32" }, "sha512-FV9m/7NmeCmSHDD5j4+4pNI8Cp3aW+JvLoXcTUo0IqyjSfAZJ8dIUmijx1qaJsIiU+Hosw6xM5KijAWRJCSgNg=="],
+
+ "@img/sharp-win32-x64": ["@img/sharp-win32-x64@0.34.5", "", { "os": "win32", "cpu": "x64" }, "sha512-+29YMsqY2/9eFEiW93eqWnuLcWcufowXewwSNIT6UwZdUUCrM3oFjMWH/Z6/TMmb4hlFenmfAVbpWeup2jryCw=="],
+
+ "@jridgewell/gen-mapping": ["@jridgewell/gen-mapping@0.3.13", "", { "dependencies": { "@jridgewell/sourcemap-codec": "^1.5.0", "@jridgewell/trace-mapping": "^0.3.24" } }, "sha512-2kkt/7niJ6MgEPxF0bYdQ6etZaA+fQvDcLKckhy1yIQOzaoKjBBjSj63/aLVjYE3qhRt5dvM+uUyfCg6UKCBbA=="],
+
+ "@jridgewell/remapping": ["@jridgewell/remapping@2.3.5", "", { "dependencies": { "@jridgewell/gen-mapping": "^0.3.5", "@jridgewell/trace-mapping": "^0.3.24" } }, "sha512-LI9u/+laYG4Ds1TDKSJW2YPrIlcVYOwi2fUC6xB43lueCjgxV4lffOCZCtYFiH6TNOX+tQKXx97T4IKHbhyHEQ=="],
+
+ "@jridgewell/resolve-uri": ["@jridgewell/resolve-uri@3.1.2", "", {}, "sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw=="],
+
+ "@jridgewell/sourcemap-codec": ["@jridgewell/sourcemap-codec@1.5.5", "", {}, "sha512-cYQ9310grqxueWbl+WuIUIaiUaDcj7WOq5fVhEljNVgRfOUhY9fy2zTvfoqWsnebh8Sl70VScFbICvJnLKB0Og=="],
+
+ "@jridgewell/trace-mapping": ["@jridgewell/trace-mapping@0.3.31", "", { "dependencies": { "@jridgewell/resolve-uri": "^3.1.0", "@jridgewell/sourcemap-codec": "^1.4.14" } }, "sha512-zzNR+SdQSDJzc8joaeP8QQoCQr8NuYx2dIIytl1QeBEZHJ9uW6hebsrYgbz8hJwUQao3TWCMtmfV8Nu1twOLAw=="],
+
+ "@markdoc/markdoc": ["@markdoc/markdoc@0.5.4", "", { "optionalDependencies": { "@types/linkify-it": "^3.0.1", "@types/markdown-it": "12.2.3" }, "peerDependencies": { "@types/react": "*", "react": "*" }, "optionalPeers": ["@types/react", "react"] }, "sha512-36YFNlqFk//gVNGm5xZaTWVwbAVF2AOmVjf1tiUrS6tCoD/YSkVy2E3CkAfhc5MlKcjparL/QFHCopxL4zRyaQ=="],
+
+ "@markdoc/next.js": ["@markdoc/next.js@0.5.0", "", { "dependencies": { "js-yaml": "^4.1.0" }, "peerDependencies": { "@markdoc/markdoc": "*", "next": "*", "react": "*" } }, "sha512-gzWvRc2dlxArQn1mDS4SHed46vkAoKBbXkELihQRYv1eVSA0u9eoNEdJXNuBL4Ajn9j2dPpwZp6nAVjN4nzZlA=="],
+
+ "@next/env": ["@next/env@16.1.4", "", {}, "sha512-gkrXnZyxPUy0Gg6SrPQPccbNVLSP3vmW8LU5dwEttEEC1RwDivk8w4O+sZIjFvPrSICXyhQDCG+y3VmjlJf+9A=="],
+
+ "@next/swc-darwin-arm64": ["@next/swc-darwin-arm64@16.1.4", "", { "os": "darwin", "cpu": "arm64" }, "sha512-T8atLKuvk13XQUdVLCv1ZzMPgLPW0+DWWbHSQXs0/3TjPrKNxTmUIhOEaoEyl3Z82k8h/gEtqyuoZGv6+Ugawg=="],
+
+ "@next/swc-darwin-x64": ["@next/swc-darwin-x64@16.1.4", "", { "os": "darwin", "cpu": "x64" }, "sha512-AKC/qVjUGUQDSPI6gESTx0xOnOPQ5gttogNS3o6bA83yiaSZJek0Am5yXy82F1KcZCx3DdOwdGPZpQCluonuxg=="],
+
+ "@next/swc-linux-arm64-gnu": ["@next/swc-linux-arm64-gnu@16.1.4", "", { "os": "linux", "cpu": "arm64" }, "sha512-POQ65+pnYOkZNdngWfMEt7r53bzWiKkVNbjpmCt1Zb3V6lxJNXSsjwRuTQ8P/kguxDC8LRkqaL3vvsFrce4dMQ=="],
+
+ "@next/swc-linux-arm64-musl": ["@next/swc-linux-arm64-musl@16.1.4", "", { "os": "linux", "cpu": "arm64" }, "sha512-3Wm0zGYVCs6qDFAiSSDL+Z+r46EdtCv/2l+UlIdMbAq9hPJBvGu/rZOeuvCaIUjbArkmXac8HnTyQPJFzFWA0Q=="],
+
+ "@next/swc-linux-x64-gnu": ["@next/swc-linux-x64-gnu@16.1.4", "", { "os": "linux", "cpu": "x64" }, "sha512-lWAYAezFinaJiD5Gv8HDidtsZdT3CDaCeqoPoJjeB57OqzvMajpIhlZFce5sCAH6VuX4mdkxCRqecCJFwfm2nQ=="],
+
+ "@next/swc-linux-x64-musl": ["@next/swc-linux-x64-musl@16.1.4", "", { "os": "linux", "cpu": "x64" }, "sha512-fHaIpT7x4gA6VQbdEpYUXRGyge/YbRrkG6DXM60XiBqDM2g2NcrsQaIuj375egnGFkJow4RHacgBOEsHfGbiUw=="],
+
+ "@next/swc-win32-arm64-msvc": ["@next/swc-win32-arm64-msvc@16.1.4", "", { "os": "win32", "cpu": "arm64" }, "sha512-MCrXxrTSE7jPN1NyXJr39E+aNFBrQZtO154LoCz7n99FuKqJDekgxipoodLNWdQP7/DZ5tKMc/efybx1l159hw=="],
+
+ "@next/swc-win32-x64-msvc": ["@next/swc-win32-x64-msvc@16.1.4", "", { "os": "win32", "cpu": "x64" }, "sha512-JSVlm9MDhmTXw/sO2PE/MRj+G6XOSMZB+BcZ0a7d6KwVFZVpkHcb2okyoYFBaco6LeiL53BBklRlOrDDbOeE5w=="],
+
+ "@swc/helpers": ["@swc/helpers@0.5.15", "", { "dependencies": { "tslib": "^2.8.0" } }, "sha512-JQ5TuMi45Owi4/BIMAJBoSQoOJu12oOk/gADqlcUL9JEdHB8vyjUSsxqeNXnmXHjYKMi2WcYtezGEEhqUI/E2g=="],
+
+ "@tailwindcss/node": ["@tailwindcss/node@4.1.18", "", { "dependencies": { "@jridgewell/remapping": "^2.3.4", "enhanced-resolve": "^5.18.3", "jiti": "^2.6.1", "lightningcss": "1.30.2", "magic-string": "^0.30.21", "source-map-js": "^1.2.1", "tailwindcss": "4.1.18" } }, "sha512-DoR7U1P7iYhw16qJ49fgXUlry1t4CpXeErJHnQ44JgTSKMaZUdf17cfn5mHchfJ4KRBZRFA/Coo+MUF5+gOaCQ=="],
+
+ "@tailwindcss/oxide": ["@tailwindcss/oxide@4.1.18", "", { "optionalDependencies": { "@tailwindcss/oxide-android-arm64": "4.1.18", "@tailwindcss/oxide-darwin-arm64": "4.1.18", "@tailwindcss/oxide-darwin-x64": "4.1.18", "@tailwindcss/oxide-freebsd-x64": "4.1.18", "@tailwindcss/oxide-linux-arm-gnueabihf": "4.1.18", "@tailwindcss/oxide-linux-arm64-gnu": "4.1.18", "@tailwindcss/oxide-linux-arm64-musl": "4.1.18", "@tailwindcss/oxide-linux-x64-gnu": "4.1.18", "@tailwindcss/oxide-linux-x64-musl": "4.1.18", "@tailwindcss/oxide-wasm32-wasi": "4.1.18", "@tailwindcss/oxide-win32-arm64-msvc": "4.1.18", "@tailwindcss/oxide-win32-x64-msvc": "4.1.18" } }, "sha512-EgCR5tTS5bUSKQgzeMClT6iCY3ToqE1y+ZB0AKldj809QXk1Y+3jB0upOYZrn9aGIzPtUsP7sX4QQ4XtjBB95A=="],
+
+ "@tailwindcss/oxide-android-arm64": ["@tailwindcss/oxide-android-arm64@4.1.18", "", { "os": "android", "cpu": "arm64" }, "sha512-dJHz7+Ugr9U/diKJA0W6N/6/cjI+ZTAoxPf9Iz9BFRF2GzEX8IvXxFIi/dZBloVJX/MZGvRuFA9rqwdiIEZQ0Q=="],
+
+ "@tailwindcss/oxide-darwin-arm64": ["@tailwindcss/oxide-darwin-arm64@4.1.18", "", { "os": "darwin", "cpu": "arm64" }, "sha512-Gc2q4Qhs660bhjyBSKgq6BYvwDz4G+BuyJ5H1xfhmDR3D8HnHCmT/BSkvSL0vQLy/nkMLY20PQ2OoYMO15Jd0A=="],
+
+ "@tailwindcss/oxide-darwin-x64": ["@tailwindcss/oxide-darwin-x64@4.1.18", "", { "os": "darwin", "cpu": "x64" }, "sha512-FL5oxr2xQsFrc3X9o1fjHKBYBMD1QZNyc1Xzw/h5Qu4XnEBi3dZn96HcHm41c/euGV+GRiXFfh2hUCyKi/e+yw=="],
+
+ "@tailwindcss/oxide-freebsd-x64": ["@tailwindcss/oxide-freebsd-x64@4.1.18", "", { "os": "freebsd", "cpu": "x64" }, "sha512-Fj+RHgu5bDodmV1dM9yAxlfJwkkWvLiRjbhuO2LEtwtlYlBgiAT4x/j5wQr1tC3SANAgD+0YcmWVrj8R9trVMA=="],
+
+ "@tailwindcss/oxide-linux-arm-gnueabihf": ["@tailwindcss/oxide-linux-arm-gnueabihf@4.1.18", "", { "os": "linux", "cpu": "arm" }, "sha512-Fp+Wzk/Ws4dZn+LV2Nqx3IilnhH51YZoRaYHQsVq3RQvEl+71VGKFpkfHrLM/Li+kt5c0DJe/bHXK1eHgDmdiA=="],
+
+ "@tailwindcss/oxide-linux-arm64-gnu": ["@tailwindcss/oxide-linux-arm64-gnu@4.1.18", "", { "os": "linux", "cpu": "arm64" }, "sha512-S0n3jboLysNbh55Vrt7pk9wgpyTTPD0fdQeh7wQfMqLPM/Hrxi+dVsLsPrycQjGKEQk85Kgbx+6+QnYNiHalnw=="],
+
+ "@tailwindcss/oxide-linux-arm64-musl": ["@tailwindcss/oxide-linux-arm64-musl@4.1.18", "", { "os": "linux", "cpu": "arm64" }, "sha512-1px92582HkPQlaaCkdRcio71p8bc8i/ap5807tPRDK/uw953cauQBT8c5tVGkOwrHMfc2Yh6UuxaH4vtTjGvHg=="],
+
+ "@tailwindcss/oxide-linux-x64-gnu": ["@tailwindcss/oxide-linux-x64-gnu@4.1.18", "", { "os": "linux", "cpu": "x64" }, "sha512-v3gyT0ivkfBLoZGF9LyHmts0Isc8jHZyVcbzio6Wpzifg/+5ZJpDiRiUhDLkcr7f/r38SWNe7ucxmGW3j3Kb/g=="],
+
+ "@tailwindcss/oxide-linux-x64-musl": ["@tailwindcss/oxide-linux-x64-musl@4.1.18", "", { "os": "linux", "cpu": "x64" }, "sha512-bhJ2y2OQNlcRwwgOAGMY0xTFStt4/wyU6pvI6LSuZpRgKQwxTec0/3Scu91O8ir7qCR3AuepQKLU/kX99FouqQ=="],
+
+ "@tailwindcss/oxide-wasm32-wasi": ["@tailwindcss/oxide-wasm32-wasi@4.1.18", "", { "dependencies": { "@emnapi/core": "^1.7.1", "@emnapi/runtime": "^1.7.1", "@emnapi/wasi-threads": "^1.1.0", "@napi-rs/wasm-runtime": "^1.1.0", "@tybys/wasm-util": "^0.10.1", "tslib": "^2.4.0" }, "cpu": "none" }, "sha512-LffYTvPjODiP6PT16oNeUQJzNVyJl1cjIebq/rWWBF+3eDst5JGEFSc5cWxyRCJ0Mxl+KyIkqRxk1XPEs9x8TA=="],
+
+ "@tailwindcss/oxide-win32-arm64-msvc": ["@tailwindcss/oxide-win32-arm64-msvc@4.1.18", "", { "os": "win32", "cpu": "arm64" }, "sha512-HjSA7mr9HmC8fu6bdsZvZ+dhjyGCLdotjVOgLA2vEqxEBZaQo9YTX4kwgEvPCpRh8o4uWc4J/wEoFzhEmjvPbA=="],
+
+ "@tailwindcss/oxide-win32-x64-msvc": ["@tailwindcss/oxide-win32-x64-msvc@4.1.18", "", { "os": "win32", "cpu": "x64" }, "sha512-bJWbyYpUlqamC8dpR7pfjA0I7vdF6t5VpUGMWRkXVE3AXgIZjYUYAK7II1GNaxR8J1SSrSrppRar8G++JekE3Q=="],
+
+ "@tailwindcss/postcss": ["@tailwindcss/postcss@4.1.18", "", { "dependencies": { "@alloc/quick-lru": "^5.2.0", "@tailwindcss/node": "4.1.18", "@tailwindcss/oxide": "4.1.18", "postcss": "^8.4.41", "tailwindcss": "4.1.18" } }, "sha512-Ce0GFnzAOuPyfV5SxjXGn0CubwGcuDB0zcdaPuCSzAa/2vII24JTkH+I6jcbXLb1ctjZMZZI6OjDaLPJQL1S0g=="],
+
+ "@types/linkify-it": ["@types/linkify-it@3.0.5", "", {}, "sha512-yg6E+u0/+Zjva+buc3EIb+29XEg4wltq7cSmd4Uc2EE/1nUVmxyzpX6gUXD0V8jIrG0r7YeOGVIbYRkxeooCtw=="],
+
+ "@types/markdown-it": ["@types/markdown-it@12.2.3", "", { "dependencies": { "@types/linkify-it": "*", "@types/mdurl": "*" } }, "sha512-GKMHFfv3458yYy+v/N8gjufHO6MSZKCOXpZc5GXIWWy8uldwfmPn98vp81gZ5f9SVw8YYBctgfJ22a2d7AOMeQ=="],
+
+ "@types/mdurl": ["@types/mdurl@2.0.0", "", {}, "sha512-RGdgjQUZba5p6QEFAVx2OGb8rQDL/cPRG7GiedRzMcJ1tYnUANBncjbSB1NRGwbvjcPeikRABz2nshyPk1bhWg=="],
+
+ "@types/node": ["@types/node@25.0.10", "", { "dependencies": { "undici-types": "~7.16.0" } }, "sha512-zWW5KPngR/yvakJgGOmZ5vTBemDoSqF3AcV/LrO5u5wTWyEAVVh+IT39G4gtyAkh3CtTZs8aX/yRM82OfzHJRg=="],
+
+ "@types/react": ["@types/react@19.2.9", "", { "dependencies": { "csstype": "^3.2.2" } }, "sha512-Lpo8kgb/igvMIPeNV2rsYKTgaORYdO1XGVZ4Qz3akwOj0ySGYMPlQWa8BaLn0G63D1aSaAQ5ldR06wCpChQCjA=="],
+
+ "@types/react-dom": ["@types/react-dom@19.2.3", "", { "peerDependencies": { "@types/react": "^19.2.0" } }, "sha512-jp2L/eY6fn+KgVVQAOqYItbF0VY/YApe5Mz2F0aykSO8gx31bYCZyvSeYxCHKvzHG5eZjc+zyaS5BrBWya2+kQ=="],
+
+ "@vscode/codicons": ["@vscode/codicons@0.0.44", "", {}, "sha512-F7qPRumUK3EHjNdopfICLGRf3iNPoZQt+McTHAn4AlOWPB3W2kL4H0S7uqEqbyZ6rCxaeDjpAn3MCUnwTu/VJQ=="],
+
+ "argparse": ["argparse@2.0.1", "", {}, "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q=="],
+
+ "autoprefixer": ["autoprefixer@10.4.23", "", { "dependencies": { "browserslist": "^4.28.1", "caniuse-lite": "^1.0.30001760", "fraction.js": "^5.3.4", "picocolors": "^1.1.1", "postcss-value-parser": "^4.2.0" }, "peerDependencies": { "postcss": "^8.1.0" }, "bin": { "autoprefixer": "bin/autoprefixer" } }, "sha512-YYTXSFulfwytnjAPlw8QHncHJmlvFKtczb8InXaAx9Q0LbfDnfEYDE55omerIJKihhmU61Ft+cAOSzQVaBUmeA=="],
+
+ "baseline-browser-mapping": ["baseline-browser-mapping@2.9.17", "", { "bin": { "baseline-browser-mapping": "dist/cli.js" } }, "sha512-agD0MgJFUP/4nvjqzIB29zRPUuCF7Ge6mEv9s8dHrtYD7QWXRcx75rOADE/d5ah1NI+0vkDl0yorDd5U852IQQ=="],
+
+ "browserslist": ["browserslist@4.28.1", "", { "dependencies": { "baseline-browser-mapping": "^2.9.0", "caniuse-lite": "^1.0.30001759", "electron-to-chromium": "^1.5.263", "node-releases": "^2.0.27", "update-browserslist-db": "^1.2.0" }, "bin": { "browserslist": "cli.js" } }, "sha512-ZC5Bd0LgJXgwGqUknZY/vkUQ04r8NXnJZ3yYi4vDmSiZmC/pdSN0NbNRPxZpbtO4uAfDUAFffO8IZoM3Gj8IkA=="],
+
+ "caniuse-lite": ["caniuse-lite@1.0.30001766", "", {}, "sha512-4C0lfJ0/YPjJQHagaE9x2Elb69CIqEPZeG0anQt9SIvIoOH4a4uaRl73IavyO+0qZh6MDLH//DrXThEYKHkmYA=="],
+
+ "client-only": ["client-only@0.0.1", "", {}, "sha512-IV3Ou0jSMzZrd3pZ48nLkT9DA7Ag1pnPzaiQhpW7c3RbcqqzvzzVu+L8gfqMp/8IM2MQtSiqaCxrrcfu8I8rMA=="],
+
+ "csstype": ["csstype@3.2.3", "", {}, "sha512-z1HGKcYy2xA8AGQfwrn0PAy+PB7X/GSj3UVJW9qKyn43xWa+gl5nXmU4qqLMRzWVLFC8KusUX8T/0kCiOYpAIQ=="],
+
+ "detect-libc": ["detect-libc@2.1.2", "", {}, "sha512-Btj2BOOO83o3WyH59e8MgXsxEQVcarkUOpEYrubB0urwnN10yQ364rsiByU11nZlqWYZm05i/of7io4mzihBtQ=="],
+
+ "electron-to-chromium": ["electron-to-chromium@1.5.278", "", {}, "sha512-dQ0tM1svDRQOwxnXxm+twlGTjr9Upvt8UFWAgmLsxEzFQxhbti4VwxmMjsDxVC51Zo84swW7FVCXEV+VAkhuPw=="],
+
+ "enhanced-resolve": ["enhanced-resolve@5.18.4", "", { "dependencies": { "graceful-fs": "^4.2.4", "tapable": "^2.2.0" } }, "sha512-LgQMM4WXU3QI+SYgEc2liRgznaD5ojbmY3sb8LxyguVkIg5FxdpTkvk72te2R38/TGKxH634oLxXRGY6d7AP+Q=="],
+
+ "escalade": ["escalade@3.2.0", "", {}, "sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA=="],
+
+ "fraction.js": ["fraction.js@5.3.4", "", {}, "sha512-1X1NTtiJphryn/uLQz3whtY6jK3fTqoE3ohKs0tT+Ujr1W59oopxmoEh7Lu5p6vBaPbgoM0bzveAW4Qi5RyWDQ=="],
+
+ "graceful-fs": ["graceful-fs@4.2.11", "", {}, "sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ=="],
+
+ "jiti": ["jiti@2.6.1", "", { "bin": { "jiti": "lib/jiti-cli.mjs" } }, "sha512-ekilCSN1jwRvIbgeg/57YFh8qQDNbwDb9xT/qu2DAHbFFZUicIl4ygVaAvzveMhMVr3LnpSKTNnwt8PoOfmKhQ=="],
+
+ "js-yaml": ["js-yaml@4.1.1", "", { "dependencies": { "argparse": "^2.0.1" }, "bin": { "js-yaml": "bin/js-yaml.js" } }, "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA=="],
+
+ "lightningcss": ["lightningcss@1.30.2", "", { "dependencies": { "detect-libc": "^2.0.3" }, "optionalDependencies": { "lightningcss-android-arm64": "1.30.2", "lightningcss-darwin-arm64": "1.30.2", "lightningcss-darwin-x64": "1.30.2", "lightningcss-freebsd-x64": "1.30.2", "lightningcss-linux-arm-gnueabihf": "1.30.2", "lightningcss-linux-arm64-gnu": "1.30.2", "lightningcss-linux-arm64-musl": "1.30.2", "lightningcss-linux-x64-gnu": "1.30.2", "lightningcss-linux-x64-musl": "1.30.2", "lightningcss-win32-arm64-msvc": "1.30.2", "lightningcss-win32-x64-msvc": "1.30.2" } }, "sha512-utfs7Pr5uJyyvDETitgsaqSyjCb2qNRAtuqUeWIAKztsOYdcACf2KtARYXg2pSvhkt+9NfoaNY7fxjl6nuMjIQ=="],
+
+ "lightningcss-android-arm64": ["lightningcss-android-arm64@1.30.2", "", { "os": "android", "cpu": "arm64" }, "sha512-BH9sEdOCahSgmkVhBLeU7Hc9DWeZ1Eb6wNS6Da8igvUwAe0sqROHddIlvU06q3WyXVEOYDZ6ykBZQnjTbmo4+A=="],
+
+ "lightningcss-darwin-arm64": ["lightningcss-darwin-arm64@1.30.2", "", { "os": "darwin", "cpu": "arm64" }, "sha512-ylTcDJBN3Hp21TdhRT5zBOIi73P6/W0qwvlFEk22fkdXchtNTOU4Qc37SkzV+EKYxLouZ6M4LG9NfZ1qkhhBWA=="],
+
+ "lightningcss-darwin-x64": ["lightningcss-darwin-x64@1.30.2", "", { "os": "darwin", "cpu": "x64" }, "sha512-oBZgKchomuDYxr7ilwLcyms6BCyLn0z8J0+ZZmfpjwg9fRVZIR5/GMXd7r9RH94iDhld3UmSjBM6nXWM2TfZTQ=="],
+
+ "lightningcss-freebsd-x64": ["lightningcss-freebsd-x64@1.30.2", "", { "os": "freebsd", "cpu": "x64" }, "sha512-c2bH6xTrf4BDpK8MoGG4Bd6zAMZDAXS569UxCAGcA7IKbHNMlhGQ89eRmvpIUGfKWNVdbhSbkQaWhEoMGmGslA=="],
+
+ "lightningcss-linux-arm-gnueabihf": ["lightningcss-linux-arm-gnueabihf@1.30.2", "", { "os": "linux", "cpu": "arm" }, "sha512-eVdpxh4wYcm0PofJIZVuYuLiqBIakQ9uFZmipf6LF/HRj5Bgm0eb3qL/mr1smyXIS1twwOxNWndd8z0E374hiA=="],
+
+ "lightningcss-linux-arm64-gnu": ["lightningcss-linux-arm64-gnu@1.30.2", "", { "os": "linux", "cpu": "arm64" }, "sha512-UK65WJAbwIJbiBFXpxrbTNArtfuznvxAJw4Q2ZGlU8kPeDIWEX1dg3rn2veBVUylA2Ezg89ktszWbaQnxD/e3A=="],
+
+ "lightningcss-linux-arm64-musl": ["lightningcss-linux-arm64-musl@1.30.2", "", { "os": "linux", "cpu": "arm64" }, "sha512-5Vh9dGeblpTxWHpOx8iauV02popZDsCYMPIgiuw97OJ5uaDsL86cnqSFs5LZkG3ghHoX5isLgWzMs+eD1YzrnA=="],
+
+ "lightningcss-linux-x64-gnu": ["lightningcss-linux-x64-gnu@1.30.2", "", { "os": "linux", "cpu": "x64" }, "sha512-Cfd46gdmj1vQ+lR6VRTTadNHu6ALuw2pKR9lYq4FnhvgBc4zWY1EtZcAc6EffShbb1MFrIPfLDXD6Xprbnni4w=="],
+
+ "lightningcss-linux-x64-musl": ["lightningcss-linux-x64-musl@1.30.2", "", { "os": "linux", "cpu": "x64" }, "sha512-XJaLUUFXb6/QG2lGIW6aIk6jKdtjtcffUT0NKvIqhSBY3hh9Ch+1LCeH80dR9q9LBjG3ewbDjnumefsLsP6aiA=="],
+
+ "lightningcss-win32-arm64-msvc": ["lightningcss-win32-arm64-msvc@1.30.2", "", { "os": "win32", "cpu": "arm64" }, "sha512-FZn+vaj7zLv//D/192WFFVA0RgHawIcHqLX9xuWiQt7P0PtdFEVaxgF9rjM/IRYHQXNnk61/H/gb2Ei+kUQ4xQ=="],
+
+ "lightningcss-win32-x64-msvc": ["lightningcss-win32-x64-msvc@1.30.2", "", { "os": "win32", "cpu": "x64" }, "sha512-5g1yc73p+iAkid5phb4oVFMB45417DkRevRbt/El/gKXJk4jid+vPFF/AXbxn05Aky8PapwzZrdJShv5C0avjw=="],
+
+ "magic-string": ["magic-string@0.30.21", "", { "dependencies": { "@jridgewell/sourcemap-codec": "^1.5.5" } }, "sha512-vd2F4YUyEXKGcLHoq+TEyCjxueSeHnFxyyjNp80yg0XV4vUhnDer/lvvlqM/arB5bXQN5K2/3oinyCRyx8T2CQ=="],
+
+ "nanoid": ["nanoid@3.3.11", "", { "bin": { "nanoid": "bin/nanoid.cjs" } }, "sha512-N8SpfPUnUp1bK+PMYW8qSWdl9U+wwNWI4QKxOYDy9JAro3WMX7p2OeVRF9v+347pnakNevPmiHhNmZ2HbFA76w=="],
+
+ "next": ["next@16.1.4", "", { "dependencies": { "@next/env": "16.1.4", "@swc/helpers": "0.5.15", "baseline-browser-mapping": "^2.8.3", "caniuse-lite": "^1.0.30001579", "postcss": "8.4.31", "styled-jsx": "5.1.6" }, "optionalDependencies": { "@next/swc-darwin-arm64": "16.1.4", "@next/swc-darwin-x64": "16.1.4", "@next/swc-linux-arm64-gnu": "16.1.4", "@next/swc-linux-arm64-musl": "16.1.4", "@next/swc-linux-x64-gnu": "16.1.4", "@next/swc-linux-x64-musl": "16.1.4", "@next/swc-win32-arm64-msvc": "16.1.4", "@next/swc-win32-x64-msvc": "16.1.4", "sharp": "^0.34.4" }, "peerDependencies": { "@opentelemetry/api": "^1.1.0", "@playwright/test": "^1.51.1", "babel-plugin-react-compiler": "*", "react": "^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0", "react-dom": "^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0", "sass": "^1.3.0" }, "optionalPeers": ["@opentelemetry/api", "@playwright/test", "babel-plugin-react-compiler", "sass"], "bin": { "next": "dist/bin/next" } }, "sha512-gKSecROqisnV7Buen5BfjmXAm7Xlpx9o2ueVQRo5DxQcjC8d330dOM1xiGWc2k3Dcnz0In3VybyRPOsudwgiqQ=="],
+
+ "node-releases": ["node-releases@2.0.27", "", {}, "sha512-nmh3lCkYZ3grZvqcCH+fjmQ7X+H0OeZgP40OierEaAptX4XofMh5kwNbWh7lBduUzCcV/8kZ+NDLCwm2iorIlA=="],
+
+ "picocolors": ["picocolors@1.1.1", "", {}, "sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA=="],
+
+ "postcss": ["postcss@8.5.6", "", { "dependencies": { "nanoid": "^3.3.11", "picocolors": "^1.1.1", "source-map-js": "^1.2.1" } }, "sha512-3Ybi1tAuwAP9s0r1UQ2J4n5Y0G05bJkpUIO0/bI9MhwmD70S5aTWbXGBwxHrelT+XM1k6dM0pk+SwNkpTRN7Pg=="],
+
+ "postcss-value-parser": ["postcss-value-parser@4.2.0", "", {}, "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ=="],
+
+ "prismjs": ["prismjs@1.30.0", "", {}, "sha512-DEvV2ZF2r2/63V+tK8hQvrR2ZGn10srHbXviTlcv7Kpzw8jWiNTqbVgjO3IY8RxrrOUF8VPMQQFysYYYv0YZxw=="],
+
+ "react": ["react@19.2.3", "", {}, "sha512-Ku/hhYbVjOQnXDZFv2+RibmLFGwFdeeKHFcOTlrt7xplBnya5OGn/hIRDsqDiSUcfORsDC7MPxwork8jBwsIWA=="],
+
+ "react-dom": ["react-dom@19.2.3", "", { "dependencies": { "scheduler": "^0.27.0" }, "peerDependencies": { "react": "^19.2.3" } }, "sha512-yELu4WmLPw5Mr/lmeEpox5rw3RETacE++JgHqQzd2dg+YbJuat3jH4ingc+WPZhxaoFzdv9y33G+F7Nl5O0GBg=="],
+
+ "scheduler": ["scheduler@0.27.0", "", {}, "sha512-eNv+WrVbKu1f3vbYJT/xtiF5syA5HPIMtf9IgY/nKg0sWqzAUEvqY/xm7OcZc/qafLx/iO9FgOmeSAp4v5ti/Q=="],
+
+ "semver": ["semver@7.7.3", "", { "bin": { "semver": "bin/semver.js" } }, "sha512-SdsKMrI9TdgjdweUSR9MweHA4EJ8YxHn8DFaDisvhVlUOe4BF1tLD7GAj0lIqWVl+dPb/rExr0Btby5loQm20Q=="],
+
+ "sharp": ["sharp@0.34.5", "", { "dependencies": { "@img/colour": "^1.0.0", "detect-libc": "^2.1.2", "semver": "^7.7.3" }, "optionalDependencies": { "@img/sharp-darwin-arm64": "0.34.5", "@img/sharp-darwin-x64": "0.34.5", "@img/sharp-libvips-darwin-arm64": "1.2.4", "@img/sharp-libvips-darwin-x64": "1.2.4", "@img/sharp-libvips-linux-arm": "1.2.4", "@img/sharp-libvips-linux-arm64": "1.2.4", "@img/sharp-libvips-linux-ppc64": "1.2.4", "@img/sharp-libvips-linux-riscv64": "1.2.4", "@img/sharp-libvips-linux-s390x": "1.2.4", "@img/sharp-libvips-linux-x64": "1.2.4", "@img/sharp-libvips-linuxmusl-arm64": "1.2.4", "@img/sharp-libvips-linuxmusl-x64": "1.2.4", "@img/sharp-linux-arm": "0.34.5", "@img/sharp-linux-arm64": "0.34.5", "@img/sharp-linux-ppc64": "0.34.5", "@img/sharp-linux-riscv64": "0.34.5", "@img/sharp-linux-s390x": "0.34.5", "@img/sharp-linux-x64": "0.34.5", "@img/sharp-linuxmusl-arm64": "0.34.5", "@img/sharp-linuxmusl-x64": "0.34.5", "@img/sharp-wasm32": "0.34.5", "@img/sharp-win32-arm64": "0.34.5", "@img/sharp-win32-ia32": "0.34.5", "@img/sharp-win32-x64": "0.34.5" } }, "sha512-Ou9I5Ft9WNcCbXrU9cMgPBcCK8LiwLqcbywW3t4oDV37n1pzpuNLsYiAV8eODnjbtQlSDwZ2cUEeQz4E54Hltg=="],
+
+ "source-map-js": ["source-map-js@1.2.1", "", {}, "sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA=="],
+
+ "styled-jsx": ["styled-jsx@5.1.6", "", { "dependencies": { "client-only": "0.0.1" }, "peerDependencies": { "react": ">= 16.8.0 || 17.x.x || ^18.0.0-0 || ^19.0.0-0" } }, "sha512-qSVyDTeMotdvQYoHWLNGwRFJHC+i+ZvdBRYosOFgC+Wg1vx4frN2/RG/NA7SYqqvKNLf39P2LSRA2pu6n0XYZA=="],
+
+ "tailwindcss": ["tailwindcss@4.1.18", "", {}, "sha512-4+Z+0yiYyEtUVCScyfHCxOYP06L5Ne+JiHhY2IjR2KWMIWhJOYZKLSGZaP5HkZ8+bY0cxfzwDE5uOmzFXyIwxw=="],
+
+ "tapable": ["tapable@2.3.0", "", {}, "sha512-g9ljZiwki/LfxmQADO3dEY1CbpmXT5Hm2fJ+QaGKwSXUylMybePR7/67YW7jOrrvjEgL1Fmz5kzyAjWVWLlucg=="],
+
+ "tslib": ["tslib@2.8.1", "", {}, "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w=="],
+
+ "typescript": ["typescript@5.9.3", "", { "bin": { "tsc": "bin/tsc", "tsserver": "bin/tsserver" } }, "sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw=="],
+
+ "undici-types": ["undici-types@7.16.0", "", {}, "sha512-Zz+aZWSj8LE6zoxD+xrjh4VfkIG8Ya6LvYkZqtUQGJPZjYl53ypCaUwWqo7eI0x66KBGeRo+mlBEkMSeSZ38Nw=="],
+
+ "update-browserslist-db": ["update-browserslist-db@1.2.3", "", { "dependencies": { "escalade": "^3.2.0", "picocolors": "^1.1.1" }, "peerDependencies": { "browserslist": ">= 4.21.0" }, "bin": { "update-browserslist-db": "cli.js" } }, "sha512-Js0m9cx+qOgDxo0eMiFGEueWztz+d4+M3rGlmKPT+T4IS/jP4ylw3Nwpu6cpTTP8R1MAC1kF4VbdLt3ARf209w=="],
+
+ "@tailwindcss/oxide-wasm32-wasi/@emnapi/core": ["@emnapi/core@1.8.1", "", { "dependencies": { "@emnapi/wasi-threads": "1.1.0", "tslib": "^2.4.0" }, "bundled": true }, "sha512-AvT9QFpxK0Zd8J0jopedNm+w/2fIzvtPKPjqyw9jwvBaReTTqPBk9Hixaz7KbjimP+QNz605/XnjFcDAL2pqBg=="],
+
+ "@tailwindcss/oxide-wasm32-wasi/@emnapi/runtime": ["@emnapi/runtime@1.8.1", "", { "dependencies": { "tslib": "^2.4.0" }, "bundled": true }, "sha512-mehfKSMWjjNol8659Z8KxEMrdSJDDot5SXMq00dM8BN4o+CLNXQ0xH2V7EchNHV4RmbZLmmPdEaXZc5H2FXmDg=="],
+
+ "@tailwindcss/oxide-wasm32-wasi/@emnapi/wasi-threads": ["@emnapi/wasi-threads@1.1.0", "", { "dependencies": { "tslib": "^2.4.0" }, "bundled": true }, "sha512-WI0DdZ8xFSbgMjR1sFsKABJ/C5OnRrjT06JXbZKexJGrDuPTzZdDYfFlsgcCXCyf+suG5QU2e/y1Wo2V/OapLQ=="],
+
+ "@tailwindcss/oxide-wasm32-wasi/@napi-rs/wasm-runtime": ["@napi-rs/wasm-runtime@1.1.1", "", { "dependencies": { "@emnapi/core": "^1.7.1", "@emnapi/runtime": "^1.7.1", "@tybys/wasm-util": "^0.10.1" }, "bundled": true }, "sha512-p64ah1M1ld8xjWv3qbvFwHiFVWrq1yFvV4f7w+mzaqiR4IlSgkqhcRdHwsGgomwzBH51sRY4NEowLxnaBjcW/A=="],
+
+ "@tailwindcss/oxide-wasm32-wasi/@tybys/wasm-util": ["@tybys/wasm-util@0.10.1", "", { "dependencies": { "tslib": "^2.4.0" }, "bundled": true }, "sha512-9tTaPJLSiejZKx+Bmog4uSubteqTvFrVrURwkmHixBo0G4seD0zUxp98E1DzUBJxLQ3NPwXrGKDiVjwx/DpPsg=="],
+
+ "@tailwindcss/oxide-wasm32-wasi/tslib": ["tslib@2.8.1", "", { "bundled": true }, "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w=="],
+
+ "next/postcss": ["postcss@8.4.31", "", { "dependencies": { "nanoid": "^3.3.6", "picocolors": "^1.0.0", "source-map-js": "^1.0.2" } }, "sha512-PS08Iboia9mts/2ygV3eLpY5ghnUcfLV/EXTOW1E2qYxJKGGBUtNjN76FYHnMs36RmARn41bC0AZmn+rR0OVpQ=="],
+ }
+}
diff --git a/packages/kilo-docs/components/Callout.tsx b/packages/kilo-docs/components/Callout.tsx
new file mode 100644
index 00000000000..df902cb6893
--- /dev/null
+++ b/packages/kilo-docs/components/Callout.tsx
@@ -0,0 +1,115 @@
+import * as React from "react"
+
+type CalloutType = "generic" | "note" | "tip" | "info" | "warning" | "danger"
+
+interface CalloutProps {
+ type?: CalloutType
+ title?: string
+ collapsed?: boolean
+ children: React.ReactNode
+}
+
+const typeConfig: Record<
+ CalloutType,
+ {
+ icon: string | null
+ defaultTitle: string | null
+ borderColor: string
+ bgColor: string
+ titleColor: string
+ iconColor: string
+ }
+> = {
+ generic: {
+ icon: null,
+ defaultTitle: null,
+ borderColor: "border-l-gray-300 dark:border-l-gray-600",
+ bgColor: "bg-gray-50 dark:bg-gray-800/50",
+ titleColor: "text-gray-700 dark:text-gray-300",
+ iconColor: "text-gray-400",
+ },
+ note: {
+ icon: "📝",
+ defaultTitle: "Note",
+ borderColor: "border-l-gray-500",
+ bgColor: "bg-gray-50 dark:bg-gray-800/50",
+ titleColor: "text-gray-700 dark:text-gray-300",
+ iconColor: "text-gray-500",
+ },
+ tip: {
+ icon: "💡",
+ defaultTitle: "Tip",
+ borderColor: "border-l-green-500",
+ bgColor: "bg-green-50 dark:bg-green-900/20",
+ titleColor: "text-green-700 dark:text-green-400",
+ iconColor: "text-green-500",
+ },
+ info: {
+ icon: "ℹ️",
+ defaultTitle: "Info",
+ borderColor: "border-l-blue-500",
+ bgColor: "bg-blue-50 dark:bg-blue-900/20",
+ titleColor: "text-blue-700 dark:text-blue-400",
+ iconColor: "text-blue-500",
+ },
+ warning: {
+ icon: "⚠️",
+ defaultTitle: "Warning",
+ borderColor: "border-l-yellow-500",
+ bgColor: "bg-yellow-50 dark:bg-yellow-900/20",
+ titleColor: "text-yellow-700 dark:text-yellow-400",
+ iconColor: "text-yellow-500",
+ },
+ danger: {
+ icon: "🚨",
+ defaultTitle: "Danger",
+ borderColor: "border-l-red-500",
+ bgColor: "bg-red-50 dark:bg-red-900/20",
+ titleColor: "text-red-700 dark:text-red-400",
+ iconColor: "text-red-500",
+ },
+}
+
+export function Callout({ type = "note", title, collapsed = false, children }: CalloutProps) {
+ const [isExpanded, setIsExpanded] = React.useState(!collapsed)
+ const config = typeConfig[type]
+ const displayTitle = title ?? config.defaultTitle
+ const showHeader = displayTitle || config.icon
+
+ // If collapsed prop is set, make the header clickable
+ if (collapsed) {
+ return (
+
+ {mainNavItems.map((item) => {
+ const isActive = item.sectionKey ? router.pathname.startsWith(item.href) : router.pathname === item.href
+ const hasSubItems = item.sectionKey && sectionNavItems[item.sectionKey]
+
+ if (hasSubItems) {
+ return (
+
+ )
+ }
+
+ return (
+
+ {item.label}
+
+ )
+ })}
+
+
+
+ )
+
+ // Section navigation panel
+ const sectionNavPanel = (
+
+
+
+
+ )
+
+ const navContent = (
+
+ {sectionItems.map((group) => (
+
+
+
+
+ {group.title}
+
+ ))}
+ -
+ {group.links.map((link) => {
+ const active = router.pathname === link.href
+ return (
+
- + + {link.children} + + + ) + })} +
+ {mainNavPanel}
+ {sectionNavPanel}
+
+
+
+ )
+
+ return (
+ <>
+ {/* Desktop sidebar */}
+
+
+ {/* Mobile overlay */}
+
+
+ {/* Mobile sidebar drawer */}
+
+
+
+
+ {/* Global styles for elements that styled-jsx can't reach */}
+
+
+ )
+}
diff --git a/packages/kilo-docs/components/Table.tsx b/packages/kilo-docs/components/Table.tsx
new file mode 100644
index 00000000000..27725720f34
--- /dev/null
+++ b/packages/kilo-docs/components/Table.tsx
@@ -0,0 +1,66 @@
+import React from "react"
+
+interface TableProps {
+ children: React.ReactNode
+}
+
+export function Table({ children }: TableProps) {
+ return (
+
+ {children}
+
+ )
+}
+
+interface THeadProps {
+ children: React.ReactNode
+}
+
+export function THead({ children }: THeadProps) {
+ return {children}
+}
+
+interface TBodyProps {
+ children: React.ReactNode
+}
+
+export function TBody({ children }: TBodyProps) {
+ return {children}
+}
+
+interface TrProps {
+ children: React.ReactNode
+}
+
+export function Tr({ children }: TrProps) {
+ return
+
+ )
+}
diff --git a/packages/kilo-docs/components/ThemeToggle.tsx b/packages/kilo-docs/components/ThemeToggle.tsx
new file mode 100644
index 00000000000..789f0529490
--- /dev/null
+++ b/packages/kilo-docs/components/ThemeToggle.tsx
@@ -0,0 +1,117 @@
+import React, { useEffect, useState } from "react"
+
+type Theme = "light" | "dark" | "system"
+
+export function ThemeToggle() {
+ const [theme, setTheme] = useState
+ {tabs.map((tab, index) => (
+
+ ))}
+
+ {tabs[activeIndex]}
+
+
+
+
+
+ )
+}
+
+function DropdownMenu({ label, items, isOpen, onToggle, onClose }: DropdownMenuProps) {
+ const dropdownRef = useRef
+
+ {isOpen && (
+
+ )
+}
+
+function NavTab({ item, isActive }: { item: NavItem; isActive: boolean }) {
+ return (
+
+ {item.label}
+ {isActive && }
+
+ )
+}
+
+interface TopNavProps {
+ onMobileMenuToggle?: () => void
+ isMobileMenuOpen?: boolean
+ showMobileMenuButton?: boolean
+}
+
+export function TopNav({ onMobileMenuToggle, isMobileMenuOpen = false, showMobileMenuButton = true }: TopNavProps) {
+ const router = useRouter()
+ const [openDropdown, setOpenDropdown] = useState
+
+ )}
+
+ {items.map((item) => (
+
+
+ {item.label}
+
+ {item.description && (
+
+ {item.description}
+
+ )}
+
+ ))}
+
+
+ {/* Mobile menu button */}
+ {showMobileMenuButton && (
+
+ )}
+
+
+
+
+
+ {/* Secondary nav bar (desktop only) */}
+
+ Kilo Code
+ DOCS
+
+
+
+ {/* Center - Search and Ask AI (desktop only) */}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ handleDropdownToggle("contributing")}
+ onClose={handleDropdownClose}
+ />
+ handleDropdownToggle("help")}
+ onClose={handleDropdownClose}
+ />
+
+
+ Invalid YouTube URL: {url}
+
+ )
+ }
+
+ return (
+
+
+ {caption}
+
+ )}
+
+ )
+}
diff --git a/packages/kilo-docs/components/index.js b/packages/kilo-docs/components/index.js
new file mode 100644
index 00000000000..eaf57b23785
--- /dev/null
+++ b/packages/kilo-docs/components/index.js
@@ -0,0 +1,15 @@
+export * from "./Callout"
+export * from "./CodeBlock"
+export * from "./Codicon"
+export * from "./CopyPageButton"
+export * from "./Heading"
+export * from "./Icon"
+export * from "./Image"
+export * from "./KiloCodeIcon"
+export * from "./SideNav"
+export * from "./Table"
+export * from "./TableOfContents"
+export * from "./Tabs"
+export * from "./ThemeToggle"
+export * from "./TopNav"
+export * from "./YouTube"
diff --git a/packages/kilo-docs/docs/advanced-usage/auto-cleanup.md b/packages/kilo-docs/docs/advanced-usage/auto-cleanup.md
deleted file mode 100644
index c9fb9b89a6e..00000000000
--- a/packages/kilo-docs/docs/advanced-usage/auto-cleanup.md
+++ /dev/null
@@ -1,275 +0,0 @@
-# Auto Cleanup
-
-Auto Cleanup automatically manages your task history by removing old tasks to free up disk space and improve performance. Tasks are intelligently classified and retained based on their type and age, ensuring important work is preserved while temporary or experimental tasks are cleaned up.
-
-:::warning Important
-Task deletion is permanent and cannot be undone. Deleted tasks are completely removed from disk, including all conversation history, checkpoints, and associated files.
-:::
-
-## Overview
-
-As you work with Kilo Code, each task creates files containing conversation history, checkpoints, and other data. Over time, this accumulates and can consume significant disk space. Auto-Cleanup solves this by:
-
-- **Automatically removing old tasks** based on configurable retention periods
-- **Preserving important tasks** by classifying them into different types
-- **Protecting favorited tasks** from deletion
-- **Managing disk usage** without manual intervention
-
-:::info Key Benefits
-
-- **Free up disk space**: Automatically remove old task data
-- **Improve performance**: Reduce the size of task history
-- **Flexible control**: Configure different retention periods for different task types
-- **Safety first**: Favorited tasks can be protected from deletion
-- **Manual override**: Run cleanup manually whenever needed
- :::
-
-## How Auto-Cleanup Works
-
-Auto-Cleanup uses an intelligent classification system to determine how long each task should be retained:
-
-### Task Classification
-
-Every task is automatically classified into one of these categories:
-
-| Task Type | Description | Default Retention |
-| -------------- | ----------------------------------------- | ---------------------------------------- |
-| **Favorited** | Tasks you've marked as favorites | Never deleted (or 90 days if configured) |
-| **Completed** | Tasks that successfully finished | 30 days |
-| **Incomplete** | Tasks that were started but not completed | 7 days |
-| **Regular** | Default classification for other tasks | 30 days |
-
-#### Understanding Task Completion
-
-A task is considered "completed" when Kilo Code uses the [`attempt_completion`](../features/tools/attempt-completion) tool to formally mark it as finished. Tasks without this completion marker are classified as incomplete, even if you consider them done. This distinction helps clean up abandoned or experimental tasks more aggressively.
-
-### Cleanup Process
-
-When Auto-Cleanup runs, it:
-
-1. **Scans all tasks** in your task history
-2. **Classifies each task** based on its properties and completion status
-3. **Checks retention periods** to determine eligibility for deletion
-4. **Protects active tasks** currently in use
-5. **Deletes eligible tasks** and their associated files
-6. **Reports results** including disk space freed
-
-## Configuration
-
-Access Auto-Cleanup settings through the Kilo Code settings panel:
-
-1. Click the gear icon () in Kilo Code
-2. Navigate to the **Auto-Cleanup** section (under Checkpoints)
-
-### Enable Auto-Cleanup
-
-
+
+
+ {caption && (
+ 
-
-Check the **"Enable automatic task cleanup"** option to activate the feature. When enabled, tasks will be automatically removed based on your retention settings.
-
-### Retention Period Settings
-
-Configure how long different types of tasks are kept before cleanup:
-
-#### Default Retention Period
-
-```
-Default: 30 days
-Minimum: 1 day
-```
-
-Sets the base retention period for regular tasks that don't fall into other categories.
-
-#### Favorited Tasks
-
-**Never delete favorited tasks** (recommended)
-
-When enabled, favorited tasks are preserved indefinitely regardless of age. This is the safest option to prevent accidental deletion of important work.
-
-If disabled, you can set a custom retention period:
-
-```
-Default: 90 days
-Minimum: 1 day
-```
-
-To favorite a task, use the star icon in the task history panel.
-
-#### Completed Tasks
-
-```
-Default: 30 days
-Minimum: 1 day
-```
-
-Tasks successfully completed via the [`attempt_completion`](../features/tools/attempt-completion) tool are retained for this period. These tasks typically represent finished work that may still be useful for reference.
-
-#### Incomplete Tasks
-
-```
-Default: 7 days
-Minimum: 1 day
-```
-
-Tasks without completion status are retained for a shorter period. This helps clean up experimental or abandoned tasks more quickly while still giving you time to review them.
-
-### Last Cleanup Display
-
-The settings show when the last cleanup operation ran, helping you understand the cleanup schedule.
-
-### Manual Cleanup
-
-Click the **"Run Cleanup Now"** button to immediately trigger a cleanup operation using your current settings. This is useful when:
-
-- You need to free up disk space urgently
-- You've changed retention settings and want them applied immediately
-- You want to preview what would be cleaned up (check the output)
-
-## Best Practices
-
-### Recommended Retention Periods
-
-**For Individual Developers:**
-
-- Default retention: 30 days
-- Completed tasks: 30 days
-- Incomplete tasks: 7 days
-- Favorited tasks: Never delete
-
-**For Experimentation:**
-
-- Default retention: 14 days
-- Completed tasks: 14 days
-- Incomplete tasks: 3 days
-- Favorited tasks: Never delete
-
-**For Limited Disk Space:**
-
-- Default retention: 14 days
-- Completed tasks: 14 days
-- Incomplete tasks: 3 days
-- Favorited tasks: 60 days
-
-### Protecting Important Work
-
-To ensure important tasks are never deleted:
-
-1. **Mark tasks as favorites** using the star icon in task history
-2. **Enable "Never delete favorited tasks"** in settings
-3. **Review cleanup results** periodically to ensure retention periods are appropriate
-
-### Balancing Disk Space and History
-
-Consider these factors when setting retention periods:
-
-- **Available disk space**: Shorter retention if space is limited
-- **Task frequency**: More tasks = shorter retention needed
-- **Reference needs**: Keep completed tasks longer if you often refer back
-- **Experimentation**: Shorter incomplete task retention for heavy experimentation
-
-## Troubleshooting
-
-### Tasks Not Being Cleaned Up
-
-**Issue**: Old tasks remain after cleanup runs
-
-**Solutions**:
-
-1. Verify Auto-Cleanup is enabled in settings
-2. Check retention periods - they may be too long
-3. Verify tasks are older than the retention period
-4. Check if tasks are favorited (they won't be deleted if "Never delete" is enabled)
-
-### Important Task Was Deleted
-
-**Issue**: A task you needed was removed
-
-**Prevention**:
-
-1. Always favorite important tasks before they age out
-2. Set longer retention periods for task types you reference frequently
-3. Consider enabling "Never delete favorited tasks"
-4. Export or backup critical task data before it ages out
-
-:::warning
-Deleted tasks cannot be recovered. Always favorite important tasks or adjust retention periods to prevent accidental deletion.
-:::
-
-### Cleanup Using Too Much Disk I/O
-
-**Issue**: Cleanup operation impacts system performance
-
-**Solutions**:
-
-1. Check the "Operation duration" in cleanup results
-2. If slow, consider reducing retention periods to clean fewer tasks at once
-3. Run manual cleanup during non-working hours
-4. Ensure adequate system resources during cleanup
-
-### Active Task Protection
-
-Auto-Cleanup automatically protects your currently active task from deletion, even if it meets the age criteria. This ensures you never lose work in progress during a cleanup operation.
-
-## Technical Details
-
-### What Gets Deleted
-
-When a task is deleted, the following are permanently removed:
-
-- Task directory and all contents
-- Conversation history and messages
-- Checkpoints (if enabled)
-- API request logs
-- Task metadata
-- Associated temporary files
-
-### Storage Location
-
-Task data is stored in your VS Code global storage location:
-
-- **macOS**: `~/Library/Application Support/Code/User/globalStorage/kilocode.kilo-code/`
-- **Windows**: `%APPDATA%\Code\User\globalStorage\kilocode.kilo-code\`
-- **Linux**: `~/.config/Code/User/globalStorage/kilocode.kilo-code/`
-
-## Privacy & Data Handling
-
-- **Local Operation**: All cleanup happens locally on your machine
-- **No Cloud Backup**: Deleted tasks are not backed up automatically
-- **Telemetry**: Anonymous usage statistics (tasks cleaned, disk space freed) are collected if telemetry is enabled
-- **No Content Sharing**: Task content, code, or personal information is never transmitted
-
-## Related Features
-
-- [**Checkpoints**](../features/checkpoints): Version control for tasks that can be restored
-- [**Settings Management**](../features/settings-management): Export/import settings including cleanup configuration
-- [**Task History**](../basic-usage/the-chat-interface): Managing and organizing your task history
-
-## Frequently Asked Questions
-
-### Does Auto-Cleanup run automatically?
-
-Yes, when enabled, Auto-Cleanup runs automatically based on the configured schedule. You can also trigger it manually using the "Run Cleanup Now" button.
-
-### Can I recover deleted tasks?
-
-No, task deletion is permanent. Always favorite important tasks or adjust retention periods to prevent accidental deletion.
-
-### Does cleanup affect my current task?
-
-No, the active task you're currently working on is automatically protected from deletion.
-
-### What happens to checkpoints when a task is deleted?
-
-All checkpoints associated with a deleted task are permanently removed along with the task data.
-
-### Can I temporarily disable cleanup?
-
-Yes, simply uncheck the "Enable automatic task cleanup" option in settings. Your configuration is preserved for when you enable it again.
-
-### Why are some old tasks not being deleted?
-
-Check if they are:
-
-1. Favorited with "Never delete favorited tasks" enabled
-2. Recently modified (even viewing a task may update its timestamp)
-3. Protected by a longer retention period based on their type
diff --git a/packages/kilo-docs/docs/advanced-usage/available-tools/codebase-search.md b/packages/kilo-docs/docs/advanced-usage/available-tools/codebase-search.md
deleted file mode 100644
index 712a59acc82..00000000000
--- a/packages/kilo-docs/docs/advanced-usage/available-tools/codebase-search.md
+++ /dev/null
@@ -1,240 +0,0 @@
-# codebase_search
-
-:::warning Experimental Feature
-The `codebase_search` tool is that requires additional setup including an embedding provider and vector database.
-:::
-
-The `codebase_search` tool performs semantic searches across your entire codebase using AI embeddings. Unlike traditional text-based search, it understands the meaning of your queries and finds relevant code even when exact keywords don't match.
-
-## Parameters
-
-The tool accepts these parameters:
-
-- `query` (required): Natural language search query describing what you're looking for
-- `path` (optional): Directory path to limit search scope to a specific part of your codebase
-
-## What It Does
-
-This tool searches through your indexed codebase using semantic similarity rather than exact text matching. It finds code blocks that are conceptually related to your query, even if they don't contain the exact words you searched for. Results include relevant code snippets with file paths, line numbers, and similarity scores.
-
-## When is it used?
-
-- When Kilo Code needs to find code related to specific functionality across your project
-- When looking for implementation patterns or similar code structures
-- When searching for error handling, authentication, or other conceptual code patterns
-- When exploring unfamiliar codebases to understand how features are implemented
-- When finding related code that might be affected by changes or refactoring
-
-## Key Features
-
-- **Semantic Understanding**: Finds code by meaning rather than exact keyword matches
-- **Cross-Project Search**: Searches across your entire indexed codebase, not just open files
-- **Contextual Results**: Returns code snippets with file paths and line numbers for easy navigation
-- **Similarity Scoring**: Results ranked by relevance with similarity scores (0-1 scale)
-- **Scope Filtering**: Optional path parameter to limit searches to specific directories
-- **Intelligent Ranking**: Results sorted by semantic relevance to your query
-- **UI Integration**: Results displayed with syntax highlighting and navigation links
-- **Performance Optimized**: Fast vector-based search with configurable result limits
-
-## Requirements
-
-This tool is only available when the experimental Codebase Indexing feature is properly configured:
-
-- **Feature Enabled**: Codebase Indexing must be enabled in experimental settings
-- **Embedding Provider**: OpenAI API key or Ollama configuration required
-- **Vector Database**: Qdrant instance running and accessible
-- **Index Status**: Codebase must be indexed (status: "Indexed" or "Indexing")
-
-## Limitations
-
-- **Experimental Feature**: Part of the experimental codebase indexing system
-- **Requires Configuration**: Depends on external services (embedding provider + Qdrant)
-- **Index Dependency**: Only searches through indexed code blocks
-- **Result Limits**: Maximum of 50 results per search to maintain performance
-- **Similarity Threshold**: Only returns results above 0.4 similarity score
-- **File Size Limits**: Limited to files under 1MB that were successfully indexed
-- **Language Support**: Effectiveness depends on Tree-sitter language support
-
-## How It Works
-
-When the `codebase_search` tool is invoked, it follows this process:
-
-1. **Availability Validation**:
-
- - Verifies that the CodeIndexManager is available and initialized
- - Confirms codebase indexing is enabled in settings
- - Checks that indexing is properly configured (API keys, Qdrant URL)
- - Validates the current index state allows searching
-
-2. **Query Processing**:
-
- - Takes your natural language query and generates an embedding vector
- - Uses the same embedding provider configured for indexing (OpenAI or Ollama)
- - Converts the semantic meaning of your query into a mathematical representation
-
-3. **Vector Search Execution**:
-
- - Searches the Qdrant vector database for similar code embeddings
- - Uses cosine similarity to find the most relevant code blocks
- - Applies the minimum similarity threshold (0.4) to filter results
- - Limits results to 50 matches for optimal performance
-
-4. **Path Filtering** (if specified):
-
- - Filters results to only include files within the specified directory path
- - Uses normalized path comparison for accurate filtering
- - Maintains relevance ranking within the filtered scope
-
-5. **Result Processing and Formatting**:
-
- - Converts absolute file paths to workspace-relative paths
- - Structures results with file paths, line ranges, similarity scores, and code content
- - Formats for both AI consumption and UI display with syntax highlighting
-
-6. **Dual Output Format**:
- - **AI Output**: Structured text format with query, file paths, scores, and code chunks
- - **UI Output**: JSON format with syntax highlighting and navigation capabilities
-
-## Search Query Best Practices
-
-### Effective Query Patterns
-
-**Good: Conceptual and specific**
-
-```xml
-
-1. **Open Agent Behaviour Tab:** Click the 
- * **Open Agent Behaviour Tab:** Click the 
-
-*Context mentions overview showing the @ symbol dropdown menu in the chat interface.*
-
-## Types of Mentions
-
-
-
-*File mentions add actual code content into the conversation for direct reference and analysis.*
-
-| Mention Type | Format | Description | Example Usage |
-|--------------|--------|-------------|--------------|
-| **File** | `@/path/to/file.ts` | Includes file contents in request context | "Explain the function in @/src/utils.ts" |
-| **Folder** | `@/path/to/folder/` | Provides directory structure in tree format | "What files are in @/src/components/?" |
-| **Problems** | `@problems` | Includes VS Code Problems panel diagnostics | "@problems Fix all errors in my code" |
-| **Terminal** | `@terminal` | Includes recent terminal command and output | "Fix the errors shown in @terminal" |
-| **Git Commit** | `@a1b2c3d` | References specific commit by hash | "What changed in commit @a1b2c3d?" |
-| **Git Changes** | `@git-changes` | Shows uncommitted changes | "Suggest a message for @git-changes" |
-| **URL** | `@https://example.com` | Imports website content | "Summarize @https://docusaurus.io/" |
-
-### File Mentions
-
-
-
-*File mentions incorporate source code with line numbers for precise references.*
-| Capability | Details |
-|------------|---------|
-| **Format** | `@/path/to/file.ts` (always start with `/` from workspace root) |
-| **Provides** | Complete file contents with line numbers |
-| **Supports** | Text files, PDFs, and DOCX files (with text extraction) |
-| **Works in** | Initial requests, feedback responses, and follow-up messages |
-| **Limitations** | Very large files may be truncated; binary files not supported |
-
-### Folder Mentions
-
-
-
-*Folder mentions display directory structure in a readable tree format.*
-| Capability | Details |
-|------------|---------|
-| **Format** | `@/path/to/folder/` (note trailing slash) |
-| **Provides** | Hierarchical tree display with ├── and └── prefixes |
-| **Includes** | Immediate child files and directories (not recursive) |
-| **Best for** | Understanding project structure |
-| **Tip** | Use with file mentions to check specific file contents |
-
-### Problems Mention
-
-
-
-*Problems mentions import diagnostics directly from VS Code's problems panel.*
-| Capability | Details |
-|------------|---------|
-| **Format** | `@problems` |
-| **Provides** | All errors and warnings from VS Code's problems panel |
-| **Includes** | File paths, line numbers, and diagnostic messages |
-| **Groups** | Problems organized by file for better clarity |
-| **Best for** | Fixing errors without manual copying |
-
-### Terminal Mention
-
-
-*Terminal mentions capture recent command output for debugging and analysis.*
-
-| Capability | Details |
-|------------|---------|
-| **Format** | `@terminal` |
-| **Captures** | Last command and its complete output |
-| **Preserves** | Terminal state (doesn't clear the terminal) |
-| **Limitation** | Limited to visible terminal buffer content |
-| **Best for** | Debugging build errors or analyzing command output |
-
-### Git Mentions
-
-
-
-*Git mentions provide commit details and diffs for context-aware version analysis.*
-| Type | Format | Provides | Limitations |
-|------|--------|----------|------------|
-| **Commit** | `@a1b2c3d` | Commit message, author, date, and complete diff | Only works in Git repositories |
-| **Working Changes** | `@git-changes` | `git status` output and diff of uncommitted changes | Only works in Git repositories |
-
-### URL Mentions
-
-
-*URL mentions import external web content and convert it to readable Markdown format.*
-
-| Capability | Details |
-|------------|---------|
-| **Format** | `@https://example.com` |
-| **Processing** | Uses headless browser to fetch content |
-| **Cleaning** | Removes scripts, styles, and navigation elements |
-| **Output** | Converts content to Markdown for readability |
-| **Limitation** | Complex pages may not convert perfectly |
-
-## How to Use Mentions
-
-1. Type `@` in the chat input to trigger the suggestions dropdown
-2. Continue typing to filter suggestions or use arrow keys to navigate
-3. Select with Enter key or mouse click
-4. Combine multiple mentions in a request: "Fix @problems in @/src/component.ts"
-
-The dropdown automatically suggests:
-- Recently opened files
-- Visible folders
-- Recent git commits
-- Special keywords (`problems`, `terminal`, `git-changes`)
-
-## Best Practices
-
-| Practice | Description |
-|----------|-------------|
-| **Use specific paths** | Reference exact files rather than describing them |
-| **Use relative paths** | Always start from workspace root: `@/src/file.ts` not `@C:/Projects/src/file.ts` |
-| **Verify references** | Ensure paths and commit hashes are correct |
-| **Click mentions** | Click mentions in chat history to open files or view content |
-| **Eliminate copy-pasting** | Use mentions instead of manually copying code or errors |
-| **Combine mentions** | "Fix @problems in @/src/component.ts using the pattern from commit @a1b2c3d" |
diff --git a/packages/kilo-docs/docs/basic-usage/how-tools-work.md b/packages/kilo-docs/docs/basic-usage/how-tools-work.md
deleted file mode 100644
index a0f5aaa7529..00000000000
--- a/packages/kilo-docs/docs/basic-usage/how-tools-work.md
+++ /dev/null
@@ -1,83 +0,0 @@
-# How Tools Work
-
-Kilo Code uses tools to interact with your code and environment. These specialized helpers perform specific actions like reading files, making edits, running commands, or searching your codebase. Tools provide automation for common development tasks without requiring manual execution.
-
-## Tool Workflow
-
-Describe what you want to accomplish in natural language, and Kilo Code will:
-
-1. Select the appropriate tool based on your request
-2. Present the tool with its parameters for your review
-3. Execute the approved tool and show you the results
-4. Continue this process until your task is complete
-
-## Tool Categories
-
-| Category | Purpose | Tool Names |
-| :------- | :------ | :--------- |
-| Read | Access file content and code structure | `read_file`, `search_files`, `list_files`, `list_code_definition_names` |
-| Edit | Create or modify files and code | `write_to_file`, `apply_diff` |
-| Execute | Run commands and perform system operations | `execute_command` |
-| Browser | Interact with web content | `browser_action` |
-| Workflow | Manage task flow and context | `ask_followup_question`, `attempt_completion`, `switch_mode`, `new_task` |
-
-## Example: Using Tools
-
-Here's how a typical tool interaction works:
-
-
-
-*The tool approval interface shows Save/Reject buttons and Auto-approve options.*
-
-**User:** Create a file named `greeting.js` that logs a greeting message
-
-**Kilo Code:** (Proposes the `write_to_file` tool as shown in the image above)
-```xml
-
-
-3. Enter a name for your new profile
-
- 
-
-4. Configure the profile settings:
-
- - Select your API provider
- 
- - Enter API key
-
- 
-
- - Choose a model
-
- 
-
- - Adjust model parameters
-
- 
-
-### Switching Profiles
-
-Switch profiles in two ways:
-
-1. From Settings panel: Select a different profile from the dropdown
-
- 
-
-2. During chat: Access the API Configuration dropdown in the chat interface
-
- 
-
-### Pinning and Sorting Profiles
-
-The API configuration dropdown now supports pinning your favorite profiles for quicker access:
-
-1. Hover over any profile in the dropdown to reveal the pin icon
-2. Click the pin icon to add the profile to your pinned list
-3. Pinned profiles appear at the top of the dropdown, sorted alphabetically
-4. Unpinned profiles appear below a separator, also sorted alphabetically
-5. You can unpin a profile by clicking the same icon again
-
-
-
-This feature makes it easier to navigate between commonly used profiles, especially when you have many configurations.
-
-### Editing and Deleting Profiles
-
-
-- Select the profile in Settings to modify any settings
-- Click the pencil icon to rename a profile
-- Click the trash icon to delete a profile (you cannot delete the only remaining profile)
-
-## Linking Profiles to Modes
-
-In the 
-
-_Prompt box and Auto-Approve Toolbar showing enabled permissions_
-
-Click the toolbar to expand it and configure individual permissions:
-
-
-
-_Prompt text box and Expanded toolbar with all options_
-
-### Available Permissions
-
-| Permission | What it does | Risk level |
-| ------------------------------ | ------------------------------------------------ | ----------- |
-| **Read files and directories** | Lets Kilo Code access files without asking | Medium |
-| **Edit files** | Lets Kilo Code modify files without asking | **High** |
-| **Execute approved commands** | Runs whitelisted terminal commands automatically | **High** |
-| **Use the browser** | Allows headless browser interaction | Medium |
-| **Use MCP servers** | Lets Kilo Code use configured MCP services | Medium-High |
-| **Switch modes** | Changes between Kilo Code modes automatically | Low |
-| **Create & complete subtasks** | Manages subtasks without confirmation | Low |
-| **Retry failed requests** | Automatically retries failed API requests | Low |
-| **Answer follow-up questions** | Selects default answer for follow-up questions | Low |
-| **Update todo list** | Automatically updates task progress | Low |
-
-## Master Toggle for Quick Control
-
-The leftmost checkbox works as a master toggle:
-
-
-
-_Master toggle (checkbox) controls all auto-approve permissions at once_
-
-Use the master toggle when:
-
-- Working in sensitive code (turn off)
-- Doing rapid development (turn on)
-- Switching between exploration and editing tasks
-
-## Advanced Settings Panel
-
-The settings panel provides detailed control with important security context:
-
-> **Allow Kilo Code to automatically perform operations without requiring approval. Enable these settings only if you fully trust the AI and understand the associated security risks.**
-
-To access these settings:
-
-1. Click 
-
-_Complete settings panel view_
-
-### Read Operations
-
-:::caution Read Operations
-
-
-**Setting:** "Always approve read-only operations"
-
-**Description:** "When enabled, Kilo Code will automatically view directory contents and read files without requiring you to click the Approve button."
-
-**Risk level:** Medium
-
-While this setting only allows reading files (not modifying them), it could potentially expose sensitive data. Still recommended as a starting point for most users, but be mindful of what files Kilo Code can access.
-
-#### Read Outside Workspace
-
-**Setting:** "Allow reading files outside the workspace"
-
-**Description:** "When enabled, Kilo Code can read files outside the current workspace directory without asking for approval."
-
-**Risk level:** Medium-High
-
-This setting extends read permissions beyond your project folder. Consider the security implications:
-
-- Kilo Code could access sensitive files in your home directory
-- Configuration files, SSH keys, or credentials could be read
-- Only enable if you trust the AI and need it to access external files
-
-**Recommendation:** Keep disabled unless you specifically need Kilo Code to read files outside your project.
-:::
-
-### Write Operations
-
-:::caution Write Operations
-
-
-**Setting:** "Always approve write operations"
-
-**Description:** "Automatically create and edit files without requiring approval"
-
-**Delay slider:** "Delay after writes to allow diagnostics to detect potential problems" (Default: 1000ms)
-
-**Risk level:** High
-
-This setting allows Kilo Code to modify your files without confirmation. The delay timer is crucial:
-
-- Higher values (2000ms+): Recommended for complex projects where diagnostics take longer
-- Default (1000ms): Suitable for most projects
-- Lower values: Use only when speed is critical and you're in a controlled environment
-- Zero: No delay for diagnostics (not recommended for critical code)
-
-#### Write Outside Workspace
-
-**Setting:** "Allow writing files outside the workspace"
-
-**Description:** "When enabled, Kilo Code can create or modify files outside the current workspace directory without asking for approval."
-
-**Risk level:** Very High
-
-Use with caution and in controlled environments. It allows Kilo Code to:
-
-- Modify your shell configuration files
-- Change system configurations
-- Write to any location your user has access to
-
-**Recommendation:** Keep disabled unless absolutely necessary. Even experienced users should avoid this setting.
-
-#### Write to Protected Files
-
-**Setting:** "Allow writing to protected files"
-
-**Description:** "When enabled, Kilo Code can overwrite or modify files that are normally protected by the `.kilocodeignore` file."
-
-**Risk level:** Very High
-
-Protected files are intentionally shielded from modification. Enable only if you understand the consequences.
-
-### Delete Operations
-
-:::danger Delete Operations
-
-**Setting:** "Always approve delete operations"
-
-**Description:** "Automatically delete files and directories without requiring approval"
-
-**Risk level:** Very High
-
-This setting allows Kilo Code to permanently remove files without confirmation.
-
-**Safeguards:**
-
-- Kilo Code still respects `.kilocodeignore` rules
-- Protected files cannot be deleted
-- The delete tool shows what will be removed before execution
-
-**Recommendation:** Enable only in isolated environments or when working with temporary/generated files. Always ensure you have backups, checkpoints, or version control.
-:::
-
-### Browser Actions
-
-:::info Browser Actions
-
-
-**Setting:** "Always approve browser actions"
-
-**Description:** "Automatically perform browser actions without requiring approval"
-
-**Note:** "Only applies when the model supports computer use"
-
-**Risk level:** Medium
-
-Allows Kilo Code to control a headless browser without confirmation. This can include:
-
-- Opening websites
-- Navigating pages
-- Interacting with web elements
-
-Consider the security implications of allowing automated browser access.
-:::
-
-### API Requests
-
-:::info API Requests
-
-
-**Setting:** "Always retry failed API requests"
-
-**Description:** "Automatically retry failed API requests when server returns an error response"
-
-**Risk level:** Low
-
-This setting automatically retries API calls when they fail.
-
-The delay controls how long Kilo Code waits before trying again:
-
-- Longer delays are gentler on API rate limits
-- Shorter delays give faster recovery from transient errors
- :::
-
-### MCP Tools
-
-:::caution MCP Tools
-
-
-**Setting:** "Always approve MCP tools"
-
-**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 Agent Behaviour > MCP Servers view. Both this global setting and the tool-specific permission must be enabled for auto-approval.
-:::
-
-### Mode Switching
-
-:::info Mode Switching
-
-
-**Setting:** "Always approve mode switching"
-
-**Description:** "Automatically switch between different modes without requiring approval"
-
-**Risk level:** Low
-
-Allows Kilo Code to change between different modes (Code, Architect, etc.) without asking for permission. This primarily affects the AI's behavior rather than system access.
-:::
-
-### Subtasks
-
-:::info Subtasks
-
-
-**Setting:** "Always approve creation & completion of subtasks"
-
-**Description:** "Allow creation and completion of subtasks without requiring approval"
-
-**Risk level:** Low
-
-Enables Kilo Code to create and complete subtasks automatically. This relates to workflow organization rather than system access.
-:::
-
-### Command Execution
-
-:::caution Command Execution
-
-
-**Setting:** "Always approve allowed execute operations"
-
-**Description:** "Automatically execute allowed terminal commands without requiring approval"
-
-**Risk level:** High
-
-This setting allows terminal command execution with controls. While risky, the allowlist and denylist features limit what commands can run.
-
-- Allowlist specific command prefixes (recommended)
-- Never use \* wildcard in production or with sensitive data
-- Consider security implications of each allowed command
-- Consider including potentially dangerous common commands in the deny list
-- Always verify commands that interact with external systems
-
-#### Allowed Commands
-
-**Setting:** "Command prefixes that can be auto-executed"
-
-Add command prefixes (e.g., `git`, `npm`, `ls`) that Kilo Code can run without asking. Use `*` to allow all commands (use with caution).
-
-**Interface elements:**
-
-- Text field to enter command prefixes (e.g., 'git')
-- "Add" button to add new prefixes
-- Clickable command buttons with X to remove them
-
-#### Denied Commands
-
-**Setting:** "Command prefixes that are always blocked"
-
-Commands in this list will never run, even if `*` is in the allowed list. Use this to create exceptions for potentially dangerous commands.
-:::
-
-### Follow-Up Questions
-
-:::info Follow-Up Questions (Risk: Low)
-
-**Setting:** `Always default answer for follow-up questions`
-
-**Description:** Automatically selects the first AI-suggested answer for a follow-up question after a configurable timeout. This speeds up your workflow by letting Kilo Code proceed without manual intervention.
-
-**Visual countdown:** When enabled, a countdown timer appears on the first suggestion button in the chat interface, showing the remaining time before auto-selection. The timer displays seconds remaining (e.g., "3s") and counts down in real-time.
-
-**Timeout slider:** Use the slider to set the wait time (Range: 1-300 seconds, Default: 60s).
-
-**Override options:** You can cancel the auto-selection at any time by:
-
-- Clicking a different suggestion
-- Editing any suggestion
-- Typing your own response
-- Clicking the timer to pause it
-
-**Risk level:** Low
-
-**Use cases:**
-
-- Overnight runs where you want Kilo Code to continue working
-- Repetitive tasks where the default suggestions are usually correct
-- Testing workflows where interaction isn't critical
- :::
-
-### Update Todo List
-
-:::info Update Todo List (Risk: Low)
-
-**Setting:** "Always approve todo list updates"
-
-**Description:** "Automatically update the to-do list without requiring approval"
-
-**Risk level:** Low
-
-This setting allows Kilo Code to automatically update task progress and todo lists during work sessions. This includes:
-
-- Marking tasks as completed
-- Adding new discovered tasks
-- Updating task status (pending, in progress, completed)
-- Reorganizing task priorities
-
-**Use cases:**
-
-- Long-running development sessions
-- Multi-step refactoring projects
-- Complex debugging workflows
-- Feature implementation with many subtasks
-
-This is particularly useful when combined with the Subtasks permission, as it allows Kilo Code to maintain a complete picture of project progress without constant approval requests.
-:::
-
-## YOLO Mode
-
-:::danger YOLO Mode (Risk: Maximum)
-
-**"You Only Live Once"** mode enables _all_ auto-approve permissions at once using the master toggle. This gives Kilo Code complete autonomy to read files, write code, execute commands, and perform any operation without asking for permission.
-
-You can optionally enable an AI Safety Gatekeeper, which reviews every intended change in YOLO mode and intelligently approves or blocks actions before they execute. We suggest using a small, fast model such as OpenAI gpt-oss-safeguard-20b. When enabled, AI Safety Gatekeeper will incur additional costs, as well as additional latency.
-
-**When to use:**
-
-- Rapid prototyping in isolated environments
-- Trusted, low-stakes projects
-- When you want maximum AI autonomy
-
-**When NOT to use:**
-
-- Production code or sensitive projects
-- Working with important data
-- Any situation where mistakes could be costly
-
-This is the fastest way to work with Kilo Code, but also the riskiest. Use it only when you fully trust the AI and are prepared for the consequences.
-:::
diff --git a/packages/kilo-docs/docs/features/enhance-prompt.md b/packages/kilo-docs/docs/features/enhance-prompt.md
deleted file mode 100644
index f9aa705cc08..00000000000
--- a/packages/kilo-docs/docs/features/enhance-prompt.md
+++ /dev/null
@@ -1,54 +0,0 @@
-# Enhance Prompt
-
-The "Enhance Prompt" feature in Kilo Code helps you improve the quality and effectiveness of your prompts before sending them to the AI model. By clicking the 
-
-
-## How to Use Enhance Prompt
-
-1. **Type your initial prompt:** Enter your request in the Kilo Code chat input box as you normally would. This can be a simple question, a complex task description, or anything in between.
-2. **Click the 
-
-For a detailed walkthrough: https://youtu.be/R1nDnCK-xzw
-
-## Limitations and Best Practices
-
-* **Experimental Feature:** Prompt enhancement is an experimental feature. The quality of the enhanced prompt may vary depending on the complexity of your request and the capabilities of the underlying model.
-* **Review Carefully:** Always review the enhanced prompt before sending it. Kilo Code may make changes that don't align with your intentions.
-* **Iterative Process:** You can use the "Enhance Prompt" feature multiple times to iteratively refine your prompt.
-* **Not a Replacement for Clear Instructions:** While "Enhance Prompt" can help, it's still important to write clear and specific prompts from the start.
-
-By using the "Enhance Prompt" feature, you can improve the quality of your interactions with Kilo Code and get more accurate and helpful responses.
diff --git a/packages/kilo-docs/docs/features/experimental/experimental-features.md b/packages/kilo-docs/docs/features/experimental/experimental-features.md
deleted file mode 100644
index 6a01cf875fd..00000000000
--- a/packages/kilo-docs/docs/features/experimental/experimental-features.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Experimental Features
-
-Kilo Code includes experimental features that are still under development. These features may be unstable, change significantly, or be removed in future versions. Use them with caution and be aware that they may not work as expected.
-
-**Warning:** Experimental features may have unexpected behavior, including potential data loss or security vulnerabilities. Enable them at your own risk.
-
-## Enabling Experimental Features
-
-To enable or disable experimental features:
-
-1. Open the Kilo Code settings (
-
-
-## Key Considerations & Warnings
-
-- **Intended Audience:** Best suited for users deeply familiar with Kilo Code's prompting system and the implications of modifying core instructions.
-- **Impact on Functionality:** Custom prompts override standard instructions, including those for tool usage and response consistency. This can cause unexpected behavior or errors if not managed carefully.
-- **Mode-Specific:** Each override file applies only to the mode specified in its filename (`{mode-slug}`).
-- **No File, No Override:** If the `.kilocode/system-prompt-{mode-slug}` file doesn't exist, Kilo Code uses the standard system prompt generation process for that mode.
-- **Directory Creation:** Kilo Code ensures the `.kilocode` directory exists before attempting to read or create the override file.
-
-Use this feature cautiously. While powerful for customization, incorrect implementation can significantly degrade Kilo Code's performance and reliability for the affected mode.
diff --git a/packages/kilo-docs/docs/features/mcp/server-transports.md b/packages/kilo-docs/docs/features/mcp/server-transports.md
deleted file mode 100644
index 8138c6785c8..00000000000
--- a/packages/kilo-docs/docs/features/mcp/server-transports.md
+++ /dev/null
@@ -1,196 +0,0 @@
----
-title: MCP Server Transports
-sidebar_label: STDIO & SSE Transports
----
-
-# MCP Server Transports: STDIO & SSE
-
-Model Context Protocol (MCP) supports two primary transport mechanisms for communication between Kilo Code and MCP servers: Standard Input/Output (STDIO) and Server-Sent Events (SSE). Each has distinct characteristics, advantages, and use cases.
-
-## STDIO Transport
-
-STDIO transport runs locally on your machine and communicates via standard input/output streams.
-
-### How STDIO Transport Works
-
-1. The client (Kilo Code) spawns an MCP server as a child process
-2. Communication happens through process streams: client writes to server's STDIN, server responds to STDOUT
-3. Each message is delimited by a newline character
-4. Messages are formatted as JSON-RPC 2.0
-
-```
-Client Server
- | |
- |---- JSON message ------>| (via STDIN)
- | | (processes request)
- |<---- JSON message ------| (via STDOUT)
- | |
-```
-
-### STDIO Characteristics
-
-* **Locality**: Runs on the same machine as Kilo Code
-* **Performance**: Very low latency and overhead (no network stack involved)
-* **Simplicity**: Direct process communication without network configuration
-* **Relationship**: One-to-one relationship between client and server
-* **Security**: Inherently more secure as no network exposure
-
-### When to Use STDIO
-
-STDIO transport is ideal for:
-
-* Local integrations and tools running on the same machine
-* Security-sensitive operations
-* Low-latency requirements
-* Single-client scenarios (one Kilo Code instance per server)
-* Command-line tools or IDE extensions
-
-### STDIO Implementation Example
-
-```typescript
-import { Server } from '@modelcontextprotocol/sdk/server/index.js';
-import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
-
-const server = new Server({name: 'local-server', version: '1.0.0'});
-// Register tools...
-
-// Use STDIO transport
-const transport = new StdioServerTransport(server);
-transport.listen();
-```
-
-## SSE Transport
-
-Server-Sent Events (SSE) transport runs on a remote server and communicates over HTTP/HTTPS.
-
-### How SSE Transport Works
-
-1. The client (Kilo Code) connects to the server's SSE endpoint via HTTP GET request
-2. This establishes a persistent connection where the server can push events to the client
-3. For client-to-server communication, the client makes HTTP POST requests to a separate endpoint
-4. Communication happens over two channels:
- * Event Stream (GET): Server-to-client updates
- * Message Endpoint (POST): Client-to-server requests
-
-```
-Client Server
- | |
- |---- HTTP GET /events ----------->| (establish SSE connection)
- |<---- SSE event stream -----------| (persistent connection)
- | |
- |---- HTTP POST /message --------->| (client request)
- |<---- SSE event with response ----| (server response)
- | |
-```
-
-### SSE Characteristics
-
-* **Remote Access**: Can be hosted on a different machine from Kilo Code
-* **Scalability**: Can handle multiple client connections concurrently
-* **Protocol**: Works over standard HTTP (no special protocols needed)
-* **Persistence**: Maintains a persistent connection for server-to-client messages
-* **Authentication**: Can use standard HTTP authentication mechanisms
-
-### When to Use SSE
-
-SSE transport is better for:
-
-* Remote access across networks
-* Multi-client scenarios
-* Public services
-* Centralized tools that many users need to access
-* Integration with web services
-
-### SSE Implementation Example
-
-```typescript
-import { Server } from '@modelcontextprotocol/sdk/server/index.js';
-import { SSEServerTransport } from '@modelcontextprotocol/sdk/server/sse.js';
-import express from 'express';
-
-const app = express();
-const server = new Server({name: 'remote-server', version: '1.0.0'});
-// Register tools...
-
-// Use SSE transport
-const transport = new SSEServerTransport(server);
-app.use('/mcp', transport.requestHandler());
-app.listen(3000, () => {
- console.log('MCP server listening on port 3000');
-});
-```
-## Local vs. Hosted: Deployment Aspects
-
-The choice between STDIO and SSE transports directly impacts how you'll deploy and manage your MCP servers.
-
-### STDIO: Local Deployment Model
-
-STDIO servers run locally on the same machine as Kilo Code, which has several important implications:
-
-* **Installation**: The server executable must be installed on each user's machine
-* **Distribution**: You need to provide installation packages for different operating systems
-* **Updates**: Each instance must be updated separately
-* **Resources**: Uses the local machine's CPU, memory, and disk
-* **Access Control**: Relies on the local machine's filesystem permissions
-* **Integration**: Easy integration with local system resources (files, processes)
-* **Execution**: Starts and stops with Kilo Code (child process lifecycle)
-* **Dependencies**: Any dependencies must be installed on the user's machine
-
-#### Practical Example
-
-A local file search tool using STDIO would:
-* Run on the user's machine
-* Have direct access to the local filesystem
-* Start when needed by Kilo Code
-* Not require network configuration
-* Need to be installed alongside Kilo Code or via a package manager
-
-### SSE: Hosted Deployment Model
-
-SSE servers can be deployed to remote servers and accessed over the network:
-
-* **Installation**: Installed once on a server, accessed by many users
-* **Distribution**: Single deployment serves multiple clients
-* **Updates**: Centralized updates affect all users immediately
-* **Resources**: Uses server resources, not local machine resources
-* **Access Control**: Managed through authentication and authorization systems
-* **Integration**: More complex integration with user-specific resources
-* **Execution**: Runs as an independent service (often continuously)
-* **Dependencies**: Managed on the server, not on user machines
-
-#### Practical Example
-
-A database query tool using SSE would:
-* Run on a central server
-* Connect to databases with server-side credentials
-* Be continuously available for multiple users
-* Require proper network security configuration
-* Be deployed using container or cloud technologies
-
-### Hybrid Approaches
-
-Some scenarios benefit from a hybrid approach:
-
-1. **STDIO with Network Access**: A local STDIO server that acts as a proxy to remote services
-2. **SSE with Local Commands**: A remote SSE server that can trigger operations on the client machine through callbacks
-3. **Gateway Pattern**: STDIO servers for local operations that connect to SSE servers for specialized functions
-
-## Choosing Between STDIO and SSE
-
-| Consideration | STDIO | SSE |
-|---------------|-------|-----|
-| **Location** | Local machine only | Local or remote |
-| **Clients** | Single client | Multiple clients |
-| **Performance** | Lower latency | Higher latency (network overhead) |
-| **Setup Complexity** | Simpler | More complex (requires HTTP server) |
-| **Security** | Inherently secure | Requires explicit security measures |
-| **Network Access** | Not needed | Required |
-| **Scalability** | Limited to local machine | Can distribute across network |
-| **Deployment** | Per-user installation | Centralized installation |
-| **Updates** | Distributed updates | Centralized updates |
-| **Resource Usage** | Uses client resources | Uses server resources |
-| **Dependencies** | Client-side dependencies | Server-side dependencies |
-
-## Configuring Transports in Kilo Code
-
-For detailed information on configuring STDIO and SSE transports in Kilo Code, including example configurations, see the [Understanding Transport Types](/features/mcp/using-mcp-in-kilo-code#understanding-transport-types) section in the Using MCP in Kilo Code guide.
\ No newline at end of file
diff --git a/packages/kilo-docs/docs/features/model-temperature.md b/packages/kilo-docs/docs/features/model-temperature.md
deleted file mode 100644
index f4780edf26d..00000000000
--- a/packages/kilo-docs/docs/features/model-temperature.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Model Temperature
-
-Temperature controls the randomness of AI model outputs. Adjusting this setting optimizes results for different tasks - from precise code generation to creative brainstorming. Temperature is one of the most powerful parameters for controlling AI behavior. A well-tuned temperature setting can dramatically improve the quality and appropriateness of responses for specific tasks.
-
-
-
-## What is Temperature?
-
-Temperature is a setting (usually between 0.0 and 2.0) that controls how random or predictable the AI's output is. Finding the right balance is key: lower values make the output more focused and consistent, while higher values encourage more creativity and variation. For many coding tasks, a moderate temperature (around 0.3 to 0.7) often works well, but the best setting depends on what you're trying to achieve.
-
-:::info Temperature and Code: Common Misconceptions
-Temperature controls output randomness, not code quality or accuracy directly. Key points:
-
-* **Low Temperature (near 0.0):** Produces predictable, consistent code. Good for simple tasks, but can be repetitive and lack creativity. It doesn't guarantee *better* code.
-* **High Temperature:** Increases randomness, potentially leading to creative solutions but also more errors or nonsensical code. It doesn't guarantee *higher-quality* code.
-* **Accuracy:** Code accuracy depends on the model's training and prompt clarity, not temperature.
-* **Temperature 0.0:** Useful for consistency, but limits exploration needed for complex problems.
-:::
-
-## Default Values in Kilo Code
-
-Kilo Code uses a default temperature of 0.0 for most models, optimizing for maximum determinism and precision in code generation. This applies to OpenAI models, Anthropic models (non-thinking variants), LM Studio models, and most other providers.
-
-Some models use higher default temperatures - DeepSeek R1 models and certain reasoning-focused models default to 0.6, providing a balance between determinism and creative exploration.
-
-Models with thinking capabilities (where the AI shows its reasoning process) require a fixed temperature of 1.0 which cannot be changed, as this setting ensures optimal performance of the thinking mechanism. This applies to any model with the ":thinking" flag enabled.
-
-Some specialized models don't support temperature adjustments at all, in which case Kilo Code respects these limitations automatically.
-
-## When to Adjust Temperature
-
-Here are some examples of temperature settings that might work well for different tasks:
-
-* **Code Mode (0.0-0.3):** For writing precise, correct code with consistent, deterministic results
-* **Architect Mode (0.4-0.7):** For brainstorming architecture or design solutions with balanced creativity and structure
-* **Ask Mode (0.7-1.0):** For explanations or open-ended questions requiring diverse and insightful responses
-* **Debug Mode (0.0-0.3):** For troubleshooting bugs with consistent precision
-
-These are starting points – it's important to [experiment with different settings](#experimentation) to find what works best for your specific needs and preferences.
-
-## How to Adjust Temperature
-
-1. **Open the Kilo Code Panel:** Click the Kilo Code icon (
) in the VS Code Side Bar
-2. **Open Settings:** Click the 
- *Temperature slider in Kilo Code settings panel*
-
-## Using API Configuration Profiles for Temperature
-
-Create multiple [API configuration profiles](/features/api-configuration-profiles) with different temperature settings:
-
-**How to set up task-specific temperature profiles:**
-
-1. Create specialized profiles like "Code - Low Temp" (0.1) and "Ask - High Temp" (0.8)
-2. Configure each profile with appropriate temperature settings
-3. Switch between profiles using the dropdown in settings or chat interface
-4. Set different profiles as defaults for each mode for automatic switching when changing modes
-
-This approach optimizes model behavior for specific tasks without manual adjustments.
-
-## Technical Implementation
-
-Kilo Code implements temperature handling with these considerations:
-
-* User-defined settings take priority over defaults
-* Provider-specific behaviors are respected
-* Model-specific limitations are enforced:
- * Thinking-enabled models require a fixed temperature of 1.0
- * Some models don't support temperature adjustments
-
-## Experimentation
-
-Experimenting with different temperature settings is the most effective way to discover what works best for your specific needs:
-
-### Effective Temperature Testing
-
-1. **Start with defaults** - Begin with Kilo Code's preset values (0.0 for most tasks) as your baseline
-2. **Make incremental adjustments** - Change values in small steps (±0.1) to observe subtle differences
-3. **Test consistently** - Use the same prompt across different temperature settings for valid comparisons
-4. **Document results** - Note which values produce the best outcomes for specific types of tasks
-5. **Create profiles** - Save effective settings as [API configuration profiles](/features/api-configuration-profiles) for quick access
-
-Remember that different models may respond differently to the same temperature values, and thinking-enabled models always use a fixed temperature of 1.0 regardless of your settings.
-
-## Related Features
-
-- Works with all [API providers](/providers/openai) supported by Kilo Code
-- Complements [custom instructions](/advanced-usage/custom-instructions) for fine-tuning responses
-- Works alongside [custom modes](/features/custom-modes) you create
\ No newline at end of file
diff --git a/packages/kilo-docs/docs/features/more-features.md b/packages/kilo-docs/docs/features/more-features.md
deleted file mode 100644
index a8b47b644ab..00000000000
--- a/packages/kilo-docs/docs/features/more-features.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-sidebar_label: Additional Features
----
-
-
-# Additional Features
-
-Kilo Code's extras streamline routine tasks and improve accessibility.
-
-## Suggested Responses
-
-Kilo Code offers suggested responses so you spend less time typing.
-- After you ask a question, buttons appear below the chat box.
-- Click a button to reuse it as your next prompt.
-
-## Text to Speech
-
-The Text-to-Speech feature lets Kilo Code read responses aloud.
-1. Enable TTS in settings.
-2. Click the speaker icon next to any response to start listening.
-
-## Global Language Support
-
-Kilo Code supports 14 languages:
-
-- Simplified Chinese
-- Traditional Chinese
-- Spanish
-- Hindi
-- French
-- Portuguese
-- German
-- Japanese
-- Korean
-- Italian
-- Turkish
-- Vietnamese
-- Polish
-- Catalan
-
-Change languages under **Advanced Settings > Language**.
diff --git a/packages/kilo-docs/docs/features/suggested-responses.md b/packages/kilo-docs/docs/features/suggested-responses.md
deleted file mode 100644
index 4a9fb07ca6c..00000000000
--- a/packages/kilo-docs/docs/features/suggested-responses.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-sidebar_label: Suggested Responses
----
-
-import Codicon from '@site/src/components/Codicon';
-
-# Suggested Responses
-
-When Kilo Code needs more information to complete a task, it uses the [`ask_followup_question` tool](/features/tools/ask-followup-question). To make responding easier and faster, Kilo Code often provides suggested answers alongside the question.
-
-## Overview
-
-Suggested Responses appear as clickable buttons directly below Kilo Code's question in the chat interface. They offer pre-formulated answers relevant to the question, helping you provide input quickly.
-
-
-
-## How It Works
-
-1. **Question Appears**: Kilo Code asks a question using the `ask_followup_question` tool.
-2. **Suggestions Displayed**: If suggestions are provided by Kilo Code, they appear as buttons below the question.
-3. **Interaction**: You can interact with these suggestions in two ways.
-
-## Interacting with Suggestions
-
-You have two options for using suggested responses:
-
-1. **Direct Selection**:
- * **Action**: Simply click the button containing the answer you want to provide.
- * **Result**: The selected answer is immediately sent back to Kilo Code as your response. This is the quickest way to reply if one of the suggestions perfectly matches your intent.
-
-2. **Edit Before Sending**:
- * **Action**:
- * Hold down `Shift` and click the suggestion button.
- * *Alternatively*, hover over the suggestion button and click the pencil icon (
-
-## Benefits
-
-* **Speed**: Quickly respond without typing full answers.
-* **Clarity**: Suggestions often clarify the type of information Kilo Code needs.
-* **Flexibility**: Edit suggestions to provide precise, customized answers when needed.
-
-This feature streamlines the interaction when Kilo Code requires clarification, allowing you to guide the task effectively with minimal effort.
\ No newline at end of file
diff --git a/packages/kilo-docs/docs/features/tools/access-mcp-resource.md b/packages/kilo-docs/docs/features/tools/access-mcp-resource.md
deleted file mode 100644
index 16af3cfbfc6..00000000000
--- a/packages/kilo-docs/docs/features/tools/access-mcp-resource.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# access_mcp_resource
-
-The `access_mcp_resource` tool retrieves data from resources exposed by connected Model Context Protocol (MCP) servers. It allows Kilo Code to access files, API responses, documentation, or system information that provides additional context for tasks.
-
-## Parameters
-
-The tool accepts these parameters:
-
-- `server_name` (required): The name of the MCP server providing the resource
-- `uri` (required): The URI identifying the specific resource to access
-
-## What It Does
-
-This tool connects to MCP servers and fetches data from their exposed resources. Unlike `use_mcp_tool` which executes actions, this tool specifically retrieves information that serves as context for tasks.
-
-## When is it used?
-
-- When Kilo Code needs additional context from external systems
-- When Kilo Code needs to access domain-specific data from specialized MCP servers
-- When Kilo Code needs to retrieve reference documentation hosted by MCP servers
-- When Kilo Code needs to integrate real-time data from external APIs via MCP
-
-## Key Features
-
-- Retrieves both text and image data from MCP resources
-- Requires user approval before executing resource access
-- Uses URI-based addressing to precisely identify resources
-- Integrates with the Model Context Protocol SDK
-- Displays resource content appropriately based on content type
-- Supports timeouts for reliable network operations
-- Handles server connection states (connected, connecting, disconnected)
-- Discovers available resources from connected servers
-- Processes structured response data with metadata
-- Handles image content special rendering
-
-## Limitations
-
-- Depends on external MCP servers being available and connected
-- Limited to the resources provided by connected servers
-- Cannot access resources from disabled servers
-- Network issues can affect reliability and performance
-- Resource access subject to configured timeouts
-- URI formats are determined by the specific MCP server implementation
-- No offline or cached resource access capabilities
-
-## How It Works
-
-When the `access_mcp_resource` tool is invoked, it follows this process:
-
-1. **Connection Validation**:
- - Verifies that an MCP hub is available and initialized
- - Confirms the specified server exists in the connection list
- - Checks if the server is disabled (returns an error if it is)
-
-2. **User Approval**:
- - Presents the resource access request to the user for approval
- - Provides server name and resource URI for user verification
- - Proceeds only if the user approves the resource access
-
-3. **Resource Request**:
- - Uses the Model Context Protocol SDK to communicate with servers
- - Makes a `resources/read` request to the server through the MCP hub
- - Applies configured timeouts to prevent hanging on unresponsive servers
-
-4. **Response Processing**:
- - Receives a structured response with metadata and content arrays
- - Processes text content for display to the user
- - Handles image data specially for appropriate display
- - Returns the processed resource data to Kilo Code for use in the current task
-
-## Resource Types
-
-MCP servers can provide two main types of resources:
-
-1. **Standard Resources**:
- - Fixed resources with specific URIs
- - Defined name, description, and MIME type
- - Direct access without parameters
- - Typically represent static data or real-time information
-
-2. **Resource Templates**:
- - Parameterized resources with placeholder values in URIs
- - Allow dynamic resource generation based on provided parameters
- - Can represent queries or filtered views of data
- - More flexible but require additional URI formatting
-
-## Examples When Used
-
-- When helping with API development, Kilo Code retrieves endpoint specifications from MCP resources to ensure correct implementation.
-- When assisting with data visualization, Kilo Code accesses current data samples from connected MCP servers.
-- When working in specialized domains, Kilo Code retrieves technical documentation to provide accurate guidance.
-- When generating industry-specific code, Kilo Code references compliance requirements from documentation resources.
-
-## Usage Examples
-
-Accessing current weather data:
-```
-
-
-_OpenRouter dashboard with "Create key" button. Name your key and copy it after creation._
-
-##### Requesty
-
-1. Go to [requesty.ai](https://requesty.ai/)
-2. Sign in with your Google account or email
-3. Navigate to the [API management page](https://app.requesty.ai/manage-api) and create a new key
-4. **Important:** Copy your API key immediately as it won't be displayed again
-
-
-
-_Requesty API management page with "Create API Key" button. Copy your key immediately - it's shown only once._
-
-#### Option 2: Direct Providers
-
-For direct access to specific models from their original providers, with full access to their features and capabilities:
-
-##### Anthropic
-
-1. Go to [console.anthropic.com](https://console.anthropic.com/)
-2. Sign up for an account or log in
-3. Navigate to the [API keys section](https://console.anthropic.com/settings/keys) and create a new key
-4. **Important:** Copy your API key immediately as it won't be displayed again
-
-
-
-_Anthropic console API Keys section with "Create key" button. Name your key, set expiration, and copy it immediately._
-
-##### OpenAI
-
-1. Go to [platform.openai.com](https://platform.openai.com/)
-2. Sign up for an account or log in
-3. Navigate to the [API keys section](https://platform.openai.com/api-keys) and create a new key
-4. **Important:** Copy your API key immediately as it won't be displayed again
-
-
-
-_OpenAI platform with "Create new secret key" button. Name your key and copy it immediately after creation._
-
-### Configuring the Provider in Kilo Code
-
-Once you have your API key:
-
-1. Open the Kilo Code sidebar by clicking the Kilo Code icon () in the VS Code Side Bar
-2. In the welcome screen, select your API provider from the dropdown
-3. Paste your API key into the appropriate field
-4. Select your model:
- - For **OpenRouter**: select `anthropic/claude-3.7-sonnet` ([model details](https://openrouter.ai/anthropic/claude-3.7-sonnet))
- - For **Anthropic**: select `claude-3-7-sonnet-20250219` ([model details](https://www.anthropic.com/pricing#anthropic-api))
-5. Click "Let's go!" to save your settings and start using Kilo Code
diff --git a/packages/kilo-docs/docs/getting-started/installing.md b/packages/kilo-docs/docs/getting-started/installing.md
deleted file mode 100644
index 07415f158fb..00000000000
--- a/packages/kilo-docs/docs/getting-started/installing.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-sidebar_label: Installing Kilo Code
----
-
-# Installing Kilo Code
-
-Kilo Code is a VS Code extension that brings AI-powered coding assistance directly to your editor. Install using one of these methods:
-- [**VS Code Marketplace (Recommended)**](#vs-code-marketplace) - fastest method for standard VS Code users
-- [**Cursor Marketplace**](#cursor-marketplace) - recommended way for Cursor users
-- [**Open VSX Registry**](#open-vsx-registry) - for VS Code-compatible editors like VSCodium or Windsurf
-- [**Manually install the .vsix file**](#manual-installation-from-vsix) - direct installation from the GitHub Release
-
-## VS Code Marketplace
-
-:::tip
-
-If you already have VS Code installed: [Click here to install Kilo Code](vscode:extension/kilocode.Kilo-Code)
-
-:::
-
-alternatively, you can:
-
-1. Open VS Code
-2. Access Extensions: Click the Extensions icon in the Side Bar or press `Ctrl+Shift+X` (Windows/Linux) or `Cmd+Shift+X` (macOS)
-3. Search for "Kilo Code"
-4. Select "Kilo Code" by Kilo Code and click **Install**
-5. Reload VS Code if prompted
-
-After installation, find the Kilo Code icon () in the Side Bar to open the Kilo Code panel.
-
-
-*VS Code marketplace with Kilo Code extension ready to install*
-
-## Cursor Marketplace
-
-:::tip
-
-If you already have Cursor installed: [Click here to install Kilo Code](cursor:extension/kilocode.Kilo-Code)
-
-:::
-
-alternatively, you can:
-
-1. Open Cursor
-2. Access Extensions: Click the Extensions icon in the Side Bar or press `Ctrl+Shift+X` (Windows/Linux) or `Cmd+Shift+X` (macOS)
-3. Search for "Kilo Code"
-4. Select "Kilo Code" by Kilo Code and click **Install**
-5. Reload Cursor if prompted
-
-After installation, find the Kilo Code icon () in the Side Bar to open the Kilo Code panel.
-
-
-
-## Open VSX Registry
-
-[Open VSX Registry](https://open-vsx.org/) is an open-source alternative to the VS Code Marketplace for VS Code-compatible editors that cannot access the official marketplace due to licensing restrictions.
-
-For VS Code-compatible editors like VSCodium, Gitpod, Eclipse Theia, and Windsurf, you can browse and install directly from the [Kilo Code page on Open VSX Registry](https://open-vsx.org/extension/kilocode/Kilo-Code).
-
-1. Open your editor
-2. Access the Extensions view (Side Bar icon or `Ctrl+Shift+X` / `Cmd+Shift+X`)
-3. Your editor should be pre-configured to use Open VSX Registry
-4. Search for "Kilo Code"
-5. Select "Kilo Code" and click **Install**
-6. Reload the editor if prompted
-
-:::note
-If your editor isn't automatically configured for Open VSX Registry, you may need to set it as your extension marketplace in settings. Consult your specific editor's documentation for instructions.
-:::
-
-## Manual Installation from VSIX
-
-If you prefer to download and install the VSIX file directly:
-
-1. **Download the VSIX file:**
- * Find official releases on the [Kilo Code GitHub Releases page](https://github.com/Kilo-Org/kilocode/releases)
- * Download the `.vsix` file from the [latest release](https://github.com/Kilo-Org/kilocode/releases/latest)
-
-2. **Install in VS Code:**
- * Open VS Code
- * Access Extensions view
- * Click the "..." menu in the Extensions view
- * Select "Install from VSIX..."
- * Browse to and select your downloaded `.vsix` file
-
-
-*Installing Kilo Code using VS Code's "Install from VSIX" dialog*
-
-## Troubleshooting
-
-**Extension Not Visible**
-* Restart VS Code
-* Verify Kilo Code is listed and enabled in Extensions
-* Try disabling and re-enabling the extension in Extensions
-* Check Output panel for errors (View → Output, select "Kilo Code")
-
-**Installation Problems**
-* Ensure stable internet connection
-* Verify VS Code version 1.84.0 or later
-* If VS Code Marketplace is inaccessible, try the Open VSX Registry method
-
-## Getting Support
-
-If you encounter issues not covered here:
-
-* Join our [Discord community](https://kilocode.ai/discord) for real-time support
-* Submit issues on [GitHub](https://github.com/Kilo-Org/kilocode/issues)
-* Visit our [Reddit community](https://www.reddit.com/r/KiloCode)
diff --git a/packages/kilo-docs/docs/getting-started/setting-up.mdx b/packages/kilo-docs/docs/getting-started/setting-up.mdx
deleted file mode 100644
index 42de7ca5921..00000000000
--- a/packages/kilo-docs/docs/getting-started/setting-up.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
----
-sidebar_label: Getting Set up
----
-
-import { DISCORD_URL } from "@site/src/constants.ts"
-import useDocusaurusContext from "@docusaurus/useDocusaurusContext"
-
-# Setting up Kilo Code
-
-When you sign up for Kilo Code, you can start immediately with free models, or [purchase Kilo credits](../basic-usage/adding-credits) and receive bonus credits.
-
-To claim your bonus credits:
-
-1. **Sign up:** Complete the registration process
-2. **First top-up:** [Add credits to your account](https://app.kilo.ai/profile) and get $20 bonus credits, or sign up for [Kilo Pass](https://kilo.ai/features/kilo-pass).
-3. **Start Coding:** Enjoy your $20 in free credits
-
-## Registration process
-
-Kilo Code provides a simple registration process that gives you access to the latest frontier coding models with your Kilo Code login.
-
-1. Click on "Try Kilo Code for Free" in the extension
-1. Sign in with your Google account to kilo.ai
-1. kilo.ai will prompt you to open Visual Studio Code
- - When using an IDE in a web browser, you will be asked to copy the API key manually instead
-1. Once you allow it to Open VS Code, you must also allow VS Code to open the authorization URL
-
-
-
-That's it - you're all set! Now you can start with [your first task](/getting-started/your-first-task)
-
-## Already have a subscription to another AI provider?
-
-If you subscribe to ChatGPT, use the [OpenAI ChatGPT provider](../providers/openai-chatgpt-plus-pro) to utilize your subscription with Kilo Code.
-
-You can also [bring your own key](../basic-usage/byok) to use your account or subscription for other providers, including: Anthropic, OpenAI, Mistral, Z.AI, and Minimax.
-
-:::tip Need Help?
-If you have any questions about pricing or tokens, please reach out to our [support team](mailto:hi@kilo.ai) or ask in our Discord community.
-:::
diff --git a/packages/kilo-docs/docs/getting-started/your-first-task.md b/packages/kilo-docs/docs/getting-started/your-first-task.md
deleted file mode 100644
index 2fdc496fd94..00000000000
--- a/packages/kilo-docs/docs/getting-started/your-first-task.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-sidebar_label: Your First Task
----
-
-# Starting Your First Task with Kilo Code
-
-) in the VS Code Primary Side Bar (vertical bar on the side of the window) to open the chat interface. If you don't see the icon, verify the extension is [installed](/getting-started/installing) and enabled.
-
-
-
-_The Kilo Code icon in the Primary Side Bar opens the chat interface._
-
-## Step 2: Type Your Task
-
-Type a clear, concise description of what you want Kilo Code to do in the chat box at the bottom of the panel. Examples of effective tasks:
-
-- "Create a file named `hello.txt` containing 'Hello, world!'."
-- "Write a Python function that adds two numbers."
-- "Create an HTML file for a simple website with the title 'Kilo test'"
-
-No special commands or syntax needed—just use plain English.
-
-
-
-
-💡 Optional: Try Autocomplete
- -While chat is great for complex tasks, Kilo Code also offers **inline autocomplete** for quick code suggestions. Open any code file, start typing, and watch for ghost text suggestions. Press `Tab` to accept. [Learn more about Autocomplete →](/basic-usage/autocomplete) - -
-*Enter your task in natural language - no special syntax required.*
-
-## Step 3: Send Your Task
-
-Press Enter or click the Send icon (
-*Kilo Code shows exactly what action it wants to perform and waits for your approval.*
-
-- In **Code** mode, writing capabilities are on by default.
-- In **Architect** and **Ask** modes, Kilo Code won't write code.
-
-:::tip
-
-The level of autonomy is configurable, allowing you to make the agent more or less autonomous.
-
-You can learn more about [using modes](/basic-usage/using-modes) and [auto-approving actions](/features/auto-approving-actions).
-
-:::
-
-## Step 5: Iterate
-
-Kilo Code works iteratively. After each action, it waits for your feedback before proposing the next step. Continue this review-approve cycle until your task is complete.
-
-
-*After completing the task, Kilo Code shows the final result and awaits your next instruction.*
-
-## Conclusion
-
-You've completed your first task. Along the way you learned:
-
-- How to interact with Kilo Code using natural language
-- Why approval keeps you in control
-- How iteration lets the AI refine its work
-
-Ready for more? Here are some next steps:
-
-- **[Autocomplete](/basic-usage/autocomplete)** — Get inline code suggestions as you type
-- **[Modes](/basic-usage/using-modes)** — Explore different modes for different tasks
-- **[Auto-approval](/features/auto-approving-actions)** — Speed up repetitive tasks
diff --git a/packages/kilo-docs/docs/index.mdx b/packages/kilo-docs/docs/index.mdx
deleted file mode 100644
index 5d8661842c1..00000000000
--- a/packages/kilo-docs/docs/index.mdx
+++ /dev/null
@@ -1,108 +0,0 @@
----
-sidebar_label: Welcome
----
-
-import {
- DISCORD_URL,
- REDDIT_URL,
- GITHUB_ISSUES_MAIN_URL,
- GITHUB_FEATURES_URL,
- YOUTUBE_URL,
-} from "@site/src/constants.ts"
-import Image from "@site/src/components/Image"
-
-# Kilo Code Documentation
-
-Kilo Code **accelerates** development with AI-driven code generation and task automation. This open source extension plugs directly into VS Code.
-
-## What Can Kilo Code Do?
-
-- 🚀 **Generate Code** from natural language descriptions
-- 🔧 **Refactor & Debug** existing code
-- 📝 **Write & Update** documentation
-- 🤔 **Answer Questions** about your codebase
-- 🔄 **Automate** repetitive tasks
-- 🏗️ **Create** new files and projects
-- ⚡ **Autocomplete** code as you type with AI-powered suggestions
-
-## Quick Start
-
-1. [Install Kilo Code](/getting-started/installing)
-2. [Set up Kilo Code](/getting-started/setting-up)
-3. [Try Your First Task](/getting-started/your-first-task)
-4. [Enable Autocomplete](/basic-usage/autocomplete) for inline code suggestions
-
-## Features
-
-
-
-_This animation shows the complete process of enabling JCEF in Android Studio._
-
-### IntelliJ IDEA
-
-JCEF should be enabled by default in IntelliJ IDEA. If you see JCEF warnings:
-
-1. **Update IntelliJ IDEA:**
-
- - Ensure you're running the latest version
- - Go to Help → Check for Updates
-
-2. **Verify JetBrains Runtime:**
-
- - IntelliJ IDEA should use JetBrains Runtime (JBR) by default
- - JBR includes JCEF support
-
-3. **Check Advanced Settings:**
- - Go to File → Settings (Windows/Linux) or IntelliJ IDEA → Preferences (macOS)
- - Navigate to Advanced Settings
- - Look for any JCEF-related options and ensure they're enabled
-
-### Other JetBrains IDEs
-
-For WebStorm, PyCharm, PhpStorm, RubyMine, CLion, GoLand, DataGrip, and Rider:
-
-1. **Update to Latest Version:**
-
- - Most JCEF issues are resolved in recent versions
- - Use the built-in updater: Help → Check for Updates
-
-2. **Verify JetBrains Runtime:**
-
- - These IDEs should use JetBrains Runtime by default
- - JBR includes comprehensive JCEF support
-
-3. **Check Settings:**
- - Go to File → Settings (Windows/Linux) or [IDE Name] → Preferences (macOS)
- - Navigate to Advanced Settings
- - Enable any JCEF-related options
-
-_For general Kilo Code support and documentation, visit [kilocode.ai/docs](https://kilocode.ai/docs)_
diff --git a/packages/kilo-docs/docs/move-to-secondary.png b/packages/kilo-docs/docs/move-to-secondary.png
deleted file mode 100644
index 9347e5804b4..00000000000
Binary files a/packages/kilo-docs/docs/move-to-secondary.png and /dev/null differ
diff --git a/packages/kilo-docs/docs/providers/anthropic.md b/packages/kilo-docs/docs/providers/anthropic.md
deleted file mode 100644
index 40c7bf1aa19..00000000000
--- a/packages/kilo-docs/docs/providers/anthropic.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-sidebar_label: Anthropic
----
-
-# Using Anthropic With Kilo Code
-
-Anthropic is an AI safety and research company that builds reliable, interpretable, and steerable AI systems. Their Claude models are known for their strong reasoning abilities, helpfulness, and honesty.
-
-**Website:** [https://www.anthropic.com/](https://www.anthropic.com/)
-
-## Getting an API Key
-
-1. **Sign Up/Sign In:** Go to the [Anthropic Console](https://console.anthropic.com/). Create an account or sign in.
-2. **Navigate to API Keys:** Go to the [API keys](https://console.anthropic.com/settings/keys) section.
-3. **Create a Key:** Click "Create Key". Give your key a descriptive name (e.g., "Kilo Code").
-4. **Copy the Key:** **Important:** Copy the API key *immediately*. You will not be able to see it again. Store it securely.
-
-## Supported Models
-
-Kilo Code supports the following Anthropic Claude models:
-
-* `claude-3-7-sonnet-20250219` (Recommended)
-* `claude-3-7-sonnet-20250219:thinking` (Extended Thinking variant)
-* `claude-3-5-sonnet-20241022`
-* `claude-3-5-haiku-20241022`
-* `claude-3-opus-20240229`
-* `claude-3-haiku-20240307`
-
-See [Anthropic's Model Documentation](https://docs.anthropic.com/en/docs/about-claude/models) for more details on each model's capabilities.
-
-## Configuration in Kilo Code
-
-1. **Open Kilo Code Settings:** Click the gear icon (
-
-## Supported Models
-
-Currently, v0 offers the following model:
-
-* `v0-1.0-md` - v0's multimodal model that supports both text and image inputs
-* `v0-1.5-lg` - composite model ([learn more](https://vercel.com/blog/v0-composite-model-family))
-* `v0-1.5.md` - composite model ([learn more](https://vercel.com/blog/v0-composite-model-family))
-
-## Troubleshooting
-
-* **"Invalid API Key":** Double-check that you've entered the API key correctly.
-* **"Model Not Found":** Make sure you're using the correct model ID (`v0-1.0-md`).
-* **Connection Errors:** Verify the Base URL is correct (`https://api.v0.dev/v1`).
-* **Access Issues:** Confirm that your Vercel v0 team account is active and properly set up.
-
-## Additional Resources
-
-* [v0 Official Documentation](https://v0.dev)
-* [Vercel AI Documentation](https://vercel.com/docs/ai)
\ No newline at end of file
diff --git a/packages/kilo-docs/docs/providers/vertex.md b/packages/kilo-docs/docs/providers/vertex.md
deleted file mode 100644
index 77c96dbe627..00000000000
--- a/packages/kilo-docs/docs/providers/vertex.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-sidebar_label: GCP Vertex AI
----
-
-# Using GCP Vertex AI With Kilo Code
-
-Kilo Code supports accessing models through Google Cloud Platform's Vertex AI, a managed machine learning platform that provides access to various foundation models, including Anthropic's Claude family.
-
-**Website:** [https://cloud.google.com/vertex-ai](https://cloud.google.com/vertex-ai)
-
-## Prerequisites
-
-* **Google Cloud Account:** You need an active Google Cloud Platform (GCP) account.
-* **Project:** You need a GCP project with the Vertex AI API enabled.
-* **Model Access:** You must request and be granted access to the specific Claude models on Vertex AI you want to use. See the [Google Cloud documentation](https://cloud.google.com/vertex-ai/generative-ai/docs/partner-models/use-claude#before_you_begin) for instructions.
-* **Application Default Credentials (ADC):** Kilo Code uses Application Default Credentials to authenticate with Vertex AI. The easiest way to set this up is to:
- 1. Install the Google Cloud CLI: [https://cloud.google.com/sdk/docs/install](https://cloud.google.com/sdk/docs/install)
- 2. Authenticate using: `gcloud auth application-default login`
-* **Service Account Key (Alternative):** Alternatively, you can authenticate using a Google Cloud Service Account key file. You'll need to generate this key in your GCP project. See the [Google Cloud documentation on creating service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys).
-
-## Supported Models
-
-Kilo Code supports the following models through Vertex AI (based on source code):
-
-* **Google Gemini Models:**
- * `gemini-2.5-flash-preview-05-20`
- * `gemini-2.0-flash-001`
- * `gemini-2.5-pro-exp-03-25`
- * `gemini-2.0-pro-exp-02-05`
- * `gemini-2.0-flash-lite-001`
- * `gemini-2.0-flash-thinking-exp-01-21`
- * `gemini-1.5-flash-002`
- * `gemini-1.5-pro-002`
-* **Anthropic Claude Models:**
- * `claude-opus-4@20250514:thinking`
- * `claude-opus-4@20250514`
- * `claude-sonnet-4@20250514:thinking`
- * `claude-sonnet-4@20250514`
- * `claude-3-7-sonnet@20250219:thinking`
- * `claude-3-7-sonnet@20250219`
- * `claude-3-5-sonnet-v2@20241022`
- * `claude-3-5-sonnet@20240620`
- * `claude-3-5-haiku@20241022`
- * `claude-3-opus@20240229`
- * `claude-3-haiku@20240307`
-
-Refer to the [Google Cloud documentation on Vertex AI Models](https://cloud.google.com/vertex-ai/generative-ai/docs/learn/models) for the most up-to-date list of available models and their IDs.
-
-## Configuration in Kilo Code
-
-1. **Open Kilo Code Settings:** Click the gear icon (
-1. **打开提示标签：** 点击 Kilo Code 顶部菜单栏中的
- * **打开标签：** 点击 Kilo Code 顶部菜单栏中的 
-
-创建和管理规则的最简单方法是通过内置 UI：
-
-1. 从 Kilo Code 面板访问规则管理界面
-2. 选择创建项目特定规则或全局规则
-3. 使用界面创建、编辑或切换规则
-4. 规则会自动保存并立即应用
-
-### 使用文件系统
-
-手动创建规则：
-
-**对于项目规则：**
-
-1. 如果不存在，请创建 `.kilocode/rules/` 目录
-2. 在此目录中创建一个具有描述性名称的新 Markdown 文件
-3. 使用 Markdown 格式编写你的规则
-4. 保存文件
-
-**对于全局规则：**
-
-1. 如果 `~/.kilocode/rules/` 目录尚不存在，则创建它
-2. 在此目录中创建一个新的 Markdown 文件，并带有描述性名称
-3. 使用 Markdown 格式编写您的规则
-4. 保存文件
-
-该规则将自动应用于你项目中所有未来的 Kilo Code 交互。任何新更改都会立即生效。
-
-## 规则示例
-
-### 示例 1：表格格式化
-
-```markdown
-# 表格
-
-打印表格时，始终在每列标题中添加感叹号
-```
-
-这个简单的规则指示 AI 在生成表格时在所有列标题中添加感叹号。
-
-### 示例 2：限制文件访问
-
-```markdown
-# 受限文件
-
-列表中包含敏感数据的文件，禁止读取
-
-- supersecrets.txt
-- credentials.json
-- .env
-```
-
-此规则防止 AI 读取或访问敏感文件，即使明确要求这样做。
-
-
-
-## 使用场景
-
-自定义规则可以应用于各种场景：
-
-- **代码风格**：强制执行一致的格式、命名约定和文档风格
-- **安全控制**：防止访问敏感文件或目录
-- **项目结构**：定义不同类型文件的创建位置
-- **文档要求**：指定文档格式和要求
-- **测试模式**：定义测试的结构方式
-- **API 使用**：指定 API 的使用和文档方式
-- **错误处理**：定义错误处理约定
-
-## 自定义规则示例
-
-- "严格遵守代码风格指南 [你的项目特定代码风格指南]"
-- "始终使用空格缩进，宽度为 4 个空格"
-- "使用 camelCase 命名变量"
-- "为所有新函数编写单元测试"
-- "在提供代码之前解释你的推理"
-- "专注于代码的可读性和可维护性"
-- "优先使用社区中最常见的库"
-- "当为网站添加新功能时，确保它们是响应式且可访问的"
-
-## 最佳实践
-
-- **具体明确**：明确定义每个规则的范围和意图
-- **使用类别**：将相关规则组织在共同的标题下
-- **分离关注点**：为不同类型的规则使用不同的文件
-- **使用示例**：包含示例以说明预期行为
-- **保持简单**：规则应简洁易懂
-- **定期更新**：随着项目需求的变化，定期审查和更新规则
-
-:::tip 专业提示：基于文件的团队标准
-在团队环境中工作时，将 `.kilocode/rules/codestyle.md` 文件置于版本控制之下，可以让你在整个开发团队中标准化 Kilo 的行为。这确保了项目中的每个人都有一致的代码风格、文档实践和开发工作流程。
-:::
-
-## 限制
-
-- 规则由 AI 模型尽力应用
-- 复杂规则可能需要多个示例才能清晰理解
-- 项目规则仅适用于定义它们的项目
-- 全局规则适用于所有项目
-
-## 故障排除
-
-如果你的自定义规则未被正确遵循：
-
-1. 检查你的规则是否使用清晰的 Markdown 结构正确格式化
-2. 确保你的规则位于以下支持的位置之一：
- - 推荐的 `.kilocode/rules/` 目录
- - 根级规则文件（`.kilocoderules`, `.roorules`, 或 `.clinerules`）
-3. 验证规则是否具体且明确
-4. 重启 VS Code 以确保规则正确加载
-
-## 相关功能
-
-- [自定义模式](/features/custom-modes)
-- [自定义指令](/advanced-usage/custom-instructions)
-- [设置管理](/features/settings-management)
-- [自动批准设置](/features/auto-approving-actions)
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/free-and-budget-models.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/free-and-budget-models.md
deleted file mode 100644
index 6f5b0beb101..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/free-and-budget-models.md
+++ /dev/null
@@ -1,283 +0,0 @@
----
-sidebar_label: 免费和预算模型
----
-
-# 免费和低成本使用 Kilo Code
-
-**为什么这很重要：** 在开发过程中，AI 模型成本可能会迅速累积。本指南展示了如何通过免费模型、经济实惠的替代方案和智能使用策略，在最小化或消除成本的同时有效使用 Kilo Code。
-
-## 完全免费的选项
-
-### Grok Code Fast 1
-
-这款前沿 AI 模型在 Kilo Code 中限时 100% 免费。[查看博客文章了解更多信息](https://blog.kilo.ai/p/grok-code-fast-get-this-frontier-ai-model-free)。
-
-### OpenRouter 免费层级模型
-
-OpenRouter 免费提供了几种具有慷慨额度的模型。**注意：** 你需要创建一个免费的 OpenRouter 账户才能访问这些模型。
-
-**设置：**
-
-1. 创建一个免费的 [OpenRouter 账户](https://openrouter.ai)
-2. 从仪表板获取你的 API 密钥
-3. 使用 OpenRouter 供应商配置 Kilo Code
-
-**可用的免费模型：**
-
-- **Qwen3 Coder (免费)** - 针对代理编码任务进行了优化，如函数调用、工具使用和对仓库的长上下文推理。
-- **Z.AI: GLM 4.5 Air (免费)** - GLM-4.5 系列的轻量级变体，专为以代理为中心的应用程序而构建。
-- **DeepSeek: R1 0528 (免费)** - 性能与 OpenAI o1 相当，但是开源的并且具有完全开放的推理令牌。
-- **MoonshotAI: Kimi K2 (免费)** - 针对代理能力进行了优化，包括高级工具使用、推理和代码合成。
-
-## 性价比高的付费模型
-
-当你需要比免费模型提供更多功能时，这些选项提供了极佳的价值：
-
-### 超低预算冠军（每百万 Tokens 低于 $0.50）
-
-**Mistral Devstral Small**
-
-- **成本：** ~$0.20 每百万输入 Tokens
-- **最佳用途：** 代码生成、调试、重构
-- **性能：** 85% 的高级模型能力，成本仅为 10%
-
-**Llama 4 Maverick**
-
-- **成本：** ~$0.30 每百万输入 Tokens
-- **最佳用途：** 复杂推理、架构规划
-- **性能：** 适用于大多数开发任务
-
-**DeepSeek v3**
-
-- **成本：** ~$0.27 每百万输入 Tokens
-- **最佳用途：** 代码分析、大型代码库理解
-- **性能：** 强大的技术推理能力
-
-### 中等价位模型（每百万 Tokens $0.50-$2.00）
-
-**Qwen3 235B**
-
-- **成本：** ~$1.20 每百万输入 Tokens
-- **最佳用途：** 需要高精度的复杂项目
-- **性能：** 接近高级质量，成本为 40%
-
-## 智能使用策略
-
-### 50% 规则
-
-**原则：** 将预算模型用于 50% 的任务，将高级模型用于另外 50% 的任务。
-
-**预算模型任务：**
-
-- 代码审查和分析
-- 文档编写
-- 简单的错误修复
-- 样板代码生成
-- 重构现有代码
-
-**高级模型任务：**
-
-- 复杂的架构决策
-- 调试困难的问题
-- 性能优化
-- 新功能设计
-- 关键生产代码
-
-### 成本节约的上下文管理
-
-**最小化上下文大小：**
-
-```typescript
-// 而不是提及整个文件
-@src/components/UserProfile.tsx
-
-// 提及特定函数或部分
-@src/components/UserProfile.tsx:45-67
-```
-
-**有效使用记忆库：**
-
-- 在 [Memory bank](/advanced-usage/memory-bank) 中存储一次项目上下文
-- 减少重复解释项目细节的需要
-- 每次对话节省 200-500 个 Tokens
-
-**战略性文件提及：**
-
-- 仅包含与任务直接相关的文件
-- 使用 [`@folder/`](/basic-usage/context-mentions) 获取广泛上下文，使用特定文件进行针对性工作
-
-### 模型切换策略
-
-**从便宜开始，需要时升级：**
-
-1. **从免费模型开始**（Qwen3 Coder, GLM-4.5-Air）
-2. **如果免费模型难以胜任，则切换到预算模型**
-3. **仅对复杂任务升级到高级模型**
-
-**使用 API 配置档案：**
-
-- 为不同成本层级设置 [多个配置](/features/api-configuration-profiles)
-- 在免费、预算和高级模型之间快速切换
-- 根据任务复杂性匹配模型能力
-
-### 基于模式的成本优化
-
-**使用适当的模式来限制昂贵的操作：**
-
-- **[询问模式](/basic-usage/using-modes#问答模式)：** 信息收集，无需代码更改
-- **[架构师模式](/basic-usage/using-modes#架构师模式)：** 规划，无需昂贵的文件操作
-- **[调试模式](/basic-usage/using-modes#调试模式)：** 专注的故障排除
-
-**用于预算控制的自定义模式：**
-
-- 创建限制昂贵工具的模式
-- 限制对特定目录的文件访问
-- 控制哪些操作是自动批准的
-
-## 现实世界的性能比较
-
-### 代码生成任务
-
-**简单函数创建：**
-
-- **Mistral Devstral Small：** 95% 成功率
-- **GPT-4：** 98% 成功率
-- **成本差异：** 免费 vs $0.20 vs $30 每百万令牌
-
-**复杂重构：**
-
-- **预算模型：** 70-80% 成功率
-- **高级模型：** 90-95% 成功率
-- **建议：** 从预算开始，需要时再升级
-
-### 调试性能
-
-**简单错误：**
-
-- **免费模型：** 通常足够
-- **预算模型：** 表现优秀
-- **高级模型：** 对于大多数情况来说过于强大
-
-**复杂系统问题：**
-
-- **免费模型：** 40-60% 成功率
-- **预算模型：** 60-80% 成功率
-- **高级模型：** 85-95% 成功率
-
-## 混合方法建议
-
-### 日常开发工作流程
-
-**早晨规划会议：**
-
-- 使用 **架构师模式** 配合 **DeepSeek R1**
-- 规划特性和架构
-- 创建任务分解
-
-**实施阶段：**
-
-- 使用 **代码模式** 配合 **预算模型**
-- 生成和修改代码
-- 处理日常开发任务
-
-**复杂问题解决：**
-
-- 当遇到困难时切换到 **高级模型**
-- 用于关键调试
-- 影响多个系统的架构决策
-
-### 项目阶段策略
-
-**早期开发：**
-
-- 免费和预算模型用于原型制作
-- 快速迭代，无需担心成本
-- 建立模式和结构
-
-**生产准备：**
-
-- 高级模型用于关键代码审查
-- 性能优化
-- 安全考虑
-
-## 成本监控和控制
-
-### 跟踪你的使用情况
-
-**监控令牌消耗：**
-
-- 查看聊天历史中的成本估算
-- 审查每月使用模式
-- 识别高成本操作
-
-**设置支出限额：**
-
-- 使用提供商账单警报
-- 配置 [速率限制](/advanced-usage/rate-limits-costs) 来控制使用
-- 设置每日/每月预算
-
-### 节约成本的技巧
-
-**减少系统提示大小：**
-
-- 如果不使用外部工具，则 [禁用 MCP](/features/mcp/using-mcp-in-kilo-code)
-- 使用专注的自定义模式
-- 最小化不必要的上下文
-
-**优化对话长度：**
-
-- 使用 [检查点](/features/checkpoints) 重置上下文
-- 为无关任务开始新的对话
-- 归档已完成的工作
-
-**批量处理相似任务：**
-
-- 分组相关的代码更改
-- 在单个请求中处理多个文件
-- 减少对话开销
-
-## 开始使用预算模型
-
-### 快速设置指南
-
-1. **创建 OpenRouter 账户** 以获取免费模型
-2. **在 Kilo Code 中配置多个提供商**
-3. **设置 API 配置档案** 以便轻松切换
-4. **在需要时升级到预算模型**
-5. **为复杂工作预留高级模型**
-
-### 推荐的提供商组合
-
-**免费层用于基础：**
-
-- [OpenRouter](/providers/openrouter) - 免费模型
-- [Groq](/providers/groq) - 支持模型的快速推理
-- [Z.ai](https://z.ai/model-api) - 提供免费模型 GLM-4.5-Flash
-
-**预算层用于选则：**
-
-- [DeepSeek](/providers/deepseek) - 性价比极高的模型
-- [Mistral](/providers/mistral) - 专业的编码模型
-
-**高级层用于备份：**
-
-- [Anthropic](/providers/anthropic) - Claude 用于复杂推理
-- [OpenAI](/providers/openai) - GPT-4 用于关键任务
-
-## 衡量是否成功
-
-**跟踪这些指标：**
-
-- 每月 AI 成本 vs 开发生产力
-- 按模型层级的任务完成率
-- 节省的时间 vs 花费的钱
-- 代码质量改进
-
-**成功指标：**
-
-- 70%+ 的任务使用免费/预算模型完成
-- 每月成本在你的目标预算内
-- 保持或提高代码质量
-- 更快的开发周期
-
-通过结合免费模型、战略性预算模型使用和智能优化技术，你可以在保持最低成本的同时充分利用 AI 辅助开发的强大功能。从免费选项开始，随着你的需求和对成本的适应程度逐渐增加预算模型。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/large-projects.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/large-projects.md
deleted file mode 100644
index 17c1b7135b5..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/large-projects.md
+++ /dev/null
@@ -1,46 +0,0 @@
-# 处理大型项目
-
-Kilo Code 可以用于任何规模的项目，但处理大型项目时需要特别注意上下文管理。以下是一些处理大型代码库的技巧：
-
-## 理解上下文限制
-
-Kilo Code 使用的大语言模型 (LLMs) 有一个有限的 "上下文窗口"。这是模型一次可以处理的文本的最大量（以 token 为单位）。如果上下文过大，模型可能无法理解你的请求或生成准确的响应。
-
-上下文窗口包括：
-
-* 系统提示（Kilo Code 的指令）。
-* 对话历史记录。
-* 你使用 `@` 提到的任何文件内容。
-* Kilo Code 使用的任何命令或工具的输出。
-
-## 管理上下文的策略
-
-1. **具体化：** 当引用文件或代码时，使用具体的文件路径和函数名称。避免使用模糊的引用，如 "主文件"。
-
-2. **有效使用上下文提及：** 使用 `@/path/to/file.ts` 来包含特定文件。使用 `@problems` 来包含当前错误和警告。使用 `@` 后跟提交哈希来引用特定的 Git 提交。
-
-3. **分解任务：** 将大型任务分解为更小、更易管理的子任务。这有助于保持上下文的聚焦。
-
-4. **总结：** 如果需要引用大量代码，考虑在提示中总结相关部分，而不是包含整个代码。
-
-5. **优先处理最近的历史记录：** Kilo Code 会自动截断对话历史记录中的旧消息，以保持在上下文窗口内。请注意这一点，并在需要时重新包含重要上下文。
-
-6. **使用提示缓存（如果可用）：** 一些 API 提供商如 Anthropic、OpenAI、OpenRouter 和 Requesty 支持 "提示缓存"。这将缓存你的提示以供未来任务使用，有助于降低请求的成本和延迟。
-
-## 示例：重构大型文件
-
-假设你需要重构一个大型 TypeScript 文件 (`src/components/MyComponent.tsx`)。以下是一个可能的方法：
-
-1. **初始概览：**
- ```
- @/src/components/MyComponent.tsx 列出此文件中的函数和类。
- ```
-
-2. **定位特定函数：**
- ```
- @/src/components/MyComponent.tsx 将 `processData` 函数重构为使用 `async/await` 而不是 Promises。
- ```
-
-3. **迭代更改：** 进行小的、增量的更改，审查并批准每一步。
-
-通过分解任务并提供具体的上下文，即使在上下文窗口有限的情况下，你也可以有效地处理大型文件。
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/local-models.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/local-models.md
deleted file mode 100644
index 5321bb1cce0..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/local-models.md
+++ /dev/null
@@ -1,38 +0,0 @@
-# 使用本地模型
-
-Kilo Code 支持使用 [Ollama](https://ollama.com/) 和 [LM Studio](https://lmstudio.ai/) 在本地计算机上运行语言模型。这提供了以下优势：
-
-* **隐私性**：你的代码和数据永远不会离开你的计算机。
-* **离线访问**：即使没有互联网连接，你也可以使用 Kilo Code。
-* **成本节约**：避免与云端模型相关的 API 使用费用。
-* **定制性**：可以尝试不同的模型和配置。
-
-**然而，使用本地模型也有一些缺点：**
-
-* **资源需求**：本地模型可能对资源要求较高，需要一台性能强大的计算机，最好配备专用 GPU。
-* **设置复杂性**：设置本地模型可能比使用云端 API 更复杂。
-* **模型性能**：本地模型的性能可能差异较大。虽然有些模型表现优秀，但可能无法与最大、最先进的云端模型相媲美。
-* **功能限制**：本地模型（以及许多在线模型）通常不支持高级功能，例如提示缓存、计算机使用等。
-
-## 支持的本地模型提供商
-
-Kilo Code 目前支持两个主要的本地模型提供商：
-
-1. **Ollama**：一个流行的开源工具，用于在本地运行大型语言模型。它支持多种模型。
-2. **LM Studio**：一个用户友好的桌面应用程序，简化了下载、配置和运行本地模型的过程。它还提供了一个模拟 OpenAI API 的本地服务器。
-
-## 设置本地模型
-
-有关详细设置说明，请参阅：
-* [设置 Ollama](/providers/ollama)
-* [设置 LM Studio](/providers/lmstudio)
-
-这两个提供商提供类似的功能，但用户界面和工作流程不同。Ollama 通过命令行界面提供更多控制，而 LM Studio 提供了一个更友好的图形界面。
-
-## 故障排除
-
-* **“由于目标计算机主动拒绝，无法建立连接”**：这通常意味着 Ollama 或 LM Studio 服务器未运行，或者 Kilo Code 配置的端口/地址与服务器不一致。请仔细检查 Base URL 设置。
-
-* **响应时间慢**：本地模型可能比云端模型慢，尤其是在硬件性能较低的情况下。如果遇到性能问题，请尝试使用较小的模型。
-
-* **找不到模型**：请确保你正确输入了模型名称。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/memory-bank.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/memory-bank.md
deleted file mode 100644
index 6a1d220d32f..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/advanced-usage/memory-bank.md
+++ /dev/null
@@ -1,297 +0,0 @@
-# Memory Bank
-
-## 概述
-
-
-
-
-*上下文提及概览，显示聊天界面中的 @ 符号下拉菜单。*
-
-## 提及类型
-
-
-
-*文件提及将实际代码内容添加到对话中，以便直接引用和分析。*
-
-| 提及类型 | 格式 | 描述 | 示例用法 |
-|--------------|--------|-------------|--------------|
-| **文件** | `@/path/to/file.ts` | 将文件内容包含在请求上下文中 | "解释 @/src/utils.ts 中的函数" |
-| **文件夹** | `@/path/to/folder/` | 以树状格式提供目录结构 | "@/src/components/ 中有哪些文件？" |
-| **问题** | `@problems` | 包含 VS Code 问题面板的诊断信息 | "@problems 修复我代码中的所有错误" |
-| **终端** | `@terminal` | 包含最近的终端命令和输出 | "修复 @terminal 中显示的错误" |
-| **Git 提交** | `@a1b2c3d` | 通过哈希引用特定提交 | "提交 @a1b2c3d 中有什么变化？" |
-| **Git 更改** | `@git-changes` | 显示未提交的更改 | "为 @git-changes 建议一条提交消息" |
-| **URL** | `@https://example.com` | 导入网站内容 | "总结 @https://docusaurus.io/" |
-
-### 文件提及
-
-
-
-*文件提及结合行号引用源代码，以便精确定位。*
-
-| 功能 | 详情 |
-|----------|---------|
-| **格式** | `@/path/to/file.ts`（始终从工作区根目录开始使用 `/`） |
-| **提供** | 包含行号的完整文件内容 |
-| **支持** | 文本文件、PDF 和 DOCX 文件（带文本提取） |
-| **适用场景** | 初始请求、反馈响应和后续消息 |
-| **限制** | 非常大的文件可能会被截断；不支持二进制文件 |
-
-### 文件夹提及
-
-
-
-*文件夹提及以可读的树状格式显示目录结构。*
-
-| 功能 | 详情 |
-|------------|---------|
-| **格式** | `@/path/to/folder/`（注意尾部的斜杠） |
-| **提供** | 使用 ├── 和 └── 前缀的分层树状显示 |
-| **包含** | 直接子文件和目录（非递归） |
-| **最佳用途** | 了解项目结构 |
-| **提示** | 结合文件提及检查特定文件内容 |
-
-### 问题提及
-
-
-
-*问题提及直接从 VS Code 的问题面板导入诊断信息。*
-
-| 功能 | 详情 |
-|------------|---------|
-| **格式** | `@problems` |
-| **提供** | VS Code 问题面板中的所有错误和警告 |
-| **包含** | 文件路径、行号和诊断信息 |
-| **分组** | 问题按文件组织以提高清晰度 |
-| **最佳用途** | 修复错误而无需手动复制 |
-
-### 终端提及
-
-
-*终端提及捕获最近的命令输出以便调试和分析。*
-
-| 功能 | 详情 |
-|------------|---------|
-| **格式** | `@terminal` |
-| **捕获** | 最后一条命令及其完整输出 |
-| **保留** | 终端状态（不会清除终端） |
-| **限制** | 仅限于可见的终端缓冲区内容 |
-| **最佳用途** | 调试构建错误或分析命令输出 |
-
-### Git 提及
-
-
-
-*Git 提及提供提交详情和差异，以便进行上下文感知的版本分析。*
-
-| 类型 | 格式 | 提供 | 限制 |
-|------|--------|----------|------------|
-| **提交** | `@a1b2c3d` | 提交消息、作者、日期和完整差异 | 仅适用于 Git 仓库 |
-| **工作区更改** | `@git-changes` | `git status` 输出和未提交更改的差异 | 仅适用于 Git 仓库 |
-
-### URL 提及
-
-
-*URL 提及导入外部网页内容并将其转换为可读的 Markdown 格式。*
-
-| 功能 | 详情 |
-|------------|---------|
-| **格式** | `@https://example.com` |
-| **处理** | 使用无头浏览器获取内容 |
-| **清理** | 移除脚本、样式和导航元素 |
-| **输出** | 将内容转换为 Markdown 以提高可读性 |
-| **限制** | 复杂页面可能无法完美转换 |
-
-## 如何使用提及
-
-1. 在聊天输入框中输入 `@` 以触发建议下拉菜单
-2. 继续输入以过滤建议，或使用箭头键导航
-3. 按回车键或鼠标点击选择
-4. 在请求中组合多个提及："修复 @/src/component.ts 中的 @problems"
-
-下拉菜单会自动建议：
-- 最近打开的文件
-- 可见的文件夹
-- 最近的 Git 提交
-- 特殊关键字（`problems`、`terminal`、`git-changes`）
-
-## 最佳实践
-
-| 实践 | 描述 |
-|----------|-------------|
-| **使用具体路径** | 引用确切文件而非描述它们 |
-| **使用相对路径** | 始终从工作区根目录开始：`@/src/file.ts` 而非 `@C:/Projects/src/file.ts` |
-| **验证引用** | 确保路径和提交哈希正确 |
-| **点击提及** | 点击聊天历史中的提及以打开文件或查看内容 |
-| **避免复制粘贴** | 使用提及而非手动复制代码或错误信息 |
-| **组合提及** | "使用提交 @a1b2c3d 中的模式修复 @/src/component.ts 中的 @problems" |
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/basic-usage/git-commit-generation.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/basic-usage/git-commit-generation.md
deleted file mode 100644
index e3a4919034f..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/basic-usage/git-commit-generation.md
+++ /dev/null
@@ -1,146 +0,0 @@
-# 生成提交消息
-
-根据您暂存的 git 更改自动生成描述性提交消息。Kilo Code 会分析您暂存的文件并创建遵循最佳实践的约定式提交消息。
-
-:::info
-此功能仅分析**暂存的更改**。在生成提交消息之前，请务必使用 `git add` 或通过 `VS Code` 界面暂存您的文件。
-:::
-
-## 工作原理
-
-git 提交消息生成器：
-- 仅分析您的**暂存更改**（未暂存或未跟踪的文件）
-- 使用 AI 理解更改的上下文和目的
-- 创建描述性提交消息，解释更改了什么以及为什么遵循[约定式提交](https://www.conventionalcommits.org/)（默认情况下，可自定义）
-
-## 使用功能
-
-### 生成提交消息
-
-1. 使用 `git add` 或 VS Code git 界面暂存您的更改
-2. 在 VS Code 源代码管理面板中，查找提交消息字段旁边的 `Kilo Code` 徽标)
-3. 单击徽标以生成提交消息
-
-
-生成的邮件将出现在提交消息字段中，您可以根据需要进行审查和修改。
-
-
-
-### 约定式提交格式
-
-默认情况下，生成的邮件遵循约定式提交规范：
-
-```
-
-
-默认模板创建约定式提交消息，但您可以修改它以：
-- 使用不同的提交消息格式
-- 包含与您的项目相关的特定信息
-- 遵循您团队的提交消息约定
-- 为 AI 添加自定义指令
-
-### API 配置
-
-您可以配置用于提交消息生成的 API 配置文件：
-
-1. 在 `Prompts` 设置中，滚动到“API 配置”
-2. 选择特定配置文件或使用当前选定的配置文件
-
-:::tip
-考虑创建一个专用的 [API 配置配置文件](/features/api-configuration-profiles)，其中包含更快、更具成本效益的模型，专门用于提交消息生成。
-:::
-
-## 最佳实践
-
-### 暂存策略
-- 将相关更改一起暂存，以获得更连贯的提交消息
-- 避免在单个提交中暂存不相关的更改
-- 需要时使用 `git add -p` 进行部分文件暂存
-
-### 消息审查
-- 始终在提交前审查生成的邮件
-- 编辑邮件以添加 AI 可能遗漏的上下文
-- 确保邮件准确描述更改
-
-### 自定义模板
-- 根据您的项目需求定制提示模板
-- 包含项目特定的术语或约定
-- 添加处理特定类型更改的说明
-
-## 生成的示例消息
-
-以下是该功能可能生成的消息示例：
-
-```
-feat(auth): add OAuth2 integration with Google
-
-Implement Google OAuth2 authentication flow including:
-- OAuth2 client configuration
-- User profile retrieval
-- Token refresh mechanism
-```
-
-```
-fix(api): resolve race condition in user data fetching
-
-Add proper error handling and retry logic to prevent
-concurrent requests from causing data inconsistency
-```
-
-```
-docs(readme): update installation instructions
-
-Add missing dependency requirements and clarify
-setup steps for new contributors
-```
-
-## 故障排除
-
-### 没有暂存的更改
-如果按钮未出现或生成失败，请确保您已暂存更改：
-```bash
-git add
-
-*工具审批界面显示保存/拒绝按钮和自动批准选项。*
-
-**用户：** 创建一个名为 `greeting.js` 的文件，用于输出问候消息
-
-**Kilo Code：** (建议使用 `write_to_file` 工具，如上图所示)
-```xml
-
-
-## 如何触发待办事项列表
-
-**自动触发**：
-
-- 包含多个步骤的复杂任务
-- 在 Architect 模式下工作
-- 具有依赖关系的多阶段工作流
-
-**手动触发**：
-
-- 要求 Kilo“使用 [update_todo_list 工具](/features/tools/update-todo-list)”
-- 说“创建待办事项列表”
-
-**关键点**：Kilo 决定列表中包含什么，但您可以在批准对话框中提供反馈。
-
----
-
-## 旧方式与新方式
-
-**以前**：您在脑海中记住任务步骤或用零散的笔记记录，不断思考“下一步是什么？”
-
-**现在**：Kilo 创建结构化清单，随着工作的进展自动更新。您清楚地知道自己所处的位置以及接下来要做什么。
-
----
-
-## 待办事项列表出现的位置
-
-**1. 任务头部摘要**
-快速进度概览，显示您的下一个重要事项
-
-
-
-**2. 交互式工具区域**
-聊天中的完整待办事项界面，您可以在其中：
-
-- 查看所有项目及其状态
-- 当 Kilo 请求批准时编辑描述
-- 使用“编辑”按钮暂存更改
-
-**3. 环境详细信息**
-后台“提醒”表，让 Kilo 了解当前进度
-
-## 任务状态解读
-
-**待处理** → 空复选框（未开始）
-
-
-
----
-
-**进行中** → 黄点（当前正在处理）
-
-
-
----
-
-**已完成** → 绿勾（已完成）
-
-
-
----
-
-## 常见问题
-
-**“可以创建自己的待办事项列表吗？”**
-是的，只需要求 Kilo 使用 update_todo_list 工具。但 Kilo 仍控制内容和工作流。
-
-**“简单的任务怎么办？”**
-Kilo 通常会跳过简单任务的待办事项列表。开销不值得。
-
-**“为什么不能直接编辑列表？”**
-设计选择。Kilo 保持对任务管理的主导权，以确保一致的进度跟踪。您提供输入，Kilo 执行。
-
----
-
-:::tip
-
-## 专业提示：自动批准
-
-**作用**：自动批准待办事项列表更新，无需确认提示。
-
-**何时使用**：在长时间工作流中，频繁的中断会拖慢您的进度。
-
-**如何启用**：检查[更新待办事项列表自动批准设置](/features/auto-approving-actions#更新待办事项列表)。
-
-**缺点**：控制较少，但执行速度更快。
-
-:::
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/basic-usage/the-chat-interface.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/basic-usage/the-chat-interface.md
deleted file mode 100644
index e1615f0b169..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/basic-usage/the-chat-interface.md
+++ /dev/null
@@ -1,83 +0,0 @@
-import Image from '@site/src/components/Image';
-
-# 与 Kilo Code 聊天
-
-:::tip
-
-**总结：** Kilo Code 是一个 AI 编码助手，它存在于 VS Code 中。您可以用简单的英语与它聊天，它会为您编写、编辑和解释代码。
-
-:::
-
-## 快速设置
-
-在 VS Code 的主侧边栏中找到 Kilo Code 图标（）。单击它以打开聊天面板。
-
-**找不到面板？** 转到“视图”>“打开视图...”并搜索“Kilo Code”
-
-## 如何与 Kilo Code 对话
-
-**关键见解：** 只需用普通英语输入您想要的内容。无需特殊命令。
-
-
-
-2. **斜杠命令**：在聊天输入框中输入 `/architect`、`/ask`、`/debug` 或 `/code`
-
- 
-
-3. **切换命令/键盘快捷键**：使用适用于你操作系统的键盘快捷键。每次按下都会按顺序循环切换可用模式，到达末尾后返回第一个模式。
-
- | 操作系统 | 快捷键 |
- |----------|--------|
- | macOS | ⌘ + . |
- | Windows | Ctrl + . |
- | Linux | Ctrl + . |
-
-4. **接受建议**：在适当时点击 Kilo Code 提供的模式切换建议
-
- 
-
-## 内置模式
-
-### 代码模式（默认）
-
-| 方面 | 详细信息 |
-|------|----------|
-| **描述** | 一位熟练的软件工程师，精通编程语言、设计模式和最佳实践 |
-| **工具访问** | 完全访问所有工具组：`read`、`edit`、`browser`、`command`、`mcp` |
-| **适合场景** | 编写代码、实现功能、调试和一般开发 |
-| **特殊功能** | 无工具限制——所有编码任务完全灵活 |
-
-### 问答模式
-
-| 方面 | 详细信息 |
-|------|----------|
-| **描述** | 一位知识渊博的技术助手，专注于回答问题而不修改代码库 |
-| **工具访问** | 有限访问：仅 `read`、`browser`、`mcp`（无法编辑文件或运行命令） |
-| **适合场景** | 代码解释、概念探索和技术学习 |
-| **特殊功能** | 优化为在不修改项目的情况下提供信息丰富的响应 |
-
-### 架构师模式
-
-| 方面 | 详细信息 |
-|------|----------|
-| **描述** | 一位经验丰富的技术领导和规划者，帮助设计系统并创建实施计划 |
-| **工具访问** | 访问 `read`、`browser`、`mcp` 和受限的 `edit`（仅限 markdown 文件） |
-| **适合场景** | 系统设计、高层规划和架构讨论 |
-| **特殊功能** | 遵循从信息收集到详细规划的结构化方法 |
-
-### 调试模式
-
-| 方面 | 详细信息 |
-|------|----------|
-| **描述** | 一位擅长系统化故障排除和诊断的专家问题解决者 |
-| **工具访问** | 完全访问所有工具组：`read`、`edit`、`browser`、`command`、`mcp` |
-| **适合场景** | 追踪错误、诊断问题并解决复杂问题 |
-| **特殊功能** | 使用分析、缩小可能性和修复问题的系统化方法 |
-
-### 协调者模式
-
-| 方面 | 详细信息 |
-|------|----------|
-| **描述** | 一位战略工作流协调者，通过将复杂任务委派给适当的专业模式来协调工作 |
-| **工具访问** | 有限的访问权限，用于创建新任务和协调工作流 |
-| **适合场景** | 将复杂项目分解为可管理的子任务，并分配给专业模式 |
-| **特殊功能** | 使用 new_task 工具将工作委派给其他模式 |
-
-## 自定义模式
-
-通过定义工具访问权限、文件权限和行为指令，创建你自己的专业助手。自定义模式有助于执行团队标准或创建特定用途的助手。有关设置说明，请参阅 [自定义模式文档](/features/custom-modes)。
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/extending/contributing-to-kilo.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/extending/contributing-to-kilo.md
deleted file mode 100644
index 6cf6d3a1327..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/extending/contributing-to-kilo.md
+++ /dev/null
@@ -1,134 +0,0 @@
-# 为 Kilo Code 做贡献
-
-Kilo Code 是一个开源项目，欢迎所有技能水平的开发者贡献代码。本指南将帮助你开始为 Kilo Code 做出贡献，无论是修复错误、添加功能、改进文档还是分享自定义模式。
-
-## 贡献方式
-
-有多种方式可以为 Kilo Code 做出贡献：
-
-1. **代码贡献**：实现新功能或修复错误
-2. **文档**：改进现有文档或创建新指南
-3. **市场贡献**：通过 [Kilo Marketplace](https://github.com/Kilo-Org/kilo-marketplace) 创建并分享自定义模式、技能和 MCP 服务器
-4. **错误报告**：报告你遇到的问题
-5. **功能请求**：建议新功能或改进
-6. **社区支持**：在社区中帮助其他用户
-
-## 设置开发环境
-
-设置开发环境的详细说明请参阅[此页面](/extending/development-environment.md)
-
-## 开发工作流
-
-### 分支策略
-
-- 为每个功能或错误修复创建一个新分支
-- 使用描述性的分支名称（例如 `feature/new-tool-support` 或 `fix/browser-action-bug`）
-
-```bash
-git checkout -b your-branch-name
-```
-
-### 编码标准
-
-- 遵循现有的代码风格和模式
-- 新代码使用 TypeScript
-- 为新功能包含适当的测试
-- 更新文档以反映任何面向用户的更改
-
-### 提交指南
-
-- 编写清晰、简洁的提交信息
-- 在适用时引用问题编号
-- 保持每次提交专注于单一更改
-
-### 测试你的更改
-
-- 运行测试套件：
- ```bash
- npm test
- ```
-- 在开发扩展中手动测试你的更改
-
-### 创建拉取请求
-
-1. 将你的更改推送到你的 fork：
-
- ```bash
- git push origin your-branch-name
- ```
-
-2. 前往 [Kilo Code 仓库](https://github.com/Kilo-Org/kilocode)
-
-3. 点击 "New Pull Request" 并选择 "compare across forks"
-
-4. 选择你的 fork 和分支
-
-5. 填写 PR 模板，包括：
- - 更改的清晰描述
- - 任何相关问题
- - 测试步骤
- - 截图（如适用）
-
-## 为 Kilo Marketplace 做贡献
-
-[Kilo Marketplace](https://github.com/Kilo-Org/kilo-marketplace) 是一个社区驱动的代理工具仓库，用于扩展 Kilo Code 的功能。你可以贡献：
-
-- **技能（Skills）**：模块化的工作流程和领域专业知识，教代理如何执行特定任务
-- **MCP 服务器**：标准化的集成，将代理连接到外部工具和服务
-- **模式（Modes）**：具有定制工具访问权限的自定义代理个性和行为
-
-贡献方式：
-
-1. 按照 [自定义模式](/agent-behavior/custom-modes)、[技能](/agent-behavior/skills) 或 [MCP 服务器](/features/mcp/overview) 的文档创建你的资源
-
-2. 彻底测试你的贡献
-
-3. 向 [Kilo Marketplace 仓库](https://github.com/Kilo-Org/kilo-marketplace) 提交拉取请求
-
-## 文档贡献
-
-文档改进是非常有价值的贡献：
-
-1. 遵循文档风格指南：
-
- - 使用清晰、简洁的语言
- - 在适当时包含示例
- - 使用以 `/docs/` 开头的绝对路径作为内部链接
- - 不要在链接中包含 `.md` 扩展名
-
-2. 通过本地运行文档站点测试你的文档更改：
-
- ```bash
- cd docs
- npm install
- npm start
- ```
-
-3. 提交包含文档更改的 PR
-
-## 社区准则
-
-参与 Kilo Code 社区时：
-
-- 保持尊重和包容
-- 提供建设性的反馈
-- 帮助新手入门
-- 遵守 [行为准则](https://github.com/Kilo-Org/kilocode/blob/main/CODE_OF_CONDUCT.md)
-
-## 获取帮助
-
-如果你需要帮助：
-
-- 加入我们的 [Discord 社区](https://kilo.ai/discord) 获取实时支持
-- 在 [GitHub Discussions](https://github.com/Kilo-Org/kilocode/discussions) 上提问
-- 访问我们的 [Reddit 社区](https://www.reddit.com/r/KiloCode)
-
-## 致谢
-
-所有贡献者都是 Kilo Code 社区的重要成员。贡献者将在以下地方获得认可：
-
-- 发布说明
-- 项目的 README
-- GitHub 上的贡献者列表
-
-感谢你为 Kilo Code 做出贡献，帮助让 AI 驱动的编码辅助对每个人更好！
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/extending/development-environment.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/extending/development-environment.md
deleted file mode 100644
index 09f371dbd68..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/extending/development-environment.md
+++ /dev/null
@@ -1,192 +0,0 @@
-# 开发环境
-
-
-
-本文档将帮助你设置开发环境，并了解如何与代码库一起工作。无论你是修复错误、添加功能，还是仅仅探索代码，本指南都将帮助你入门。
-
-## 先决条件
-
-在开始之前，请确保已安装以下内容：
-
-1. **Git** - 用于版本控制
-2. **Node.js**（建议使用 [v20.18.1](https://github.com/Kilo-Org/kilocode/blob/main/.nvmrc) 或更高版本）和 npm
-3. **Visual Studio Code** - 我们推荐的开发 IDE
-
-## 入门
-
-### 安装
-
-1. **Fork 并克隆仓库**：
-
- - **Fork 仓库**：
- - 访问 [Kilo Code GitHub 仓库](https://github.com/Kilo-Org/kilocode)
- - 点击右上角的 "Fork" 按钮，创建你自己的副本。
- - **克隆你的 Fork**：
- ```bash
- git clone https://github.com/[YOUR-USERNAME]/kilocode.git
- cd kilocode
- ```
- 将 `[YOUR-USERNAME]` 替换为你的 GitHub 用户名。
-
-2. **安装依赖项**：
-
- ```bash
- npm run install:all
- ```
-
- 此命令将为主扩展、Webview UI 和 e2e 测试安装依赖项。
-
-3. **安装 VSCode 扩展**：
- - **必需**：[ESBuild Problem Matchers](https://marketplace.visualstudio.com/items?itemName=connor4312.esbuild-problem-matchers) - 帮助正确显示构建错误。
-
-虽然不是运行扩展所必需的，但以下扩展建议用于开发：
-
-- [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) - 将 ESLint 集成到 VS Code 中。
-- [Prettier - Code formatter](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) - 将 Prettier 集成到 VS Code 中。
-
-推荐的扩展完整列表在[这里](https://github.com/Kilo-Org/kilocode/blob/main/.vscode/extensions.json)
-
-### 项目结构
-
-项目组织为以下几个关键目录：
-
-- **`src/`** - 核心扩展代码
- - **`core/`** - 核心功能和工具
- - **`services/`** - 服务实现
-- **`webview-ui/`** - 前端 UI 代码
-- **`e2e/`** - 端到端测试
-- **`scripts/`** - 实用脚本
-- **`assets/`** - 静态资源，如图片和图标
-
-## 开发工作流
-
-### 构建扩展
-
-要构建扩展：
-
-```bash
-npm run build
-```
-
-这将：
-
-1. 构建 Webview UI
-2. 编译 TypeScript
-3. 打包扩展
-4. 在 `bin/` 目录下创建 `.vsix` 文件
-
-### 运行扩展
-
-要在开发模式下运行扩展：
-
-1. 在 VSCode 中按 `F5`（或选择 **Run** → **Start Debugging**）
-2. 这将打开一个新的 VSCode 窗口，并加载 Kilo Code
-
-### 热重载
-
-- **Webview UI 变更**：Webview UI 的变更会立即生效，无需重启
-- **核心扩展变更**：核心扩展代码的变更会自动重新加载扩展主机
-
-在开发模式下（NODE_ENV="development"），更改核心代码将触发 `workbench.action.reloadWindow` 命令，因此不再需要手动启动/停止调试器和任务。
-
-> **重要提示**：在生产构建中，更改核心扩展代码时，你需要：
->
-> 1. 停止调试过程
-> 2. 终止任何在后台运行的 npm 任务（见下图）
-> 3. 重新开始调试
-
-）并在聊天框中输入你的任务。请清晰具体地描述你希望Kilo Code完成的工作。请参阅[输入你的请求](/)获取最佳实践。
-
-### Kilo Code有哪些模式？
-
-[模式](/basic-usage/using-modes)是Kilo Code可以采用的不同的角色，每个角色都有特定的关注点和能力。内置模式包括：
-
-- **Code模式：** 用于通用编码任务
-- **Architect模式：** 用于规划和技术领导
-- **Ask模式：** 用于回答问题并提供信息
-- **Debug模式：** 用于系统化问题诊断
- 你还可以创建[自定义模式](/features/custom-modes)。
-
-### 如何在模式之间切换？
-
-使用聊天输入区域的下拉菜单选择不同的模式，或者使用`/`命令切换到特定模式。
-
-### 什么是工具，如何使用它们？
-
-[工具](/basic-usage/how-tools-work)是Kilo Code与你的系统交互的方式。Kilo Code会自动选择并使用适当的工具来完成你的任务。你不需要直接调用工具。每次使用工具时，你都会被提示批准或拒绝。
-
-### 什么是上下文提及？
-
-[上下文提及](/basic-usage/context-mentions)是一种为Kilo Code提供项目特定信息的方式，例如文件、文件夹或问题。使用"@"符号后跟你想要提及的项目（例如`@/src/file.ts`，`@problems`）。
-
-### Kilo Code可以访问互联网吗？
-
-是的，如果你使用的提供商支持模型进行网页浏览。请注意允许此功能的安全隐患。
-
-### Kilo Code可以在我的终端中运行命令吗？
-
-是的，Kilo Code可以在你的VS Code终端中执行命令。除非你启用了命令的自动批准，否则在执行每个命令之前，你都会被提示批准。在自动批准命令时要格外小心。如果你在终端命令上遇到问题，请参阅[Shell集成指南](/features/shell-integration)进行故障排除。
-
-### 如何向Kilo Code提供反馈？
-
-你可以通过批准或拒绝Kilo Code的提议操作来提供反馈。你还可以使用反馈字段提供额外的反馈。
-
-### 可以自定义Kilo Code的行为吗？
-
-是的，你可以通过多种方式自定义Kilo Code：
-
-- **自定义指令：** 提供适用于所有模式的通用指令，或特定模式的指令
-- **自定义模式：** 创建具有定制提示和工具权限的自定义模式
-- **`.clinerules`文件：** 在项目中创建`.clinerules`文件以提供额外的指导
-- **设置：** 调整各种设置，如自动批准、差异编辑等
-
-### Kilo Code有自动批准设置吗？
-
-是的，Kilo Code有一些设置，启用后会自动批准操作。了解更多[这里](/features/auto-approving-actions)。
-
-## 高级功能
-
-### 可以离线使用Kilo Code吗？
-
-是的，如果你使用[本地模型](/advanced-usage/local-models)。
-
-### 什么是MCP（模型上下文协议）？
-
-[MCP](/features/mcp/overview)是一种协议，允许Kilo Code与外部服务器通信，通过自定义工具和资源扩展其能力。
-
-### 可以创建自己的MCP服务器吗？
-
-是的，你可以创建自己的MCP服务器来为Kilo Code添加自定义功能。详情请参阅[MCP文档](https://github.com/modelcontextprotocol)。
-
-## 故障排除
-
-### Kilo Code没有响应。我该怎么办？
-
-- 确保你的API密钥正确且未过期
-- 检查你的互联网连接
-- 检查你选择的API提供商的状态
-- 尝试重启VS Code
-- 如果问题仍然存在，请在[GitHub](https://github.com/Kilo-Org/kilocode/issues)或[Discord](https://kilocode.ai/discord)上报告问题
-
-### 我看到错误消息。这是什么意思？
-
-错误消息应该会提供一些关于问题的信息。如果你不确定如何解决，请在社区论坛中寻求帮助。
-
-### Kilo Code做了我不想要的更改。如何撤销？
-
-Kilo Code使用VS Code内置的文件编辑功能。你可以使用标准的"撤销"命令（Ctrl/Cmd + Z）来还原更改。此外，如果启用了实验性检查点，Kilo可以还原对文件所做的更改。
-
-### 如何报告bug或建议功能？
-
-请在Kilo Code的[问题页面](https://github.com/Kilo-Org/kilocode/issues)和[功能请求页面](https://github.com/Kilo-Org/kilocode/discussions/categories/ideas)上报告bug或建议功能。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/KiloCodeBrowser.png b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/KiloCodeBrowser.png
deleted file mode 100644
index 9181a877006..00000000000
Binary files a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/KiloCodeBrowser.png and /dev/null differ
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/api-configuration-profiles.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/api-configuration-profiles.md
deleted file mode 100644
index 705b7eb5085..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/api-configuration-profiles.md
+++ /dev/null
@@ -1,106 +0,0 @@
-# API 配置配置文件
-
-API 配置配置文件允许您创建和切换不同的 AI 设置集。每个配置文件可以为每种模式设置不同的配置，让您根据手头的任务优化您的体验。
-
-:::info
-拥有多个配置配置文件可以让您快速切换不同的 AI 提供商、模型和设置，而无需每次更改设置时都重新配置所有内容。
-:::
-
-## 工作原理
-
-配置配置文件可以拥有自己的：
-
-- API 提供商（OpenAI、Anthropic、OpenRouter、Glama 等）
-- API 密钥和身份验证详细信息
-- 模型选择（o3-mini-high、Claude 3.7 Sonnet、DeepSeek R1 等）
-- [温度设置](/features/model-temperature)用于控制响应随机性
-- 思维预算
-- 特定于提供商的设置
-
-请注意，可用设置因提供商和模型而异。每个提供商提供不同的配置选项，即使在同一提供商内，不同的模型也可能支持不同的参数范围或功能。
-
-## 创建和管理配置文件
-
-### 创建配置文件
-
-1. 单击齿轮图标
-
-3. 输入新配置文件的名称
-
-
-
-4. 配置配置文件设置：
-
- - 选择您的 API 提供商
-
-
-
- - 输入 API 密钥
-
-
-
- - 选择模型
-
-
-
- - 调整模型参数
-
-
-
-### 切换配置文件
-
-通过两种方式切换配置文件：
-
-1. 从设置面板：从下拉菜单中选择不同的配置文件
-
-
-
-2. 聊天期间：访问聊天界面中的 API 配置下拉菜单
-
-
-
-### 固定和排序配置文件
-
-API 配置下拉菜单现在支持固定您喜欢的配置文件，以便更快访问：
-
-1. 将鼠标悬停在下拉菜单中的任何配置文件上以显示图钉图标
-2. 单击图钉图标将配置文件添加到您的固定列表
-3. 固定配置文件显示在下拉菜单顶部，按字母顺序排序
-4. 未固定配置文件显示在分隔符下方，也按字母顺序排序
-5. 您可以再次单击同一图标以取消固定配置文件
-
-
-
-此功能使您更容易在常用配置文件之间导航，尤其是在您有许多配置时。
-
-### 编辑和删除配置文件
-
-
-- 在设置中选择配置文件以修改任何设置
-- 单击铅笔图标以重命名配置文件
-- 单击垃圾桶图标以删除配置文件（您不能删除唯一剩余的配置文件）
-
-## 将配置文件链接到模式
-
-在
-
-_提示框和自动批准工具栏显示已启用的权限_
-
-单击工具栏以展开它并配置单个权限：
-
-
-
-_提示文本框和展开的工具栏，包含所有选项_
-
-### 可用权限
-
-| 权限 | 作用 | 风险级别 |
-| -------------------- | ----------------------------------- | -------- |
-| **读取文件和目录** | 允许 Kilo Code 无需询问即可访问文件 | 中 |
-| **编辑文件** | 允许 Kilo Code 无需询问即可修改文件 | **高** |
-| **执行已批准的命令** | 自动运行白名单中的终端命令 | **高** |
-| **使用浏览器** | 允许无头浏览器交互 | 中 |
-| **使用 MCP 服务器** | 允许 Kilo Code 使用配置的 MCP 服务 | 中-高 |
-| **切换模式** | 自动在 Kilo Code 模式之间切换 | 低 |
-| **创建和完成子任务** | 无需确认即可管理子任务 | 低 |
-| **重试失败的请求** | 自动重试失败的 API 请求 | 低 |
-| **回答后续问题** | 为后续问题选择默认答案 | 低 |
-| **更新待办事项列表** | 自动更新任务进度 | 低 |
-
-## 快速控制的主开关
-
-最左侧的复选框作为主开关：
-
-
-
-_主开关（复选框）一次控制所有自动批准权限_
-
-在以下情况下使用主开关：
-
-- 在敏感代码中工作（关闭）
-- 进行快速开发（打开）
-- 在探索和编辑任务之间切换
-
-## 高级设置面板
-
-设置面板提供详细控制和重要的安全上下文：
-
-> **允许 Kilo Code 自动执行操作而无需批准。仅在您完全信任 AI 并了解相关安全风险的情况下才启用这些设置。**
-
-要访问这些设置：
-
-1. 单击右上角的
-
-_完整的设置面板视图_
-
-### 读取操作
-
-:::caution 读取操作
-
-
-**设置：** “始终批准只读操作”
-
-**描述：** “启用后，Kilo Code 将自动查看目录内容并读取文件，无需您单击批准按钮。”
-
-**风险级别：** 中
-
-虽然此设置只允许读取文件（不修改它们），但它可能会暴露敏感数据。对于大多数用户来说，仍然建议将其作为起点，但请注意 Kilo Code 可以访问哪些文件。
-:::
-
-### 写入操作
-
-:::caution 写入操作
-
-
-**设置：** “始终批准写入操作”
-
-**描述：** “自动创建和编辑文件，无需批准”
-
-**延迟滑块：** “写入后延迟以允许诊断检测潜在问题”（默认：1000ms）
-
-**风险级别：** 高
-
-此设置允许 Kilo Code 无需确认即可修改您的文件。延迟计时器至关重要：
-
-- 较高值（2000ms+）：建议用于诊断时间较长的复杂项目
-- 默认值（1000ms）：适用于大多数项目
-- 较低值：仅在速度至关重要且您处于受控环境中时使用
-- 零：诊断无延迟（不建议用于关键代码）
-
-#### 写入延迟和问题窗格集成
-
-
-
-_Kilo Code 在写入延迟期间检查的 VSCode 问题窗格_
-
-当您启用文件写入的自动批准时，延迟计时器与 VSCode 的问题窗格一起工作：
-
-1. Kilo Code 对您的文件进行更改
-2. VSCode 的诊断工具分析更改
-3. 问题窗格更新任何错误或警告
-4. Kilo Code 在继续之前注意到这些问题
-
-这就像人类开发人员在更改代码后暂停检查错误一样。您可以根据以下因素调整延迟时间：
-
-- 项目复杂性
-- 语言服务器速度
-- 错误检测对您的工作流程的重要性
- :::
-
-### 浏览器操作
-
-:::info 浏览器操作
-
-
-**设置：** “始终批准浏览器操作”
-
-**描述：** “自动执行浏览器操作，无需批准”
-
-**注意：** “仅当模型支持计算机使用时才适用”
-
-**风险级别：** 中
-
-允许 Kilo Code 无需确认即可控制无头浏览器。这可以包括：
-
-- 打开网站
-- 导航页面
-- 与网页元素交互
-
-考虑允许自动化浏览器访问的安全隐患。
-:::
-
-### API 请求
-
-:::info API 请求
-
-
-**设置：** “始终重试失败的 API 请求”
-
-**描述：** “当服务器返回错误响应时，自动重试失败的 API 请求”
-
-**延迟滑块：** “重试请求前的延迟”（默认：5s）
-
-**风险级别：** 低
-
-此设置会在 API 调用失败时自动重试。延迟控制 Kilo Code 在重试之前等待多长时间：
-
-- 较长的延迟对 API 速率限制更温和
-- 较短的延迟可以更快地从瞬时错误中恢复
- :::
-
-### MCP 工具
-
-:::caution MCP 工具
-
-
-**设置：** “始终批准 MCP 工具”
-
-**描述：** “在 MCP 服务器视图中启用单个 MCP 工具的自动批准（需要此设置和工具的单独‘始终允许’复选框）”
-
-**风险级别：** 中-高（取决于配置的 MCP 工具）
-
-此设置与 MCP 服务器视图中的单个工具权限结合使用。此全局设置和工具特定权限都必须启用才能进行自动批准。
-:::
-
-### 模式切换
-
-:::info 模式切换
-
-
-**设置：** “始终批准模式切换”
-
-**描述：** “自动在不同模式之间切换，无需批准”
-
-**风险级别：** 低
-
-允许 Kilo Code 在不同模式（代码、架构师等）之间切换，无需请求权限。这主要影响 AI 的行为，而不是系统访问。
-:::
-
-### 子任务
-
-:::info 子任务
-
-
-**设置：** “始终批准子任务的创建和完成”
-
-**描述：** “允许创建和完成子任务，无需批准”
-
-**风险级别：** 低
-
-启用 Kilo Code 自动创建和完成子任务。这与工作流组织有关，而不是系统访问。
-:::
-
-### 命令执行
-
-:::caution 命令执行
-
-
-**设置：** “始终批准允许的执行操作”
-
-**描述：** “自动执行允许的终端命令，无需批准”
-
-**命令管理：** “当启用‘始终批准执行操作’时，可以自动执行的命令前缀。添加 \* 以允许所有命令（谨慎使用）。”
-
-**风险级别：** 高
-
-此设置允许通过控制执行终端命令。虽然有风险，但白名单功能限制了可以运行的命令。重要的安全功能：
-
-- 白名单特定命令前缀（推荐）
-- 切勿在生产环境或敏感数据中使用 \* 通配符
-- 考虑每个允许命令的安全隐患
-- 始终验证与外部系统交互的命令
-
-**界面元素：**
-
-- 文本字段用于输入命令前缀（例如，“git”）
-- “添加”按钮用于添加新前缀
-- 可单击的命令按钮，带 X 可删除它们
- :::
-
-### 后续问题
-
-:::info 后续问题（风险：低）
-
-**设置：** `始终为后续问题提供默认答案`
-
-**描述：** 在可配置的超时后，自动为后续问题选择第一个 AI 建议的答案。这通过让 Kilo Code 无需手动干预即可继续操作来加快您的工作流程。
-
-**视觉倒计时：** 启用后，第一个建议按钮上会出现一个倒计时计时器，显示自动选择前的剩余时间。计时器显示为圆形进度指示器，随着时间推移而耗尽。
-
-**超时滑块：** 使用滑块设置等待时间，从 1 到 300 秒（默认：60 秒）。
-
-**覆盖选项：** 您可以通过以下方式随时取消自动选择：
-
-- 单击不同的建议
-- 编辑任何建议
-- 输入您自己的响应
-- 单击计时器以暂停它
-
-**风险级别：** 低
-
-**用例：**
-
-- 您希望 Kilo Code 继续工作的隔夜运行
-- 默认建议通常正确的重复任务
-- 交互不重要的测试工作流
- :::
-
-### 更新待办事项列表
-
-:::info 更新待办事项列表（风险：低）
-
-**设置：** “始终批准待办事项列表更新”
-
-**描述：** “自动更新待办事项列表，无需批准”
-
-**风险级别：** 低
-
-此设置允许 Kilo Code 在工作会话期间自动更新任务进度和待办事项列表。这包括：
-
-- 将任务标记为已完成
-- 添加新发现的任务
-- 更新任务状态（待处理、进行中、已完成）
-- 重新组织任务优先级
-
-**优点：**
-
-- 保持实时任务进度可见性
-- 减少多步骤工作流中的中断
-- 保持项目状态准确反映
-- 帮助跟踪复杂的任务依赖关系
-
-**用例：**
-
-- 长期开发会话
-- 多步骤重构项目
-- 复杂调试工作流
-- 具有许多子任务的功能实现
-
-当与子任务权限结合使用时，这尤其有用，因为它允许 Kilo Code 在没有持续批准请求的情况下保持项目进度的完整视图。
-:::
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/browser-use.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/browser-use.md
deleted file mode 100644
index 660210cc769..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/browser-use.md
+++ /dev/null
@@ -1,177 +0,0 @@
-# 浏览器使用
-
-Kilo Code 提供复杂的浏览器自动化功能，让您可以直接从 VS Code 与网站交互。此功能支持测试 Web 应用程序、自动化浏览器任务和捕获屏幕截图，而无需离开您的开发环境。
-
-:::info 需要模型支持
-Kilo Code 中的浏览器使用需要使用高级代理模型，并且仅在 Claude Sonnet 3.5、3.7 和 4 上进行过测试。
-:::
-
-## 浏览器使用工作原理
-
-默认情况下，Kilo Code 使用内置浏览器，该浏览器：
-
-- 当您要求 Kilo 访问网站时自动启动
-- 捕获网页屏幕截图
-- 允许 Kilo 与网页元素交互
-- 在后台隐形运行
-
-所有这些都直接在 VS Code 中发生，无需设置。
-
-## 使用浏览器
-
-典型的浏览器交互遵循以下模式：
-
-1. 要求 Kilo 访问网站
-2. Kilo 启动浏览器并向您显示屏幕截图
-3. 请求其他操作（单击、键入、滚动）
-4. 完成后 Kilo 关闭浏览器
-
-例如：
-
-```
-打开浏览器并查看我们的网站。
-```
-
-```
-您能检查一下我的网站 https://kilocode.ai 是否正常显示吗？
-```
-
-```
-浏览 http://localhost:3000，滚动到页面底部并检查页脚信息是否正常显示。
-```
-
-
-
-## 浏览器操作工作原理
-
-`browser_action` 工具控制一个浏览器实例，该实例在每次操作后返回屏幕截图和控制台日志，让您可以看到交互结果。
-
-主要特点：
-
-- 每个浏览器会话必须以 `launch` 开始并以 `close` 结束
-- 每个消息只能使用一个浏览器操作
-- 浏览器处于活动状态时，不能使用其他工具
-- 在执行下一个操作之前，您必须等待响应（屏幕截图和日志）
-
-### 可用的浏览器操作
-
-| 操作 | 描述 | 何时使用 |
-| ------------- | ------------------- | ------------------ |
-| `launch` | 在 URL 处打开浏览器 | 启动新的浏览器会话 |
-| `click` | 在特定坐标处单击 | 与按钮、链接等交互 |
-| `type` | 将文本键入活动元素 | 填写表单、搜索框 |
-| `scroll_down` | 向下滚动一页 | 查看折叠下方的内容 |
-| `scroll_up` | 向上滚动一页 | 返回到以前的内容 |
-| `close` | 关闭浏览器 | 结束浏览器会话 |
-
-## 浏览器使用配置/设置
-
-:::info 默认浏览器设置
-
-- **启用浏览器工具**：已启用
-- **视口大小**：小型桌面 (900x600)
-- **屏幕截图质量**：75%
-- **使用远程浏览器连接**：已禁用
- :::
-
-### 访问设置
-
-要更改 Kilo 中的浏览器/计算机使用设置：
-
-1. 单击齿轮图标 
-
-### 启用/禁用浏览器使用
-
-**目的**：主开关，使 Kilo 能够使用 Puppeteer 控制的浏览器与网站交互。
-
-要更改此设置：
-
-1. 在浏览器/计算机使用设置中选中或取消选中“启用浏览器工具”复选框
-
- 
-
-### 视口大小
-
-**目的**：确定 Kilo Code 使用的浏览器会话的分辨率。
-
-**权衡**：较高的值提供更大的视口，但会增加 token 使用量。
-
-要更改此设置：
-
-1. 单击浏览器/计算机使用设置中“视口大小”下的下拉菜单
-2. 选择可用选项之一：
- - 大型桌面 (1280x800)
- - 小型桌面 (900x600) - 默认
- - 平板电脑 (768x1024)
- - 移动设备 (360x640)
-3. 选择您所需的分辨率。
-
- 
-
-### 屏幕截图质量
-
-**目的**：控制浏览器屏幕截图的 WebP 压缩质量。
-
-**权衡**：较高的值提供更清晰的屏幕截图，但会增加 token 使用量。
-
-要更改此设置：
-
-1. 在浏览器/计算机使用设置中调整“屏幕截图质量”下的滑块
-2. 设置 1-100% 之间的值（默认值为 75%）
-3. 较高的值提供更清晰的屏幕截图，但会增加 token 使用量：
-
- - 40-50%：适用于基本的基于文本的网站
- - 60-70%：适用于大多数通用浏览
- - 80%+：在精细视觉细节至关重要时使用
-
- 
-
-### 远程浏览器连接
-
-**目的**：将 Kilo 连接到现有 Chrome 浏览器，而不是使用内置浏览器。
-
-**优点**：
-
-- 在容器化环境和远程开发工作流中工作
-- 在浏览器使用之间保持经过身份验证的会话
-- 消除重复的登录步骤
-- 允许使用带有特定扩展的自定义浏览器配置文件
-
-**要求**：Chrome 必须运行并启用远程调试。
-
-要启用此功能：
-
-1. 在浏览器/计算机使用设置中选中“使用远程浏览器连接”框
-2. 单击“测试连接”以验证
-
- 
-
-#### 常见用例
-
-- **DevContainers**：从容器化 VS Code 连接到主机 Chrome 浏览器
-- **远程开发**：将本地 Chrome 与远程 VS Code 服务器一起使用
-- **自定义 Chrome 配置文件**：使用带有特定扩展和设置的配置文件
-
-#### 连接到可见的 Chrome 窗口
-
-连接到可见的 Chrome 窗口以实时观察 Kilo 的交互：
-
-**macOS**
-
-```bash
-/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug --no-first-run
-```
-
-**Windows**
-
-```bash
-"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir=C:\chrome-debug --no-first-run
-```
-
-**Linux**
-
-```bash
-google-chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug --no-first-run
-```
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/checkpoints.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/checkpoints.md
deleted file mode 100644
index 15ec8437087..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/checkpoints.md
+++ /dev/null
@@ -1,253 +0,0 @@
-# 检查点
-
-检查点在 Kilo Code 任务期间自动对您的工作区文件进行版本控制，从而实现对 AI 建议的非破坏性探索，并轻松从不需要的更改中恢复。
-
-检查点让您能够：
-
-- 安全地试验 AI 建议的更改
-- 轻松从不需要的修改中恢复
-- 比较不同的实现方法
-- 恢复到以前的项目状态而不会丢失工作
-
-:::info 重要说明
-
-- **检查点默认启用。**
-- **必须安装 Git** 才能使检查点正常工作 - [请参阅安装说明](#git-安装)
-- 无需 GitHub 帐户或仓库
-- 无需 Git 个人信息配置
-- 影子 Git 仓库独立于您项目现有的 Git 配置运行
- :::
-
-## 配置选项
-
-在 Kilo Code 设置的“检查点”部分访问检查点设置：
-
-1. 单击齿轮图标 
-
-## 检查点工作原理
-
-Kilo Code 使用一个影子 Git 仓库（独立于您的主版本控制系统）捕获项目状态的快照。这些快照称为检查点，会在您的 AI 辅助工作流中自动记录更改——无论任务何时开始、文件何时更改或命令何时运行。
-
-检查点作为 Git 提交存储在影子仓库中，捕获：
-
-- 文件内容更改
-- 添加的新文件
-- 删除的文件
-- 重命名文件
-- 二进制文件更改
-
-## 使用检查点
-
-检查点直接通过聊天界面集成到您的工作流中。
-
-检查点以两种形式直接出现在您的聊天历史记录中：
-
-- **初始检查点**标记您的起始项目状态
- 
-
-- **常规检查点**在文件修改或命令执行后出现
- 
-
-每个检查点提供两个主要功能：
-
-### 查看差异
-
-要将当前工作区与以前的检查点进行比较：
-
-1. 在聊天历史记录中找到检查点
-2. 单击检查点的 `View Differences` 按钮
-
- 
-
-3. 在比较视图中查看差异：
- - 添加的行以绿色突出显示
- - 删除的行以红色突出显示
- - 修改的文件列出详细更改
- - 重命名和移动的文件跟踪其路径更改
- - 新建或删除的文件清晰标记
-
-
-
-### 恢复检查点
-
-要将项目恢复到以前的检查点状态：
-
-1. 在聊天历史记录中找到检查点
-2. 单击检查点的 `Restore Checkpoint` 按钮
- 
-3. 选择以下恢复选项之一：
-
- 
-
-- **仅恢复文件** - 仅将工作区文件恢复到检查点状态，而不修改对话历史记录。非常适合在保持聊天上下文的同时比较替代实现，让您可以在不同项目状态之间无缝切换。此选项无需确认，可让您快速在不同实现之间切换。
-
-- **恢复文件和任务** - 恢复工作区文件并删除所有后续对话消息。当您希望将代码和对话完全重置回检查点的时间点时使用。此选项需要在对话框中进行确认，因为它无法撤消。
-
- 
-
-### 限制和注意事项
-
-- **范围**：检查点仅捕获在活动 Kilo Code 任务期间所做的更改
-- **外部更改**：在任务之外进行的修改（手动编辑、其他工具）不包括在内
-- **大文件**：非常大的二进制文件可能会影响性能
-- **未保存的工作**：恢复将覆盖工作区中任何未保存的更改
-
-## 技术实现
-
-### 检查点架构
-
-检查点系统包括：
-
-1. **影子 Git 仓库**：专门为检查点跟踪创建的独立 Git 仓库，作为检查点状态的持久存储机制。
-
-2. **检查点服务**：通过以下方式处理 Git 操作和状态管理：
-
- - 仓库初始化
- - 检查点创建和存储
- - 差异计算
- - 状态恢复
-
-3. **UI 组件**：聊天中显示的界面元素，可实现与检查点的交互。
-
-### 恢复过程
-
-当执行恢复时，Kilo Code：
-
-- 对指定的检查点提交执行硬重置
-- 将所有文件从影子仓库复制到您的工作区
-- 更新内部检查点跟踪状态
-
-### 存储类型
-
-检查点是任务范围的，这意味着它们特定于单个任务。
-
-### 差异计算
-
-检查点比较使用 Git 的底层差异功能生成结构化的文件差异：
-
-- 修改的文件显示逐行更改
-- 正确检测和处理二进制文件
-- 正确跟踪重命名和移动的文件
-- 清晰识别文件创建和删除
-
-### 文件排除和忽略模式
-
-检查点系统使用智能文件排除来仅跟踪相关文件：
-
-#### 内置排除
-
-系统具有全面的内置排除模式，自动忽略：
-
-- 构建工件和依赖项目录（`node_modules/`、`dist/`、`build/`）
-- 媒体文件和二进制资产（图像、视频、音频）
-- 缓存和临时文件（`.cache/`、`.tmp/`、`.bak`）
-- 包含敏感信息的配置文件（`.env`）
-- 大型数据文件（存档、可执行文件、二进制文件）
-- 数据库文件和日志
-
-这些模式在初始化期间写入影子仓库的 `.git/info/exclude` 文件。
-
-#### .gitignore 支持
-
-检查点系统尊重工作区中的 `.gitignore` 模式：
-
-- 被 `.gitignore` 排除的文件不会触发检查点创建
-- 排除的文件不会出现在检查点差异中
-- 暂存文件更改时应用标准 Git 忽略规则
-
-#### .kilocodeignore 行为
-
-`.kilocodeignore` 文件（控制 AI 对文件的访问）与检查点跟踪是分开的：
-
-- 被 `.kilocodeignore` 排除但未被 `.gitignore` 排除的文件仍将被检查点
-- 对 AI 无法访问的文件的更改仍可通过检查点恢复
-
-这种分离是故意的，因为 `.kilocodeignore` 限制了 AI 可以访问的文件，而不是应该跟踪版本历史的文件。
-
-#### 嵌套 Git 仓库
-
-检查点系统包括对嵌套 Git 仓库的特殊处理：
-
-- 在操作期间临时将嵌套的 `.git` 目录重命名为 `.git_disabled`
-- 操作完成后恢复它们
-- 允许正确跟踪嵌套仓库中的文件
-- 确保嵌套仓库保持功能正常且不受影响
-
-### 并发控制
-
-操作排队以防止可能损坏仓库状态的并发 Git 操作。这确保了即使在快速连续请求时，快速检查点操作也能安全完成。
-
-## Git 安装
-
-检查点要求您的系统上安装 Git。该实现使用 `simple-git` 库，该库依赖于 Git 命令行工具来创建和管理影子仓库。
-
-### macOS
-
-1. **使用 Homebrew 安装（推荐）**：
-
- ```
- brew install git
- ```
-
-2. **替代方案：使用 Xcode 命令行工具安装**：
-
- ```
- xcode-select --install
- ```
-
-3. **验证安装**：
- - 打开终端
- - 键入 `git --version`
- - 您应该会看到版本号，例如 `git version 2.40.0`
-
-### Windows
-
-1. **下载适用于 Windows 的 Git**：
-
- - 访问 https://git-scm.com/download/win
- - 下载应自动开始
-
-2. **运行安装程序**：
-
- - 接受许可协议
- - 选择安装位置（推荐默认）
- - 选择组件（默认选项通常足够）
- - 选择默认编辑器
- - 选择如何从命令行使用 Git（推荐：从命令行和第三方软件使用 Git）
- - 配置行尾转换（推荐：Checkout Windows-style, commit Unix-style）
- - 完成安装
-
-3. **验证安装**：
- - 打开命令提示符或 PowerShell
- - 键入 `git --version`
- - 您应该会看到版本号，例如 `git version 2.40.0.windows.1`
-
-### Linux
-
-**Debian/Ubuntu**：
-
-```
-sudo apt update
-sudo apt install git
-```
-
-**Fedora**：
-
-```
-sudo dnf install git
-```
-
-**Arch Linux**：
-
-```
-sudo pacman -S git
-```
-
-**验证安装**：
-
-- 打开终端
-- 键入 `git --version`
-- 您应该会看到版本号
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/code-actions.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/code-actions.md
deleted file mode 100644
index d39556f0f84..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/code-actions.md
+++ /dev/null
@@ -1,90 +0,0 @@
-import Image from '@site/src/components/Image';
-
-# 代码操作
-
-代码操作是 VS Code 的强大功能，它直接在编辑器中提供快速修复、重构和其他与代码相关的建议。Kilo Code 与此系统集成，为常见的编码任务提供 AI 辅助。
-
-## 什么是代码操作？
-
-代码操作在编辑器装订线（行号左侧区域）中显示为灯泡图标（💡）。它们也可以通过右键单击上下文菜单或通过键盘快捷键访问。它们在以下情况下触发：
-
-* 您选择了一段代码。
-* 您的光标位于有问题（错误、警告或提示）的行上。
-* 您通过命令调用它们。
-
-单击灯泡、右键单击并选择“Kilo Code”，或使用键盘快捷键（macOS 上默认为 `Ctrl+.` 或 `Cmd+.`），将显示可用操作菜单。
-
-
-
-## Kilo Code 的代码操作
-
-Kilo Code 提供以下代码操作：
-
-* **添加到上下文：** 快速将选定的代码添加到与 Kilo 的聊天中，包括行号，以便 Kilo 确切知道代码来自何处。它在菜单中排在第一位，以便于访问。（更多详细信息见下文）。
-* **解释代码：** 要求 Kilo Code 解释选定的代码。
-* **修复代码：** 要求 Kilo Code 修复选定代码中的问题（在存在诊断时可用）。
-* **改进代码：** 要求 Kilo Code 建议改进选定的代码。
-
-### 添加到上下文深入探讨
-
-**添加到上下文**操作在代码操作菜单中排在第一位，因此您可以快速将代码片段添加到对话中。当您使用它时，Kilo Code 会将文件名和行号以及代码包含在内。
-
-这有助于 Kilo 理解代码在项目中的确切上下文，从而使其能够提供更相关和准确的帮助。
-
-
-
-**示例聊天输入：**
-
-```
-你能解释一下这个函数吗？
-@myFile.js:15:25
-```
-
-*（其中 `@myFile.js:15:25` 表示通过“添加到上下文”添加的代码）*
-
-这些操作中的每一个都可以在“新任务中”或“当前任务中”执行。
-
-## 使用代码操作
-
-使用 Kilo Code 的代码操作有三种主要方式：
-
-### 1. 从灯泡 (💡)
-
-1. **选择代码：** 选择您要处理的代码。您可以选择单行、多行或整个代码块。
-2. **查找灯泡：** 灯泡图标将出现在选定代码（或带有错误/警告的行）旁边的装订线中。
-3. **单击灯泡：** 单击灯泡图标以打开代码操作菜单。
-4. **选择操作：** 从菜单中选择所需的 Kilo Code 操作。
-5. **审查和批准：** Kilo Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
-
-### 2. 从右键上下文菜单
-
-1. **选择代码：** 选择您要处理的代码。
-2. **右键单击：** 右键单击选定的代码以打开上下文菜单。
-3. **选择“Kilo Code”：** 从上下文菜单中选择“Kilo Code”选项。将出现一个子菜单，其中包含可用的 Kilo Code 操作。
-4. **选择操作：** 从子菜单中选择所需的操作。
-5. **审查和批准：** Kilo Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
-
-### 3. 从命令面板
-
-1. **选择代码：** 选择您要处理的代码。
-2. **打开命令面板：** 按 `Ctrl+Shift+P` (Windows/Linux) 或 `Cmd+Shift+P` (macOS)。
-3. **键入命令：** 键入“Kilo Code”以过滤命令，然后选择相关的代码操作（例如，“Kilo Code: Explain Code”）。您也可以键入命令的开头，例如“Kilo Code: Explain”，然后从过滤列表中选择。
-4. **审查和批准：** Kilo Code 将在聊天面板中提出解决方案。审查提议的更改并批准或拒绝它们。
-
-## 代码操作和当前任务
-
-每个代码操作都为您提供两个选项：
-
-* **在新任务中：** 选择此选项以开始与 Kilo 的对话，围绕此代码操作进行。
-* **在当前任务中：** 如果对话已经开始，此选项将代码操作添加为附加消息。
-
-## 自定义代码操作提示
-
-您可以通过修改“提示”选项卡中的“支持提示”来自定义每个代码操作使用的提示。这允许您微调提供给 AI 模型的指令，并根据您的特定需求调整响应。
-
-1. **打开提示选项卡：** 单击 Kilo Code 顶部菜单栏中的 
-
-## 作用
-
-启用后，索引系统：
-
-1. **使用 Tree-sitter 解析您的代码**以识别语义块（函数、类、方法）
-2. **使用 AI 模型创建每个代码块的嵌入**
-3. **将向量存储在 Qdrant 数据库中**以进行快速相似性搜索
-4. **为 Kilo Code 提供 [`codebase_search`](/advanced-usage/available-tools/codebase-search) 工具**以进行智能代码发现
-
-这使得自然语言查询（如“用户身份验证逻辑”或“数据库连接处理”）能够查找整个项目中的相关代码。
-
-## 主要优点
-
-- **语义搜索**：通过含义查找代码，而不仅仅是关键字
-- **增强 AI 理解**：Kilo Code 可以更好地理解和使用您的代码库
-- **跨项目发现**：搜索所有文件，而不仅仅是打开的文件
-- **模式识别**：查找相似的实现和代码模式
-
-## 设置要求
-
-### 嵌入提供商
-
-选择以下选项之一来生成嵌入：
-
-**OpenAI（推荐）**
-
-- 需要 OpenAI API 密钥
-- 支持所有 OpenAI 嵌入模型
-- 默认：`text-embedding-3-small`
-- 每批处理多达 100,000 个 token
-
-**Gemini**
-
-- 需要 Google AI API 密钥
-- 支持 Gemini 嵌入模型，包括 `gemini-embedding-001`
-- OpenAI 的经济高效替代方案
-- 用于代码理解的高质量嵌入
-
-**Ollama（本地）**
-
-- 需要本地 Ollama 安装
-- 无 API 成本或互联网依赖
-- 支持任何 Ollama 兼容的嵌入模型
-- 需要 Ollama 基本 URL 配置
-
-### 向量数据库
-
-**Qdrant** 是存储和搜索嵌入所必需的：
-
-- **本地**：`http://localhost:6333`（推荐用于测试）
-- **云**：Qdrant Cloud 或自托管实例
-- **身份验证**：安全部署的可选 API 密钥
-
-## 设置 Qdrant
-
-### 快速本地设置
-
-**使用 Docker：**
-
-```bash
-docker run -p 6333:6333 qdrant/qdrant
-```
-
-**使用 Docker Compose：**
-
-```yaml
-version: '3.8'
-services:
- qdrant:
- image: qdrant/qdrant
- ports:
- - '6333:6333'
- volumes:
- - qdrant_storage:/qdrant/storage
-volumes:
- qdrant_storage:
-```
-
-### 生产部署
-
-用于团队或生产：
-
-- [Qdrant Cloud](https://cloud.qdrant.io/) - 托管服务
-- 在 AWS、GCP 或 Azure 上自托管
-- 带有网络访问的本地服务器，用于团队共享
-
-## 配置
-
-1. 打开 Kilo Code 设置（
-
-_Kilo Code 创建和管理自定义模式的界面。_
-
-## 自定义模式包含哪些内容？
-
-自定义模式由几个关键属性定义。理解这些概念将帮助您有效地调整 Kilo 的行为。
-
-| UI 字段 / YAML 属性 | 概念描述 |
-| ------------------------------------- | -------------------------------------------------------------------------------------------------- |
-| **Slug** (`slug`) | 模式的唯一内部标识符。Kilo Code 使用它来引用模式，特别是用于关联特定于模式的指令文件。 |
-| **名称** (`name`) | 在 Kilo Code 用户界面中显示的模式名称。应该是人类可读且具有描述性的。 |
-| **描述** (`description`) | 在模式选择器 UI 中显示的模式目的的简短、用户友好的摘要。保持简洁，并专注于该模式对用户的作用。 |
-| **角色定义** (`roleDefinition`) | 定义模式的核心身份和专业领域。此文本放置在系统提示的开头，并定义 Kilo 在此模式激活时的个性和行为。 |
-| **可用工具** (`groups`) | 定义模式允许的工具集和文件访问权限。对应于选择模式可以使用的工具的一般类别。 |
-| **使用时机** (`whenToUse`) | _(可选)_ 为 Kilo 的自动化决策提供指导，特别是模式选择和任务编排。由协调器模式用于任务协调。 |
-| **自定义指令** (`customInstructions`) | _(可选)_ 模式的特定行为准则或规则。添加在系统提示的末尾附近，以进一步细化 Kilo 的行为。 |
-
-## 导入/导出模式
-
-轻松共享、备份和模板化您的自定义模式。此功能允许您将任何模式及其关联规则导出到单个便携式 YAML 文件中，您可以将其导入到任何项目中。
-
-### 主要功能
-
-- **可共享设置**：将模式及其规则打包到一个文件中，轻松与团队共享
-- **轻松备份**：保存您的自定义模式配置，这样您就不会丢失它们
-- **项目模板**：为不同类型的项目创建标准化模式模板
-- **简单迁移**：在全局设置和特定项目之间轻松移动模式
-- **灵活的 Slug 更改**：在导出的文件中更改模式 slug，无需手动路径编辑
-
-### 工作原理
-
-**导出模式：**
-
-1. 导航到模式视图
-2. 选择您希望导出的模式
-3. 点击导出模式按钮（下载图标）
-4. 选择保存 `.yaml` 文件的位置
-5. Kilo 将模式的配置和任何规则打包到 YAML 文件中
-
-**导入模式：**
-
-1. 在模式视图中点击导入模式按钮（上传图标）
-2. 选择模式的 YAML 文件
-3. 选择导入级别：
- - **项目**：仅在当前工作区中可用（保存到 `.kilocodemodes` 文件）
- - **全局**：在所有项目中可用（保存到全局设置）
-
-### 导入时更改 Slug
-
-导入模式时，您可以在导入之前更改导出的 YAML 文件中的 slug：
-
-1. 导出一个 slug 为 `original-mode` 的模式
-2. 编辑 YAML 文件并将 slug 更改为 `new-mode`
-3. 导入文件 - 导入过程将自动更新规则文件路径以匹配新的 slug
-
-## 创建和配置自定义模式的方法
-
-您可以通过几种方式创建和配置自定义模式：
-
-### 1. 询问 Kilo！（推荐）
-
-您可以通过要求 Kilo Code 为您创建基本的自定义模式来快速创建。例如：
-
-```
-创建一个名为"文档编写者"的新模式。它应该只能读取文件和编写 Markdown 文件。
-```
-
-Kilo Code 将引导您完成此过程，提示必要的信息并使用首选的 YAML 格式创建模式。
-
-### 2. 使用提示标签页
-
-1. **打开提示标签页**：点击 Kilo Code 顶部菜单栏中的 
-
-_自定义模式创建界面，显示名称、slug、描述、保存位置、角色定义、可用工具、自定义指令的字段。_
-
-界面提供名称、Slug、描述、保存位置、角色定义、使用时机（可选）、可用工具和自定义指令的字段。填写这些字段后，点击"创建模式"按钮。Kilo Code 将以 YAML 格式保存新模式。
-
-### 3. 手动配置（YAML 和 JSON）
-
-您可以直接编辑配置文件来创建或修改自定义模式。此方法为您提供对所有属性的最大控制。Kilo Code 现在支持 YAML（首选）和 JSON 格式。
-
-- **全局模式**：编辑 `custom_modes.yaml`（首选）或 `custom_modes.json` 文件。通过提示标签页 >
-
-
-## 如何使用增强提示
-
-1. **输入您的初始提示：** 像往常一样在 Kilo Code 聊天输入框中输入您的请求。这可以是一个简单的问题、一个复杂的任务描述，或介于两者之间的任何内容。
-2. **单击
-
-有关详细演练：https://youtu.be/R1nDnCK-xzw
-
-## 限制和最佳实践
-
-* **实验性功能：** 提示增强是一项实验性功能。增强提示的质量可能因您的请求的复杂性和底层模型的功能而异。
-* **仔细审查：** 在发送之前务必仔细审查增强提示。Kilo Code 可能会进行与您的意图不符的更改。
-* **迭代过程：** 您可以多次使用“增强提示”功能来迭代优化您的提示。
-* **不能替代清晰的指令：** 尽管“增强提示”可以提供帮助，但从一开始就编写清晰具体的提示仍然很重要。
-
-通过使用“增强提示”功能，您可以提高与 Kilo Code 交互的质量，并获得更准确和有用的响应。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/experimental/experimental-features.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/experimental/experimental-features.md
deleted file mode 100644
index fc147a35e5a..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/experimental/experimental-features.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# 实验性功能
-
-Kilo Code 包含一些仍在开发中的实验性功能。这些功能可能不稳定，会在未来版本中发生重大变化，甚至可能被移除。请谨慎使用，并注意它们可能无法按预期工作。
-
-**警告：** 实验性功能可能存在意外行为，包括潜在的数据丢失或安全漏洞。启用这些功能需自行承担风险。
-
-## 启用实验性功能
-
-要启用或禁用实验性功能：
-
-1. 打开 Kilo Code 设置（右上角的 
-1. **更快的文件编辑**：Kilo 通过仅应用必要的更改来更快地修改文件。
-2. **防止截断写入**：系统自动检测并拒绝 AI 写入不完整文件内容的尝试，这可能发生在大型文件或复杂指令中。这有助于防止文件损坏。
-
-:::note 禁用快速编辑
-如果您取消选中“**通过差异启用编辑**”，Kilo 将恢复为使用 [`write_to_file`](/features/tools/write-to-file) 工具为每次编辑写入整个文件内容，而不是使用 [`apply_diff`](/features/tools/apply-diff) 应用有针对性的更改。这种完全写入的方法通常在修改现有文件时速度较慢，并导致更高的 token 使用量。
-:::
-
-## 匹配精度
-
-此滑块控制 AI 识别的代码部分在应用更改之前必须与文件中实际代码匹配的紧密程度。
-
- 
-
-* **100%（默认）**：需要精确匹配。这是最安全的选择，可最大程度地降低错误更改的风险。
-* **较低值（80%-99%）**：允许“模糊”匹配。即使代码部分与 AI 预期有细微差异，Kilo 也可以应用更改。这在文件略有修改时很有用，但**增加了**在错误位置应用更改的风险。
-
-**请极其谨慎地使用低于 100% 的值。** 较低的精度可能偶尔是必要的，但请务必仔细审查提议的更改。
-
-在内部，此设置调整用于比较代码相似性的 `fuzzyMatchThreshold`（例如 Levenshtein 距离）算法。
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/footgun-prompting.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/footgun-prompting.md
deleted file mode 100644
index 31239250070..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/footgun-prompting.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-sidebar_label: "足枪式提示"
----
-
-# 足枪式提示：覆盖系统提示
-
-足枪式提示，又称覆盖系统提示，允许高级用户完全替换特定 Kilo Code 模式的默认系统提示。这提供了对 AI 行为的精细控制，但绕过了内置的安全措施。
-
-:::info **足枪** _(名词)_
-
-1. _(编程俚语，幽默，贬义)_ 任何可能导致程序员自作自受的功能。
-
-> 系统提示覆盖被认为是一种足枪，因为在没有深入理解的情况下修改核心指令可能导致意外或错误的行为，尤其是在工具使用和响应一致性方面。
-
-:::
-
-## 工作原理
-
-1. **覆盖文件：** 在您的工作区根目录中创建一个名为 `.kilocode/system-prompt-{mode-slug}` 的文件（例如，Code 模式的 `.kilocode/system-prompt-code`）。
-2. **内容：** 此文件的内容将成为该特定模式的新系统提示。
-3. **激活：** Kilo Code 会自动检测此文件。如果存在，它将替换大多数标准系统提示部分。
-4. **保留部分：** 只有核心 `roleDefinition` 和您为该模式设置的任何 `customInstructions` 会与您的覆盖内容一起保留。工具描述、规则和功能等标准部分将被绕过。
-5. **构建：** 发送到模型的最终提示如下所示：
-
- ```
- ${roleDefinition}
-
- ${content_of_your_override_file}
-
- ${customInstructions}
- ```
-
-## 访问功能
-
-您可以在 Kilo Code UI 中找到选项和说明：
-
-1. 单击 Kilo Code 文本输入框左下角的 MODE 选择器。
-2. 单击模式选择列表底部的“编辑...”
-3. 展开底部的“**高级：覆盖系统提示**”部分。
-4. 单击说明中的文件路径链接将在 VS Code 中打开或创建当前选定模式的正确覆盖文件。
-
-
-
-## 主要注意事项和警告
-
-- **目标受众：** 最适合深入了解 Kilo Code 提示系统以及修改核心指令所带来影响的用户。
-- **对功能的影响：** 自定义提示会覆盖标准指令，包括工具使用和响应一致性的指令。如果管理不当，这可能导致意外行为或错误。
-- **模式特定：** 每个覆盖文件仅适用于其文件名中指定的模式（`{mode-slug}`）。
-- **无文件，无覆盖：** 如果 `.kilocode/system-prompt-{mode-slug}` 文件不存在，Kilo Code 将使用该模式的标准系统提示生成过程。
-- **目录创建：** Kilo Code 确保 `.kilocode` 目录存在，然后才尝试读取或创建覆盖文件。
-
-请谨慎使用此功能。虽然它在自定义方面功能强大，但错误的实现可能会显著降低 Kilo Code 在受影响模式下的性能和可靠性。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/mcp-vs-api.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/mcp-vs-api.md
deleted file mode 100644
index 0e4934c94db..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/mcp-vs-api.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: MCP与API
-sidebar_label: MCP与API
----
-
-# MCP与REST API：根本区别
-
-将REST API与模型上下文协议（MCP）进行比较是一种类别错误。它们在抽象的不同层次上运行，为AI系统提供根本不同的功能。
-
-## 架构差异
-
-| 特性 | MCP | REST API |
-|---------|-----|-----------|
-| 状态管理 | **有状态** - 在交互中维护上下文 | **无状态** - 每个请求都是独立的 |
-| 连接类型 | 持久、双向连接 | 单向请求/响应 |
-| 通信风格 | 基于JSON-RPC的持续会话 | 基于HTTP的离散请求 |
-| 上下文处理 | 上下文是协议的内在部分 | 上下文必须手动管理 |
-| 工具发现 | 运行时发现可用工具 | 设计时集成，需要预先了解 |
-| 集成方式 | 运行时集成，动态能力 | 设计时集成，需要代码修改 |
-
-## 不同层次，不同目的
-
-REST API和MCP服务于技术栈的不同层次：
-
-1. **REST**：暴露资源操作的低级Web通信模式
-2. **MCP**：编排工具使用和维护上下文的高级AI协议
-
-MCP通常在内部使用REST API，但为AI抽象了它们。可以将MCP视为将离散的Web服务转变为AI可以操作的统一环境的中间件。
-
-## 上下文保存：AI工作流程的关键
-
-MCP的有状态设计解决了REST在AI应用中的关键限制：
-
-- **REST方法**：每个调用都是独立的，需要在步骤间手动传递上下文
-- **MCP方法**：一次对话上下文在多个工具使用中持续存在
-
-例如，AI在调试代码库时可以打开文件、运行测试并识别错误，而不会在各步骤间丢失上下文。MCP会话会保持对先前操作和结果的感知。
-
-## 动态工具发现
-
-MCP使AI能够在运行时发现和使用工具：
-
-```json
-// AI发现可用工具
-{
- "tools": [
- {
- "name": "readFile",
- "description": "从文件中读取内容",
- "parameters": {
- "path": { "type": "string", "description": "文件路径" }
- }
- },
- {
- "name": "createTicket",
- "description": "在问题跟踪器中创建工单",
- "parameters": {
- "title": { "type": "string" },
- "description": { "type": "string" }
- }
- }
- ]
-}
-```
-
-这种"即插即用"能力允许添加新工具而无需重新部署或修改AI本身。
-
-## 实际示例：多工具工作流程
-
-考虑一个需要多个服务的任务："检查最近的提交，为bug修复创建JIRA工单，并发布到Slack。"
-
-**基于REST的方法**：
-- 需要为Git、JIRA和Slack API分别集成
-- 需要自定义代码来管理调用间的上下文
-- 任何服务更改API都会中断
-
-**基于MCP的方法**：
-- 所有工具的统一协议
-- 维护整个工作流程的上下文
-- 新工具可以无缝替换，无需代码修改
-
-## 为什么Kilo Code使用MCP
-
-Kilo Code利用MCP提供：
-
-1. **可扩展性**：添加无限自定义工具，无需等待官方集成
-2. **上下文感知**：工具可以访问对话历史和项目上下文
-3. **简化集成**：一个标准协议，而非多种API模式
-4. **运行时灵活性**：动态发现和使用新功能
-
-MCP在Kilo Code和外部服务之间创建了通用连接器，REST API通常在这些服务背后提供支持。
-
-## 结论：互补而非竞争的技术
-
-MCP并不取代REST API - 它建立在它们之上。REST擅长提供离散服务，而MCP擅长为AI代理编排这些服务。
-
-关键区别在于MCP是AI原生的：它把模型视为一等用户，提供AI代理在复杂环境中有效运行所需的上下文、有状态交互层。
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/overview.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/overview.md
deleted file mode 100644
index f8fc0ab4264..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/overview.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: MCP概览
-sidebar_label: MCP概览
----
-
-# 模型上下文协议（MCP）
-
-模型上下文协议（MCP）是扩展Kilo Code功能的标准化协议，通过连接外部工具和服务来实现。MCP服务器提供了额外的工具和资源，帮助Kilo Code完成超出其内置功能的任务，例如访问数据库、自定义API和特殊功能。
-
-## MCP文档结构
-
-本文档分为以下几个部分：
-
-* [**在Kilo Code中使用MCP**](/features/mcp/using-mcp-in-kilo-code) - 在Kilo Code中配置、启用和管理MCP服务器的综合指南。包括服务器设置、工具批准和故障排除。
-
-* [**什么是MCP？**](/features/mcp/what-is-mcp) - 解释模型上下文协议、其客户端-服务器架构以及如何使AI系统与外部工具交互。
-
-* [**STDIO与SSE传输**](/features/mcp/server-transports) - 详细比较本地（STDIO）和远程（SSE）传输机制，以及每种方法的部署考虑。
-
-* [**MCP与API**](/features/mcp/mcp-vs-api) - 分析MCP与REST API的根本区别，解释它们如何在不同的抽象层为AI系统工作。
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/server-transports.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/server-transports.md
deleted file mode 100644
index d41530619c4..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/server-transports.md
+++ /dev/null
@@ -1,199 +0,0 @@
----
-title: MCP服务器传输机制
-sidebar_label: STDIO与SSE传输
----
-
-# MCP服务器传输机制：STDIO与SSE
-
-模型上下文协议（MCP）支持两种主要的传输机制用于Kilo Code与MCP服务器之间的通信：标准输入/输出（STDIO）和服务器发送事件（SSE）。每种机制都有其独特的特点、优势和适用场景。
-
-## STDIO传输
-
-STDIO传输在本地机器上运行，通过标准输入/输出流进行通信。
-
-### STDIO传输工作原理
-
-1. 客户端（Kilo Code）将MCP服务器作为子进程启动
-2. 通信通过进程流进行：客户端写入服务器的STDIN，服务器响应到STDOUT
-3. 每个消息以换行符分隔
-4. 消息格式为JSON-RPC 2.0
-
-```
-Client Server
- | |
- |---- JSON message ------>| (via STDIN)
- | | (processes request)
- |<---- JSON message ------| (via STDOUT)
- | |
-```
-
-### STDIO特点
-
-- **本地性**：与Kilo Code在同一台机器上运行
-- **性能**：延迟和开销非常低（不涉及网络栈）
-- **简单性**：直接进程通信，无需网络配置
-- **关系**：客户端与服务器之间的一对一关系
-- **安全性**：本质上更安全，因为不暴露网络
-
-### 使用STDIO的场景
-
-STDIO传输适用于：
-
-- 本地集成和工具
-- 安全敏感操作
-- 低延迟要求
-- 单客户端场景（每个服务器一个Kilo Code实例）
-- 命令行工具或IDE扩展
-
-### STDIO实现示例
-
-```typescript
-import { Server } from "@modelcontextprotocol/sdk/server/index.js"
-import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
-
-const server = new Server({ name: "local-server", version: "1.0.0" })
-// 注册工具...
-
-// 使用STDIO传输
-const transport = new StdioServerTransport(server)
-transport.listen()
-```
-
-## SSE传输
-
-服务器发送事件（SSE）传输在远程服务器上运行，通过HTTP/HTTPS进行通信。
-
-### SSE传输工作原理
-
-1. 客户端（Kilo Code）通过HTTP GET请求连接到服务器的SSE端点
-2. 建立持久连接，服务器可以向客户端推送事件
-3. 对于客户端到服务器的通信，客户端向单独的端点发送HTTP POST请求
-4. 通信通过两个通道进行：
- - 事件流（GET）：服务器到客户端更新
- - 消息端点（POST）：客户端到服务器请求
-
-```
-Client Server
- | |
- |---- HTTP GET /events ----------->| (establish SSE connection)
- |<---- SSE event stream -----------| (persistent connection)
- | |
- |---- HTTP POST /message --------->| (client request)
- |<---- SSE event with response ----| (server response)
- | |
-```
-
-### SSE特点
-
-- **远程访问**：可以托管在与Kilo Code不同的机器上
-- **可扩展性**：支持多个客户端并发连接
-- **协议**：基于标准HTTP（无需特殊协议）
-- **持久性**：维护服务器到客户端消息的持久连接
-- **认证**：可以使用标准HTTP认证机制
-
-### 使用SSE的场景
-
-SSE传输更适合：
-
-- 跨网络远程访问
-- 多客户端场景
-- 公共服务
-- 许多用户需要访问的集中式工具
-- 与Web服务集成
-
-### SSE实现示例
-
-```typescript
-import { Server } from "@modelcontextprotocol/sdk/server/index.js"
-import { SSEServerTransport } from "@modelcontextprotocol/sdk/server/sse.js"
-import express from "express"
-
-const app = express()
-const server = new Server({ name: "remote-server", version: "1.0.0" })
-// 注册工具...
-
-// 使用SSE传输
-const transport = new SSEServerTransport(server)
-app.use("/mcp", transport.requestHandler())
-app.listen(3000, () => {
- console.log("MCP server listening on port 3000")
-})
-```
-
-## 本地 vs. 托管：部署考虑
-
-选择STDIO还是SSE传输将直接影响MCP服务器的部署和管理方式。
-
-### STDIO：本地部署模式
-
-STDIO服务器与Kilo Code在同一台机器上运行，这有几个重要影响：
-
-- **安装**：必须在每个用户的机器上安装服务器可执行文件
-- **分发**：需要为不同操作系统提供安装包
-- **更新**：每个实例必须单独更新
-- **资源**：使用本地机器的CPU、内存和磁盘
-- **访问控制**：依赖于本地机器的文件系统权限
-- **集成**：易于与本地系统资源（文件、进程）集成
-- **执行**：随Kilo Code启动和停止（子进程生命周期）
-- **依赖**：任何依赖项都必须安装在用户机器上
-
-#### 实际示例
-
-一个本地文件搜索工具使用STDIO会：
-
-- 在用户机器上运行
-- 直接访问本地文件系统
-- 在Kilo Code需要时启动
-- 不需要网络配置
-- 需要与Kilo Code一起安装或通过包管理器安装
-
-### SSE：托管部署模式
-
-SSE服务器可以部署到远程服务器并通过网络访问：
-
-- **安装**：在服务器上安装一次，供多个用户访问
-- **分发**：单一部署服务多个客户端
-- **更新**：集中更新立即影响所有用户
-- **资源**：使用服务器资源，而非本地机器资源
-- **访问控制**：通过认证和授权系统管理
-- **集成**：与用户特定资源的集成更复杂
-- **执行**：作为独立服务运行（通常持续运行）
-- **依赖**：在服务器上管理，而非用户机器
-
-#### 实际示例
-
-一个数据库查询工具使用SSE会：
-
-- 在中央服务器上运行
-- 使用服务器端凭据连接数据库
-- 持续可用，供多个用户使用
-- 需要正确的网络安全配置
-- 使用容器或云技术部署
-
-### 混合方法
-
-某些场景受益于混合方法：
-
-1. **带网络访问的STDIO**：本地STDIO服务器充当远程服务的代理
-2. **带本地命令的SSE**：远程SSE服务器可以通过回调触发客户端机器上的操作
-3. **网关模式**：本地操作的STDIO服务器连接到专用功能的SSE服务器
-
-## 选择STDIO还是SSE
-
-| 考虑因素 | STDIO | SSE |
-| -------------- | -------------- | ------------------------ |
-| **位置** | 仅限本地机器 | 本地或远程 |
-| **客户端** | 单客户端 | 多客户端 |
-| **性能** | 延迟更低 | 延迟更高（网络开销） |
-| **设置复杂性** | 更简单 | 更复杂（需要HTTP服务器） |
-| **安全性** | 本质上更安全 | 需要明确的安全措施 |
-| **网络访问** | 不需要 | 需要 |
-| **可扩展性** | 限于本地机器 | 可以在网络上分布 |
-| **部署** | 每用户安装 | 集中安装 |
-| **更新** | 分布式更新 | 集中更新 |
-| **资源使用** | 使用客户端资源 | 使用服务器资源 |
-| **依赖** | 客户端依赖 | 服务器依赖 |
-
-## 在Kilo Code中配置传输
-
-有关在Kilo Code中配置STDIO和SSE传输的详细信息，包括示例配置，请参见[理解传输类型](/features/mcp/using-mcp-in-kilo-code#理解传输类型)部分。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/using-mcp-in-kilo-code.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/using-mcp-in-kilo-code.md
deleted file mode 100644
index 66799ccdfd0..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/using-mcp-in-kilo-code.md
+++ /dev/null
@@ -1,225 +0,0 @@
----
-title: 在Kilo Code中使用MCP
-sidebar_label: 在Kilo Code中使用MCP
----
-
-# 在Kilo Code中使用MCP
-
-模型上下文协议（MCP）通过连接外部工具和服务扩展了Kilo Code的功能。本指南涵盖了在Kilo Code中使用MCP所需了解的所有内容。
-
-
-
-两个文件都使用JSON格式，其中包含一个`mcpServers`对象，包含命名的服务器配置：
-
-```json
-{
- "mcpServers": {
- "server1": {
- "command": "python",
- "args": ["/path/to/server.py"],
- "env": {
- "API_KEY": "your_api_key"
- },
- "alwaysAllow": ["tool1", "tool2"],
- "disabled": false
- }
- }
-}
-```
-
-_Kilo Code中的MCP服务器配置示例（STDIO传输）_
-
-### 理解传输类型
-
-MCP支持两种服务器通信的传输类型：
-
-#### STDIO传输
-
-用于在本地机器上运行的服务器：
-
-- 通过标准输入/输出流通信
-- 延迟更低（无网络开销）
-- 安全性更好（无网络暴露）
-- 设置更简单（不需要HTTP服务器）
-- 作为本地机器上的子进程运行
-
-有关STDIO传输工作原理的深入信息，请参见[STDIO传输](/features/mcp/server-transports#stdio传输)。
-
-STDIO配置示例：
-
-```json
-{
- "mcpServers": {
- "local-server": {
- "command": "node",
- "args": ["/path/to/server.js"],
- "env": {
- "API_KEY": "your_api_key"
- },
- "alwaysAllow": ["tool1", "tool2"],
- "disabled": false
- }
- }
-}
-```
-
-#### SSE传输
-
-用于通过HTTP/HTTPS访问的远程服务器：
-
-- 通过服务器发送事件协议通信
-- 可以托管在不同的机器上
-- 支持多个客户端连接
-- 需要网络访问
-- 允许集中部署和管理
-
-有关SSE传输工作原理的深入信息，请参见[SSE传输](/features/mcp/server-transports#sse传输)。
-
-SSE配置示例：
-
-```json
-{
- "mcpServers": {
- "remote-server": {
- "url": "https://your-server-url.com/mcp",
- "headers": {
- "Authorization": "Bearer your-token"
- },
- "alwaysAllow": ["tool3"],
- "disabled": false
- }
- }
-}
-```
-
-### 删除服务器
-
-1. 点击要删除的MCP服务器旁边的
-
-### 重启服务器
-
-1. 点击要重启的MCP服务器旁边的
-
-### 自动批准工具
-
-MCP工具自动批准按工具进行，默认禁用。要配置自动批准：
-
-1. 首先在[自动批准操作](/features/auto-approving-actions)中启用全局"使用MCP服务器"自动批准选项
-2. 在MCP服务器设置中，定位要自动批准的特定工具
-3. 勾选工具名称旁边的`始终允许`复选框
-
-
-
-启用后，Kilo Code将自动批准此特定工具而无需提示。请注意，全局"使用MCP服务器"设置优先 - 如果它被禁用，则不会自动批准任何MCP工具。
-
-## 查找和安装MCP服务器
-
-Kilo Code不附带任何预安装的MCP服务器。你需要单独查找并安装它们。
-
-- **社区仓库**：在GitHub上查看社区维护的MCP服务器列表
-- **询问Kilo Code**：你可以请Kilo Code帮助你查找甚至创建MCP服务器
-- **自行构建**：使用SDK创建自定义MCP服务器，使用你自己的工具扩展Kilo Code
-
-有关完整的SDK文档，请访问[MCP GitHub仓库](https://github.com/modelcontextprotocol/)。
-
-## 在工作流中使用MCP工具
-
-配置MCP服务器后，Kilo Code将自动检测可用的工具和资源。要使用它们：
-
-1. 在Kilo Code聊天界面中输入你的请求
-2. Kilo Code将识别何时MCP工具可以帮助完成任务
-3. 在提示时批准工具使用（或使用自动批准）
-
-示例："分析我的API性能"可能会使用一个测试API端点的MCP工具。
-
-## 故障排除MCP服务器
-
-常见问题及解决方案：
-
-- **服务器无响应**：检查服务器进程是否正在运行并验证网络连接
-- **权限错误**：确保在`mcp_settings.json`（用于全局设置）或`.kilocode/mcp.json`（用于项目设置）中配置了正确的API密钥和凭据。
-- **工具不可用**：确认服务器是否正确实现了该工具且未在设置中禁用
-- **性能缓慢**：尝试调整特定MCP服务器的网络超时值
-
-## 平台特定的MCP配置示例
-
-### Windows配置示例
-
-在Windows上设置MCP服务器时，你需要使用Windows命令提示符（`cmd`）来执行命令。以下是在Windows上配置Puppeteer MCP服务器的示例：
-
-```json
-{
- "mcpServers": {
- "puppeteer": {
- "command": "cmd",
- "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-puppeteer"]
- }
- }
-}
-```
-
-此Windows特定配置：
-
-- 使用`cmd`命令访问Windows命令提示符
-- 使用`/c`告诉cmd执行命令然后终止
-- 使用`npx`运行包而无需永久安装
-- `-y`标志在安装期间自动回答"是"任何提示
-- 运行提供浏览器自动化功能的`@modelcontextprotocol/server-puppeteer`包
-
-:::note
-对于macOS或Linux，你将使用不同的配置：
-
-```json
-{
- "mcpServers": {
- "puppeteer": {
- "command": "npx",
- "args": ["-y", "@modelcontextprotocol/server-puppeteer"]
- }
- }
-}
-```
-
-:::
-
-相同的方法可以用于Windows上的其他MCP服务器，根据需要调整包名称以匹配不同的服务器类型。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/what-is-mcp.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/what-is-mcp.md
deleted file mode 100644
index 0336cd019b6..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/mcp/what-is-mcp.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: 什么是 MCP？
-sidebar_label: 什么是 MCP？
----
-
-# 什么是 MCP？
-
-MCP（Model Context Protocol，模型上下文协议）是 LLM 系统与外部工具和服务交互的标准化通信协议。它充当 AI 助手与各类数据源或应用程序之间的通用适配器。
-
-## 工作原理
-
-MCP 采用客户端-服务端架构：
-
-1. AI 助手（客户端）连接至 MCP 服务器
-2. 每个服务器提供特定能力（文件访问、数据库查询、API 集成等）
-3. AI 通过标准化接口使用这些能力
-4. 通信通过 JSON-RPC 2.0 消息进行
-
-可以将 MCP 类比为 USB-C 接口——任何兼容的 LLM 都能连接任意 MCP 服务器来使用其功能。这种标准化消除了为每个工具和服务构建定制集成的需求。
-
-例如，使用 MCP 的 AI 可以执行"搜索公司数据库并生成报告"这类任务，而无需为每个数据库系统编写专用代码。
-
-## 常见问题
-
-- **MCP 是云服务吗？** MCP 服务器既可在本地运行，也可作为云服务远程部署，具体取决于使用场景和安全要求。
-
-- **MCP 会取代其他集成方式吗？** 不会。MCP 是对 API 插件和检索增强生成等现有工具的补充。它提供了工具交互的标准化协议，但不会取代专业集成方案。
-
-- **如何保障安全性？** 用户可自主控制连接哪些 MCP 服务器，以及授予这些服务器哪些权限。与任何访问数据或服务的工具一样，请使用可信来源并配置适当的访问控制。
-
-## Kilo Code 中的 MCP
-
-Kilo Code 通过实现模型上下文协议来：
-
-- 同时连接本地和远程 MCP 服务器
-- 提供访问工具的统一接口
-- 无需修改核心即可扩展功能
-- 按需启用专项能力
-
-MCP 为 AI 系统与外部工具服务的交互提供了标准化方式，使复杂集成更易用且一致。
-
-## 深入了解 MCP
-
-准备好深入探索了吗？请查阅以下指南：
-
-- [MCP 概述](/features/mcp/overview) - 快速了解 MCP 文档结构
-- [在 Kilo Code 中使用 MCP](/features/mcp/using-mcp-in-kilo-code) - 包含创建简单服务器的入门指导
-- [MCP vs 传统 API](/features/mcp/mcp-vs-api) - 相比传统 API 的技术优势
-- [STDIO 与 SSE 传输协议](/features/mcp/server-transports) - 本地与云端部署模式对比
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/model-temperature.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/model-temperature.md
deleted file mode 100644
index 701e7901951..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/model-temperature.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# 模型温度
-
-温度控制 AI 模型输出的随机性。调整此设置可优化不同任务的结果——从精确的代码生成到创意头脑风暴。温度是控制 AI 行为最强大的参数之一。精心调整的温度设置可以显著提高特定任务响应的质量和适用性。
-
-
-
-## 什么是温度？
-
-温度是一个设置（通常在 0.0 到 2.0 之间），用于控制 AI 输出的随机性或可预测性。找到正确的平衡是关键：较低的值使输出更集中和一致，而较高的值则鼓励更多的创造性和多样性。对于许多编码任务，中等温度（约 0.3 到 0.7）通常效果很好，但最佳设置取决于您要实现的目标。
-
-:::info 温度和代码：常见误解
-温度控制输出随机性，而不是直接控制代码质量或准确性。关键点：
-
-- **低温度（接近 0.0）：** 生成可预测、一致的代码。适用于简单任务，但可能重复且缺乏创造力。它不能保证*更好*的代码。
-- **高温度：** 增加随机性，可能导致创造性解决方案，但也可能导致更多错误或无意义的代码。它不能保证*更高质量*的代码。
-- **准确性：** 代码准确性取决于模型的训练和提示清晰度，而不是温度。
-- **温度 0.0：** 有助于一致性，但限制了复杂问题所需的探索。
- :::
-
-## Kilo Code 中的默认值
-
-Kilo Code 对大多数模型使用 0.0 的默认温度，以优化代码生成的最大确定性和精度。这适用于 OpenAI 模型、Anthropic 模型（非思考变体）、LM Studio 模型和大多数其他提供商。
-
-某些模型使用较高的默认温度——DeepSeek R1 模型和某些以推理为重点的模型默认为 0.6，在确定性和创造性探索之间取得了平衡。
-
-具有思考能力的模型（AI 显示其推理过程）需要固定温度 1.0，无法更改，因为此设置可确保思考机制的最佳性能。这适用于任何启用“:thinking”标志的模型。
-
-某些专业模型根本不支持温度调整，在这种情况下，Kilo Code 会自动遵守这些限制。
-
-## 何时调整温度
-
-以下是一些可能适用于不同任务的温度设置示例：
-
-- **代码模式 (0.0-0.3)：** 用于编写精确、正确的代码，具有一致、确定性的结果
-- **架构师模式 (0.4-0.7)：** 用于头脑风暴架构或设计解决方案，具有平衡的创造性和结构
-- **询问模式 (0.7-1.0)：** 用于需要多样化和有见地的解释或开放式问题
-- **调试模式 (0.0-0.3)：** 用于以一致的精度排除故障
-
-这些是起点——重要的是[尝试不同的设置](#实验)以找到最适合您特定需求和偏好的设置。
-
-## 如何调整温度
-
-1. **打开 Kilo Code 面板：** 单击 VS Code 侧边栏中的 Kilo Code 图标（）
-2. **打开设置：** 单击右上角的
- *Kilo Code 设置面板中的温度滑块*
-
-## 使用 API 配置配置文件进行温度设置
-
-创建多个具有不同温度设置的[API 配置配置文件](/features/api-configuration-profiles)：
-
-**如何设置任务特定温度配置文件：**
-
-1. 创建专业配置文件，例如“代码 - 低温”（0.1）和“询问 - 高温”（0.8）
-2. 为每个配置文件配置适当的温度设置
-3. 使用设置或聊天界面中的下拉菜单在配置文件之间切换
-4. 为每种模式设置不同的配置文件作为默认值，以便在切换模式时自动切换
-
-这种方法可以优化模型行为以适应特定任务，而无需手动调整。
-
-## 技术实现
-
-Kilo Code 在实现温度处理时考虑了以下因素：
-
-- 用户定义的设置优先于默认设置
-- 尊重提供商特定的行为
-- 强制执行模型特定的限制：
- - 启用思考功能的模型需要固定温度 1.0
- - 某些模型不支持温度调整
-
-## 实验
-
-尝试不同的温度设置是发现最适合您特定需求的最有效方法：
-
-### 有效的温度测试
-
-1. **从默认值开始** - 从 Kilo Code 的预设值（大多数任务为 0.0）作为您的基线
-2. **进行增量调整** - 以小步（±0.1）更改值以观察细微差异
-3. **一致测试** - 在不同的温度设置下使用相同的提示进行有效比较
-4. **记录结果** - 记录哪些值对特定类型的任务产生最佳结果
-5. **创建配置文件** - 将有效设置保存为[API 配置配置文件](/features/api-configuration-profiles)以便快速访问
-
-请记住，不同的模型可能对相同的温度值有不同的响应，并且启用思考功能的模型始终使用固定温度 1.0，无论您的设置如何。
-
-## 相关功能
-
-- 适用于 Kilo Code 支持的所有 [API 提供商](/providers/openai)
-- 补充[自定义指令](/agent-behavior/custom-instructions)以微调响应
-- 与您创建的[自定义模式](/agent-behavior/custom-modes)一起使用
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/more-features.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/more-features.md
deleted file mode 100644
index 40730e6e5d9..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/more-features.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-sidebar_label: Additional Features
----
-
-
-# 附加功能
-
-Kilo Code 的附加功能简化了日常任务并提高了可访问性。
-
-## 建议回复
-
-Kilo Code 提供建议回复，让您减少打字时间。
-- 提问后，聊天框下方会出现按钮。
-- 单击按钮可将其用作您的下一个提示。
-
-## 文本转语音
-
-文本转语音功能让 Kilo Code 可以朗读回复。
-1. 在设置中启用 TTS。
-2. 单击任何回复旁边的扬声器图标即可开始收听。
-
-## 全球语言支持
-
-Kilo Code 支持 14 种语言：
-
-- 简体中文
-- 繁体中文
-- 西班牙语
-- 印地语
-- 法语
-- 葡萄牙语
-- 德语
-- 日语
-- 韩语
-- 意大利语
-- 土耳其语
-- 越南语
-- 波兰语
-- 加泰罗尼亚语
-
-在**高级设置 > 语言**下更改语言。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/settings-management.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/settings-management.md
deleted file mode 100644
index b75c6447066..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/settings-management.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: 导入、导出和重置设置
-sidebar_label: 导入/导出/重置设置
-description: 通过导出、导入或重置为默认值来管理您的 Kilo Code 设置。
----
-
-# 导入、导出和重置设置
-
-Kilo Code 允许您通过导出、导入和重置选项有效地管理您的配置设置。这些功能对于备份您的设置、与他人共享配置或在需要时恢复默认设置非常有用。
-
-您可以在 Kilo Code 设置页面的底部找到这些选项，通过 Kilo Code 聊天视图中的齿轮图标（）访问。
-
-
-*图片：导出、导入和重置按钮。*
-
-## 导出设置
-
-单击“**导出**”按钮会将您当前的 Kilo Code 设置保存到 JSON 文件中。
-
-* **导出内容：** 文件包含您配置的 API 提供商配置文件和全局设置（UI 首选项、模式配置、上下文设置等）。
-* **安全警告：** 导出的 JSON 文件包含**所有**您配置的 API 提供商配置文件和全局设置。至关重要的是，这包括**纯文本形式的 API 密钥**。请将此文件视为高度敏感。请勿公开或与不受信任的个人共享，因为它会授予对您的 API 帐户的访问权限。
-* **过程：**
- 1. 单击“**导出**”。
- 2. 出现文件保存对话框，建议将 `kilo-code-settings.json` 作为文件名（通常在您的 `~/Documents` 文件夹中）。
- 3. 选择位置并保存文件。
-
-这将创建您的配置备份或您可以共享的文件。
-
-## 导入设置
-
-单击“**导入**”按钮允许您从以前导出的 JSON 文件加载设置。
-
-* **过程：**
- 1. 单击“**导入**”。
- 2. 出现文件打开对话框。选择您要导入的 `kilo-code-settings.json` 文件（或类似名称的文件）。
- 3. Kilo Code 读取文件，根据预期模式验证其内容，并应用设置。
-* **合并：** 导入设置会**合并**配置。它会添加新的 API 配置文件并根据文件内容更新现有配置文件和全局设置。它**不会**删除您当前设置中存在但导入文件中缺失的配置。
-* **验证：** 只有与内部模式匹配的有效设置才能导入，从而防止配置错误。完成后会出现成功通知。
-
-## 重置设置
-
-单击“**重置**”按钮会完全清除所有 Kilo Code 配置数据，并将扩展恢复到其默认状态。这是一个破坏性操作，旨在用于故障排除或重新开始。
-
-* **警告：** 此操作**不可逆**。它会永久删除所有 API 配置（包括存储在秘密存储中的密钥）、自定义模式、全局设置和任务历史记录。
-
-* **过程：**
- 1. 单击红色“**重置**”按钮。
- 2. 出现确认对话框，警告此操作无法撤消。
- 3. 单击“是”以确认。
-
-* **重置内容：**
- * **API 提供商配置文件：** 所有配置都从设置和秘密存储中删除。
- * **全局设置：** 所有首选项（UI、模式、批准、浏览器等）都重置为默认值。
- * **自定义模式：** 所有用户定义的模式都删除。
- * **秘密存储：** Kilo Code 管理的所有 API 密钥和其他秘密都清除。
- * **任务历史记录：** 当前任务堆栈清除。
-
-* **结果：** Kilo Code 返回到其初始状态，就像刚安装一样，具有默认设置且没有用户配置。
-
-仅当您确定要删除所有 Kilo Code 数据或在故障排除期间收到指示时才使用此选项。如果您以后可能需要恢复设置，请考虑先导出您的设置。
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/shell-integration.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/shell-integration.md
deleted file mode 100644
index 4d7ce97e064..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/shell-integration.md
+++ /dev/null
@@ -1,382 +0,0 @@
-# 终端 Shell 集成
-
-终端 Shell 集成是一项关键功能，它使 Kilo Code 能够在您的终端中执行命令并智能地处理其输出。AI 与您的开发环境之间的这种双向通信解锁了强大的自动化功能。
-
-## 什么是 Shell 集成？
-
-Shell 集成在 Kilo Code 中自动启用，并直接连接到您的终端命令执行生命周期，无需您进行任何设置。此内置功能允许 Kilo Code：
-
-- 通过 [`execute_command`](/features/tools/execute-command) 工具代表您执行命令
-- 实时读取命令输出，无需手动复制粘贴
-- 自动检测并修复正在运行的应用程序中的错误
-- 观察命令退出代码以确定成功或失败
-- 在您导航项目时跟踪工作目录更改
-- 无需用户干预即可智能地响应终端输出
-
-当 Kilo Code 需要执行安装依赖项、启动开发服务器或分析构建错误等任务时，shell 集成会在后台工作，使这些交互顺畅有效。
-
-## Shell 集成入门
-
-Shell 集成内置于 Kilo Code 中，在大多数情况下会自动工作。如果您看到“Shell 集成不可用”消息或遇到命令执行问题，请尝试以下解决方案：
-
-1. **将 VSCode/Cursor 更新**到最新版本（需要 VSCode 1.93+）
-2. **确保选择了兼容的 shell**：命令面板（`Ctrl+Shift+P` 或 `Cmd+Shift+P`）→ “终端：选择默认配置文件”→ 选择 bash、zsh、PowerShell 或 fish
-3. **Windows PowerShell 用户**：运行 `Set-ExecutionPolicy RemoteSigned -Scope CurrentUser`，然后重新启动 VSCode
-4. **WSL 用户**：将 `. "$(code --locate-shell-integration-path bash)"` 添加到您的 `~/.bashrc`
-
-## 终端集成设置
-
-Kilo Code 提供了几个设置来微调 shell 集成。在 Kilo Code 侧边栏的“设置”→“终端”下访问这些设置。
-
-### 基本设置
-
-#### 终端输出限制
-
-控制从终端输出捕获的最大行数。超出时，它会保留开头 20% 和结尾 80%，中间有截断消息。这可以防止过度使用 token，同时保持上下文。默认值：500 行。
-控制从终端输出捕获的最大行数。超出时，会从中间删除行以节省 token。默认值：500 行。
-
-#### 终端 Shell 集成超时
-
-
-在执行命令之前等待 shell 集成初始化的最长时间。如果您遇到“Shell 集成不可用”错误，请增加此值。默认值：15 秒。
-
-#### 终端命令延迟
-
-
-在运行命令后添加一个短暂的暂停，以帮助 Kilo Code 正确捕获所有输出。由于 VSCode 在不同操作系统和 shell 配置中实现终端集成的方式，此设置可能会显著影响 shell 集成的可靠性：
-
-- **默认**：0 毫秒
-- **常见值**：
- * 0 毫秒：对于某些使用较新 VSCode 版本的用户效果最佳
- * 50 毫秒：历史默认值，对许多用户仍然有效
- * 150 毫秒：推荐用于 PowerShell 用户
-- **注意**：不同的值可能更适合您的：
- * VSCode 版本
- * Shell 自定义（oh-my-zsh、powerlevel10k 等）
- * 操作系统和环境
-
-### 高级设置
-
-:::info 重要
-**这些设置需要重新启动终端**
-
-高级终端设置的更改仅在重新启动终端后生效。要重新启动终端：
-
-1. 单击终端面板中的垃圾桶图标以关闭当前终端
-2. 使用“终端”→“新建终端”或 Ctrl+`（反引号）打开新终端
-
-更改任何这些设置后，务必重新启动所有打开的终端。
-:::
-
-#### PowerShell 计数器解决方法
-
-
-帮助 PowerShell 连续多次运行相同的命令。如果您发现 Kilo Code 无法在 PowerShell 中连续运行相同的命令，请启用此功能。
-
-#### 清除 ZSH EOL 标记
-
-
-防止 ZSH 在输出行末尾添加特殊字符，这些字符在 Kilo Code 读取终端结果时可能会造成混淆。
-
-#### Oh My Zsh 集成
-
-
-使 Kilo Code 更好地与流行的 [Oh My Zsh](https://ohmyz.sh/) shell 自定义框架配合使用。如果您使用 Oh My Zsh 并遇到终端问题，请打开此功能。
-
-#### Powerlevel10k 集成
-
-
-如果您使用 ZSH 的 Powerlevel10k 主题，则可提高兼容性。如果您的花哨终端提示导致 Kilo Code 出现问题，请打开此功能。
-
-#### ZDOTDIR 处理
-
-
-帮助 Kilo Code 与自定义 ZSH 配置配合使用，而不会干扰您的个人 shell 设置和自定义。
-
-## Shell 集成故障排除
-
-### PowerShell 执行策略 (Windows)
-
-PowerShell 默认限制脚本执行。要配置：
-
-1. 以管理员身份打开 PowerShell
-2. 检查当前策略：`Get-ExecutionPolicy`
-3. 设置适当的策略：`Set-ExecutionPolicy RemoteSigned -Scope CurrentUser`
-
-常见策略：
-- `Restricted`：不允许任何脚本（默认）
-- `RemoteSigned`：本地脚本可以运行；下载的脚本需要签名
-- `Unrestricted`：所有脚本都带警告运行
-- `AllSigned`：所有脚本都必须签名
-
-### 手动 Shell 集成安装
-
-如果自动集成失败，请将适当的行添加到您的 shell 配置中：
-
-**Bash** (`~/.bashrc`)：
-```bash
-[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash)"
-```
-
-**Zsh** (`~/.zshrc`)：
-```bash
-[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"
-```
-
-**PowerShell** (`$Profile`)：
-```powershell
-if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }
-```
-
-**Fish** (`~/.config/fish/config.fish`)：
-```fish
-string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration-path fish)
-```
-
-### 终端自定义问题
-
-如果您使用终端自定义工具：
-
-**Powerlevel10k**：
-```bash
-# 在 ~/.zshrc 中 source powerlevel10k 之前添加
-typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true
-```
-
-**替代方案**：在 Kilo Code 设置中启用 Powerlevel10k 集成设置。
-
-### 验证 Shell 集成状态
-
-使用以下命令确认 shell 集成处于活动状态：
-
-**Bash**：
-```bash
-set | grep -i '[16]33;'
-echo "$PROMPT_COMMAND" | grep vsc
-trap -p DEBUG | grep vsc
-```
-
-**Zsh**：
-```zsh
-functions | grep -i vsc
-typeset -p precmd_functions preexec_functions
-```
-
-**PowerShell**：
-```powershell
-Get-Command -Name "*VSC*" -CommandType Function
-Get-Content Function:\Prompt | Select-String "VSCode"
-```
-
-**Fish**：
-```fish
-functions | grep -i vsc
-functions fish_prompt | grep -i vsc
-```
-
-活动 shell 集成的视觉指示器：
-1. 终端标题栏中的 shell 集成指示器
-2. 命令检测高亮显示
-3. 终端标题中的工作目录更新
-4. 命令持续时间和退出代码报告
-
-## WSL 终端集成方法
-
-使用 Windows Subsystem for Linux (WSL) 时，有两种不同的方法可以使用 VSCode 和 WSL，每种方法对 shell 集成都有不同的影响：
-
-### 方法 1：VSCode Windows 与 WSL 终端
-
-在此设置中：
-- VSCode 在 Windows 中原生运行
-- 您在 VSCode 中使用 WSL 终端集成功能
-- Shell 命令通过 WSL 桥接执行
-- 由于 Windows-WSL 通信，可能会出现额外的延迟
-- Shell 集成标记可能会受到 WSL-Windows 边界的影响：您必须确保在 WSL 环境中为您的 shell 加载 `source "$(code --locate-shell-integration-path 
-
-此设置在使用 Cygwin、Fish 和 Starship 提示符的 Windows 系统上运行稳定，并应能帮助有类似配置的用户。
-
-
-### VSCode 1.98 版本后 Shell 集成失败
-
-**问题**：VSCode 更新到 1.98 以上版本后，shell 集成可能会失败，并显示错误 “VSCE output start escape sequence (]633;C or ]133;C) not received”。
-
-**解决方案**：
-1. **设置终端命令延迟**：
- - 在 Kilo Code 设置中将“终端命令延迟”设置为 50 毫秒。
- - 更改此设置后，重启所有终端。
- - 这与旧版的默认行为匹配，可能解决问题，但有用户报告称设置为 0 毫秒效果更好。这是针对上游 VSCode 问题的解决方法。
-
-2. **回退 VSCode 版本**：
- - 从 [VSCode 更新页面](https://code.visualstudio.com/updates/v1_98) 下载 VSCode v1.98。
- - 替换您当前的 VSCode 安装。
- - 无需备份 Kilo 设置。
-
-3. **WSL 特定解决方法**：
- - 如果使用 WSL，请确保您是从 WSL 内部通过 `code .` 命令启动 VSCode。
-
-4. **ZSH 用户**：
- - 尝试在 Kilo Code 设置中启用部分或全部 ZSH 相关的解决方法。
- - 无论您的操作系统是什么，这些设置都可能有所帮助。
-
-## 已知问题及解决方法
-
-### Ctrl+C 的行为
-
-**问题**：当 Kilo Code 尝试运行命令时，如果终端中已经输入了文本，Kilo Code 会先按 Ctrl+C 来清空当前行，这可能会中断正在运行的进程。
-
-**解决方法**：在要求 Kilo Code 执行终端命令之前，请确保您的终端提示符是空的（没有输入任何部分命令）。
-
-### 多行命令问题
-
-**问题**：跨多行的命令可能会让 Kilo Code 混淆，并可能将先前命令的输出与当前输出混合在一起。
-
-**解决方法**：不要使用多行命令，而是使用 `&&` 进行命令链接，将所有内容保持在一行（例如，使用 `echo a && echo b`，而不是分行输入每个命令）。
-
-### PowerShell 特定问题
-
-1. **过早完成**：PowerShell 有时会在所有输出显示完毕前就通知 Kilo Code 命令已完成。
-2. **重复命令**：PowerShell 可能会拒绝连续两次运行相同的命令。
-
-**解决方法**：启用“PowerShell 计数器解决方法”设置，并在设置中将终端命令延迟设置为 150 毫秒，以便为命令留出更多完成时间。
-
-### 终端输出不完整
-
-**问题**：有时 VS Code 不会显示或捕获命令的全部输出。
-
-**解决方法**：如果您发现输出缺失，请尝试关闭并重新打开终端选项卡，然后再次运行该命令。这会刷新终端连接。
-
-## 故障排除资源
-
-### 检查调试日志
-当出现 shell 集成问题时，请检查调试日志：
-1. 打开“帮助” → “切换开发人员工具” → “控制台”。
-2. 将日志级别设置为“显示所有级别”以查看所有日志消息。
-3. 查找包含 `[Terminal Process]` 的消息。
-4. 检查错误消息中的 `preOutput` 内容：
- - 空的 `preOutput` (`''`) 意味着 VSCode 没有发送任何数据。
- - 这表明可能存在 VSCode shell 集成问题，或者是我们无法控制的上游 bug。
- - 缺少 shell 集成标记可能需要调整设置，以解决与 shell 初始化和 VSCode 加载特殊 shell 集成钩子相关的上游 bug 或本地工作站配置问题。
-
-### 使用 VSCode Terminal Integration Test 扩展
-[VSCode Terminal Integration Test 扩展](https://github.com/KJ7LNW/vsce-test-terminal-integration) 通过测试不同的设置组合来帮助诊断 shell 集成问题：
-
-
-1. **当命令卡住时**：
- - 如果您看到“命令已在运行”的警告，请单击“重置统计信息”以重置终端状态。
- - 这些警告表明 shell 集成未正常工作。
- - 尝试不同的设置组合，直到找到一个可行的。
- - 如果问题确实卡住了，通过关闭窗口并按 F5 来重启扩展。
-
-2. **测试设置**：
- - 系统地尝试以下设置的不同组合：
- * 终端命令延迟
- * Shell 集成设置
- - 记录哪些组合成功或失败。
- - 这有助于识别 shell 集成问题的模式。
-
-3. **报告问题**：
- - 一旦找到有问题的配置。
- - 记录下确切的设置组合。
- - 注明您的环境（操作系统、VSCode 版本、shell 以及任何 shell 提示符自定义）。
- - 提交一个包含这些详细信息的问题，以帮助改进 shell 集成。
-
-## 支持
-
-如果您已遵循上述步骤但仍遇到问题，请：
-
-1. 查看 [Kilo Code GitHub Issues](https://github.com/Kilo-Org/kilocode/issues) 页面，看是否有人报告了类似的问题。
-2. 如果没有，请创建一个新 issue，并提供有关您的操作系统、VSCode/Cursor 版本以及您已尝试过的步骤的详细信息。
-
-如需更多帮助，请加入我们的 [Discord](https://kilocode.ai/discord)。如需其他帮助，请加入我们的 [Discord](https://kilocode.ai/discord)。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/slash-commands/workflows.mdx b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/slash-commands/workflows.mdx
deleted file mode 100644
index e9e648d6250..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/slash-commands/workflows.mdx
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: "工作流"
-sidebarTitle: "工作流"
----
-
-Workflows 通过为 Kilo Code 定义分步指令来自动化重复性任务。通过在聊天中键入 `/[workflow-name.md]` 来调用任何工作流。
-
-
-
-## 创建工作流
-
-工作流是存储在 `.kilocode/workflows/` 中的 markdown 文件：
-- **全局工作流**：`~/.kilocode/workflows/`（在所有项目中可用）
-- **项目工作流**：`[project]/.kilocode/workflows/`（项目特定）
-
-### 基本设置
-
-1. 创建一个包含分步指令的 `.md` 文件
-2. 将其保存在您的工作流目录中
-3. 键入 `/filename.md` 执行
-
-### 工作流功能
-
-工作流可以利用：
-- [内置工具](/features/tools/tool-use-overview)：[`read_file()`](/features/tools/read-file)、[`search_files()`](/features/tools/search-files)、[`execute_command()`](/features/tools/execute-command)
-- CLI 工具：`gh`、`docker`、`npm`、自定义脚本
-- [MCP 集成](/features/mcp/overview)：Slack、数据库、API
-- [模式切换](/basic-usage/using-modes)：[`new_task()`](/features/tools/new-task) 用于专业上下文
-
-## 常见工作流模式
-
-**发布管理**
-```markdown
-1. 收集自上次发布以来合并的 PR
-2. 从提交消息生成更新日志
-3. 更新版本号
-4. 创建发布分支和标签
-5. 部署到 staging 环境
-```
-
-**项目设置**
-```markdown
-1. 克隆仓库模板
-2. 安装依赖项（`npm install`、`pip install -r requirements.txt`）
-3. 配置环境文件
-4. 初始化数据库/服务
-5. 运行初始测试
-```
-
-**代码审查准备**
-```markdown
-1. 搜索 TODO 注释和 debug 语句
-2. 运行 linting 和格式化
-3. 执行测试套件
-4. 从最近的提交生成 PR 描述
-```
-
-## 示例：PR 提交工作流
-
-让我们逐步创建一个用于提交拉取请求的工作流。此工作流处理从代码审查到部署通知的整个过程。
-
-在您的 `.kilocode/workflows` 目录中创建一个名为 `submit-pr.md` 的文件：
-
-```markdown
-# 提交 PR 工作流
-
-您正在帮助提交拉取请求。请按照以下步骤操作：
-
-1. 首先，使用 `search_files` 检查是否有任何不应提交的 TODO 注释或 console.log 语句
-2. 使用 `execute_command` 运行测试，使用 `npm test` 或适当的测试命令
-3. 如果测试通过，则暂存并提交更改，并附上描述性提交消息
-4. 使用 `gh pr create` 推送分支并创建拉取请求
-5. 使用 `ask_followup_question` 从用户那里获取 PR 标题和描述
-
-所需参数（如果未提供则询问）：
-- 分支名称
-- 要分配的审阅者
-```
-
-现在您可以通过在聊天中键入 `/submit-pr.md` 来触发此工作流。Kilo Code 将：
-
-- 在提交之前扫描您的代码以查找常见问题
-- 运行您的测试套件以尽早发现问题
-- 处理 Git 操作和 PR 创建
-- 自动通知您的团队
-- 设置部署的后续任务
-
-这使您无需手动运行相同的 7 步过程，每次您想提交代码进行审查时。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/suggested-responses.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/suggested-responses.md
deleted file mode 100644
index af2196bcc22..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/suggested-responses.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-sidebar_label: Suggested Responses
----
-
-import Codicon from '@site/src/components/Codicon';
-
-# 建议回复
-
-当 Kilo Code 需要更多信息来完成任务时，它会使用 [`ask_followup_question` 工具](/features/tools/ask-followup-question)。为了使回复更轻松、更快捷，Kilo Code 通常会在问题旁边提供建议答案。
-
-## 概述
-
-建议回复以可点击按钮的形式直接显示在 Kilo Code 问题下方，位于聊天界面中。它们提供与问题相关的预设答案，帮助您快速提供输入。
-
-
-
-## 工作原理
-
-1. **问题出现**：Kilo Code 使用 `ask_followup_question` 工具提问。
-2. **显示建议**：如果 Kilo Code 提供了建议，它们将作为按钮显示在问题下方。
-3. **交互**：您可以通过两种方式与这些建议进行交互。
-
-## 与建议交互
-
-您有两种使用建议回复的选项：
-
-1. **直接选择**：
- * **操作**：只需单击包含您要提供的答案的按钮。
- * **结果**：选定的答案会立即作为您的回复发送回 Kilo Code。如果其中一个建议完全符合您的意图，这是最快的回复方式。
-
-2. **发送前编辑**：
- * **操作**：
- * 按住 `Shift` 并单击建议按钮。
- * *或者*，将鼠标悬停在建议按钮上，然后单击出现的铅笔图标（
-
-## 优点
-
-* **速度**：无需输入完整答案即可快速回复。
-* **清晰度**：建议通常会阐明 Kilo Code 需要的信息类型。
-* **灵活性**：根据需要编辑建议以提供精确、自定义的答案。
-
-此功能简化了 Kilo Code 需要澄清时的交互，让您能够以最少的精力有效指导任务。
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/system-notifications.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/system-notifications.md
deleted file mode 100644
index f7a1d005097..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/features/system-notifications.md
+++ /dev/null
@@ -1,251 +0,0 @@
-# 系统通知
-
-系统通知是原生操作系统通知，会出现在系统的通知中心或托盘中。与仅在编辑器内显示的 VSCode 内置通知不同，系统通知在以下情况下仍然可见：
-
-- VSCode 最小化或处于后台
-- 你正在其他应用程序中工作
-- 你的屏幕被锁定（取决于操作系统设置）
-- 你离开电脑
-
-Kilo Code 使用系统通知来告知你：
-
-- 任务完成状态
-- 重要错误或警告
-- 长时间运行操作的更新
-- 关键系统事件
-
-## 支持的操作系统
-
-Kilo Code 的系统通知可在所有主要操作系统上运行，但底层技术不同：
-
-| 操作系统 | 技术 | 要求 |
-| ----------- | ------------------------------- | ----------------------- |
-| **macOS** | AppleScript + terminal-notifier | 内置支持，可选增强功能 |
-| **Windows** | PowerShell + Windows Runtime | PowerShell 执行策略配置 |
-| **Linux** | notify-send | 安装 libnotify 包 |
-
-## 平台特定设置
-
-### macOS 设置
-
-macOS 对系统通知具有最佳的内置支持，有两种可用方法：
-
-#### 方法 1：内置 AppleScript（备用）
-
-无需额外设置。Kilo Code 使用 macOS 的内置命令来显示通知。
-
-#### 方法 2：使用 terminal-notifier 增强（推荐）
-
-要获得带有自定义图标的增强通知，请安装 terminal-notifier：
-
-```bash
-# 通过 Homebrew 安装
-brew install terminal-notifier
-
-# 或通过 npm 安装
-npm install -g terminal-notifier
-```
-
-**工作原理：** Kilo Code 首先尝试使用 `terminal-notifier`，如果未安装则自动回退到 AppleScript。
-
-### Windows 设置
-
-Windows 通知需要配置 PowerShell 执行策略才能正常工作。
-
-#### 步骤 1：配置 PowerShell 执行策略
-
-以管理员身份打开 PowerShell 并运行：
-
-```powershell
-# 检查当前执行策略
-Get-ExecutionPolicy
-
-# 设置执行策略以允许本地脚本运行
-Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
-```
-
-#### 步骤 2：验证 Windows Runtime 访问权限
-
-Windows 通知通过 PowerShell 使用 `Windows.UI.Notifications` API。此功能在以下版本中可用：
-
-- ✅ Windows 10（所有版本）
-- ✅ Windows 11（所有版本）
-- ✅ Windows Server 2016 及更高版本
-- ❌ Windows 8.1 及更早版本（支持有限）
-
-#### 执行策略选项
-
-| 策略 | 描述 | 安全级别 | 推荐 |
-| -------------- | ---------------------------------- | -------- | ----------- |
-| `Restricted` | 不允许运行脚本（默认） | 最高 | ❌ 阻止通知 |
-| `RemoteSigned` | 本地脚本可运行，下载的脚本需要签名 | 高 | ✅ **推荐** |
-| `Unrestricted` | 所有脚本运行但会显示警告 | 中等 | ⚠️ 谨慎使用 |
-| `AllSigned` | 所有脚本必须签名 | 最高 | ❌ 过于严格 |
-
-### Linux 设置
-
-Linux 通知需要 `libnotify` 包和 `notify-send` 命令。
-
-#### Ubuntu/Debian 安装
-
-```bash
-# 安装 libnotify
-sudo apt update
-sudo apt install libnotify-bin
-
-# 验证安装
-which notify-send
-```
-
-#### Red Hat/CentOS/Fedora 安装
-
-```bash
-# RHEL/CentOS
-sudo yum install libnotify
-
-# Fedora
-sudo dnf install libnotify
-
-# 验证安装
-which notify-send
-```
-
-#### Arch Linux 安装
-
-```bash
-# 安装 libnotify
-sudo pacman -S libnotify
-
-# 验证安装
-which notify-send
-```
-
-#### 桌面环境要求
-
-系统通知在以下桌面环境中效果最佳：
-
-| 桌面环境 | 支持级别 | 说明 |
-| -------------- | ----------- | ------------------------ |
-| **GNOME** | ✅ 完全支持 | 原生通知中心 |
-| **KDE Plasma** | ✅ 完全支持 | 原生通知系统 |
-| **XFCE** | ✅ 良好支持 | 需要通知守护进程 |
-| **Unity** | ✅ 完全支持 | Ubuntu 的通知系统 |
-| **i3/Sway** | ⚠️ 有限支持 | 需要手动设置通知守护进程 |
-| **Headless** | ❌ 不支持 | 无显示服务器可用 |
-
-#### 通知守护进程设置（高级）
-
-对于极简窗口管理器，你可能需要启动通知守护进程：
-
-```bash
-# 安装并启动 dunst（轻量级通知守护进程）
-sudo apt install dunst # Ubuntu/Debian
-sudo pacman -S dunst # Arch Linux
-
-# 手动启动 dunst
-dunst &
-
-# 或添加到窗口管理器启动脚本
-echo "dunst &" >> ~/.xinitrc
-```
-
-## 验证系统通知
-
-### 各平台测试命令
-
-#### macOS 测试
-
-```bash
-# 测试 AppleScript 方法
-osascript -e 'display notification "测试消息" with title "测试标题" sound name "Tink"'
-
-# 测试 terminal-notifier（如果已安装）
-terminal-notifier -message "测试消息" -title "测试标题" -sound Tink
-```
-
-#### Windows 测试
-
-```powershell
-# 测试 PowerShell 通知
-$template = @"
-
-
-_OpenRouter仪表板，带有"创建密钥"按钮。命名您的密钥并在创建后复制它。_
-
-##### Requesty
-
-1. 访问 [requesty.ai](https://requesty.ai/)
-2. 使用Google账号或电子邮件登录
-3. 导航到[API管理页面](https://app.requesty.ai/manage-api)并创建新密钥
-4. **重要：** 立即复制您的API密钥，因为它不会再次显示
-
-
-
-_Requesty API管理页面，带有"创建API密钥"按钮。立即复制您的密钥 - 它只会显示一次。_
-
-#### 选项2：直接提供商
-
-直接访问特定模型的原提供商，完全使用其功能和特性：
-
-##### Anthropic
-
-1. 访问 [console.anthropic.com](https://console.anthropic.com/)
-2. 注册账号或登录
-3. 导航到[API密钥部分](https://console.anthropic.com/settings/keys)并创建新密钥
-4. **重要：** 立即复制您的API密钥，因为它不会再次显示
-
-
-
-_Anthropic控制台API密钥部分，带有"创建密钥"按钮。命名您的密钥，设置过期时间，并立即复制它。_
-
-##### OpenAI
-
-1. 访问 [platform.openai.com](https://platform.openai.com/)
-2. 注册账号或登录
-3. 导航到[API密钥部分](https://platform.openai.com/api-keys)并创建新密钥
-4. **重要：** 立即复制您的API密钥，因为它不会再次显示
-
-
-
-_OpenAI平台，带有"创建新密钥"按钮。命名您的密钥并在创建后立即复制它。_
-
-### 在VS Code中配置Kilo Code
-
-获取API密钥后：
-
-1. 点击VS Code侧边栏中的Kilo Code图标()打开Kilo Code侧边栏
-2. 在欢迎界面，从下拉菜单中选择您的API提供商
-3. 将API密钥粘贴到相应字段中
-4. 选择您的模型：
- - 对于**OpenRouter**：选择`anthropic/claude-3.7-sonnet` ([模型详情](https://openrouter.ai/anthropic/claude-3.7-sonnet))
- - 对于**Anthropic**：选择`claude-3-7-sonnet-20250219` ([模型详情](https://www.anthropic.com/pricing#anthropic-api))
-5. 点击"Let's go!"保存设置并开始使用Kilo Code
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/installing.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/installing.md
deleted file mode 100644
index 384c64224c6..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/installing.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-sidebar_label: 安装Kilo Code
----
-
-# 安装Kilo Code
-
-Kilo Code是一款VS Code扩展，可将AI编程助手直接集成到编辑器中。可通过以下方式安装：
-
-- [**VS Code应用商店（推荐）**](#vs-code应用商店) - VS Code用户最快捷的安装方式
-- [**Cursor应用商店**](#cursor应用商店) - Cursor用户的推荐安装方式
-- [**Open VSX注册表**](#open-vsx注册表) - 适用于VSCodium/Windsurf等兼容VS Code的编辑器
-- [**手动安装.vsix文件**](#手动安装vsix文件) - 从GitHub Release直接安装
-
-## VS Code应用商店
-
-:::tip
-
-若已安装VS Code：[点击此处直接安装Kilo Code](vscode:extension/kilocode.Kilo-Code)
-
-:::
-
-或按以下步骤操作：
-
-1. 打开VS Code
-2. 进入扩展面板：点击侧边栏扩展图标 或按 `Ctrl+Shift+X`（Windows/Linux） / `Cmd+Shift+X`（macOS）
-3. 搜索 "Kilo Code"
-4. 选择Kilo Code发布的扩展并点击**安装**
-5. 根据提示重新加载VS Code
-
-安装完成后，在侧边栏找到Kilo Code图标（）即可打开面板。
-
-
-*VS Code应用商店中的Kilo Code扩展安装界面*
-
-## Cursor应用商店
-
-:::tip
-
-若已安装Cursor：[点击此处直接安装Kilo Code](cursor:extension/kilocode.Kilo-Code)
-
-:::
-
-或按以下步骤操作：
-
-1. 打开Cursor
-2. 进入扩展面板：点击侧边栏扩展图标 或按 `Ctrl+Shift+X`（Windows/Linux） / `Cmd+Shift+X`（macOS）
-3. 搜索 "Kilo Code"
-4. 选择Kilo Code发布的扩展并点击**安装**
-5. 根据提示重新加载Cursor
-
-安装完成后，在侧边栏找到Kilo Code图标（）即可打开面板。
-
-## Open VSX注册表
-
-[Open VSX注册表](https://open-vsx.org/)是VS Code应用商店的开源替代方案，适用于因许可证限制无法访问官方商店的编辑器。
-
-在VSCodium、Gitpod、Eclipse Theia、Windsurf等兼容编辑器中，可通过[Open VSX上的Kilo Code页面](https://open-vsx.org/extension/kilocode/Kilo-Code)直接安装。
-
-1. 打开编辑器
-2. 进入扩展视图（侧边栏图标或快捷键 `Ctrl+Shift-X` / `Cmd+Shift-X`）
-3. 编辑器应已预配置Open VSX注册表
-4. 搜索 "Kilo Code"
-5. 选择扩展并点击**安装**
-6. 根据提示重新加载编辑器
-
-:::note
-若编辑器未自动配置Open VSX，需在设置中手动配置扩展市场。具体操作请参考编辑器文档。
-:::
-
-## 手动安装VSIX文件
-
-若需手动下载安装：
-
-1. **下载VSIX文件：**
-
- - 在[Kilo Code GitHub Releases页面](https://github.com/Kilo-Org/kilocode/releases)查找正式版本
- - 从[最新版本](https://github.com/Kilo-Org/kilocode/releases/latest)下载`.vsix`文件
-
-2. **在VS Code中安装：**
- - 打开VS Code
- - 进入扩展视图
- - 点击扩展视图右上角的"..."菜单
- - 选择"从VSIX安装..."
- - 选择已下载的`.vsix`文件
-
-
-*通过VS Code的"从VSIX安装"对话框进行安装*
-
-## 故障排除
-
-**扩展不可见**
-
-- 重启VS Code
-- 检查扩展列表确认Kilo Code已启用
-- 尝试禁用后重新启用扩展
-- 在输出面板查看错误日志（查看 → 输出，选择"Kilo Code"）
-
-**安装问题**
-
-- 确保网络连接稳定
-- 确认VS Code版本≥1.84.0
-- 若无法访问VS Code应用商店，尝试Open VSX方式
-
-## 获取支持
-
-若遇到其他问题：
-
-- 加入[Discord社区](https://kilo.ai/discord)获取实时支持
-- 在[GitHub](https://github.com/Kilo-Org/kilocode/issues)提交问题报告
-- 访问[Reddit社区](https://www.reddit.com/r/KiloCode)
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/setting-up.mdx b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/setting-up.mdx
deleted file mode 100644
index d6667342e57..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/setting-up.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-sidebar_label: 初始设置
----
-
-import { DISCORD_URL } from "@site/src/constants.ts";
-import useDocusaurusContext from "@docusaurus/useDocusaurusContext";
-
-# 设置Kilo Code
-
-1. **注册：** 完成注册流程
-2. **首次充值：** 向账户添加资金（最低 $5）并获得 $20 奖励积分
-3. **开始编程：** 尽情使用你的 $20 免费积分
-
-:::note 关于临时冻结
-有时，我们可能需要临时冻结 $0.50，这仅用于身份验证：
-
-- **免费** - 这是临时授权，不会被收取费用
-- **即时释放** - Kilo Code 在验证后会立即释放冻结
-- **银行处理** - 虽然我们即时释放，但资金返回可能需要几个工作日（因银行而异）
- :::
-
-## 注册流程
-
-Kilo Code提供简单的注册流程，通过你的账号即可使用前沿的编程模型：
-
-1. 在扩展中点击"免费试用 Kilo Code"
-2. 使用你的 Google 账户登录 kilocode.ai
-3. kilocode.ai 将提示你打开 Visual Studio Code
- - 当使用浏览器中的 IDE 时，系统会要求你手动复制 API 密钥
-4. 允许打开 VS Code 后，还必须允许 VS Code 打开授权 URL
-
-
-
-完成！现在可以开始你的[第一个任务](/getting-started/your-first-task)
-
-:::tip 需要帮助？
-如有任何定价或token相关问题，请联系[支持团队](mailto:hi@kilocode.ai)或加入我们的Discord社区。
-:::
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/your-first-task.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/your-first-task.md
deleted file mode 100644
index b2e75261e54..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/getting-started/your-first-task.md
+++ /dev/null
@@ -1,72 +0,0 @@
----
-sidebar_label: 第一个任务
----
-
-# 开始你的第一个Kilo Code任务
-
-本快速教程将展示 Kilo Code 如何从头到尾处理一个简单的请求。
-
-完成[初始设置](/getting-started/setting-up)后，请按照以下步骤操作：
-
-## 第一步：打开Kilo Code面板
-
-点击VS Code主侧边栏（窗口侧边的垂直栏）中的Kilo Code图标（）打开聊天界面。如果看不到图标，请确认扩展已[安装](/getting-started/installing)并启用。
-
-
-*主侧边栏中的Kilo Code图标可打开聊天界面*
-
-## 第二步：输入你的任务
-
-在面板底部的聊天框中，清晰简洁地描述你希望Kilo Code完成的操作。有效任务的示例：
-
-* "创建名为`hello.txt`的文件，内容为'Hello, world!'"
-* "编写一个两数相加的Python函数"
-* "创建一个标题为'Kilo测试'的简单网站HTML文件"
-
-无需特殊命令或语法——使用普通英语即可。
-
-
-*用自然语言输入任务 - 无需特殊语法*
-
-## 第三步：发送任务
-
-按Enter键或点击输入框右侧的发送图标（
-*Kilo Code明确显示将要执行的操作并等待你的批准*
-
-* 在**Code**模式下，默认启用许多代码编写功能
-* 在**Architect**和**Ask**模式下，代理不会编写任何代码
-
-:::tip
-自主程度可配置，你可以让代理更自主或更受限。
-
-了解更多关于[使用模式](/basic-usage/using-modes)和[自动批准操作](/features/auto-approving-actions)。
-:::
-
-## 第五步：迭代操作
-
-Kilo Code以迭代方式工作。每个操作后都会等待你的反馈，然后再提出下一步建议。持续这个"审核-批准"循环直到任务完成。
-
-
-*任务完成后，Kilo Code显示最终结果并等待下一条指令*
-
-## 总结
-
-你已完成第一个Kilo Code任务！通过这个过程，你已了解：
-
-* 如何使用自然语言与Kilo Code交互
-* 让你保持控制的基于批准的工作流
-* Kilo Code用于逐步解决问题的迭代方法
-
-这种迭代的、基于批准的工作流是Kilo Code的核心——让AI处理编码的繁琐部分，同时你保持完全监督。现在你已掌握基础知识，可以尝试更复杂的任务，探索不同的[模式](/basic-usage/using-modes)进行专门的工作流，或试用[自动批准功能](/features/auto-approving-actions)来加速重复性任务。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/index.mdx b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/index.mdx
deleted file mode 100644
index fa295c1db21..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/index.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
----
-sidebar_label: 欢迎
----
-
-import {
- DISCORD_URL,
- REDDIT_URL,
- GITHUB_ISSUES_MAIN_URL,
- GITHUB_FEATURES_URL,
- YOUTUBE_URL,
-} from "@site/src/constants.ts"
-import Image from "@site/src/components/Image"
-
-# Kilo Code 文档
-
-Kilo Code 通过 AI 驱动的代码生成和任务自动化**加速**开发。这个开源扩展直接集成到 VS Code 中。
-
-## Kilo Code 能做什么？
-
-- 🚀 **生成代码**：根据自然语言描述生成代码
-- 🔧 **重构与调试**：优化现有代码并修复问题
-- 📝 **编写与更新**：创建和更新文档
-- 🤔 **回答问题**：解答关于代码库的疑问
-- 🔄 **自动化**：自动化重复性任务
-- 🏗️ **创建**：新建文件和项目
-
-## 快速开始
-
-1. [安装 Kilo Code](/getting-started/installing)
-2. [设置 Kilo Code](/getting-started/setting-up)
-3. [尝试你的首个任务](/getting-started/your-first-task)
-
-## 功能
-
-
-*使用 devstral 编写贪吃蛇游戏*
-
-## 管理期望
-
-可以在本地运行的LLM通常比云端托管的LLM（如Claude和GPT）要小得多，因此结果也会逊色不少。
-它们更容易陷入循环、无法正确使用工具或在代码中产生语法错误。
-要找到合适的提示词通常需要更多的反复试验。
-本地运行LLM通常也不够快。
-使用简单的提示词、保持对话简短并禁用MCP工具可以提高运行速度。
-
-## 硬件要求
-
-你需要一块拥有大量显存（24GB或以上）的GPU，或者一台拥有大量统一内存（32GB或以上）的MacBook，才能以良好的速度运行下面讨论的模型。
-
-## 选择模型
-
-Ollama 支持许多不同的模型。
-你可以在 [Ollama 网站](https://ollama.com/library) 上找到可用模型的列表。
-
-对于 Kilo Code 代理，当前推荐使用 `qwen3-coder:30b`。`qwen3-coder:30b` 有时无法正确调用工具（相比完整版 `qwen3-coder:480b` 模型，这个问题更常见）。作为一个混合专家模型，这可能是因为它激活了错误的专家。每当发生这种情况时，尝试更改你的提示词或使用“增强提示”按钮。
-
-`qwen3-coder:30b` 的替代方案是 `devstral:24b`。对于 Kilo Code 的其他功能，如增强提示或提交信息生成，较小的模型可能就足够了。
-
-## 设置 Ollama
-
-要设置 Ollama 以与 Kilo Code 一起使用，请按照以下说明操作。
-
-### 下载并安装 Ollama
-
-从 [Ollama 网站](https://ollama.com/) 下载 Ollama 安装程序（或使用你操作系统的包管理器）。按照安装说明操作，然后确保 Ollama 正在运行：
-
-```bash
-ollama serve
-```
-
-### 下载模型
-
-要下载模型，请打开第二个终端（`ollama serve` 需要正在运行）并运行：
-
-```bash
-ollama pull 图标）。
-- 点击设置齿轮图标（
-
-## 支持的模型
-
-目前，v0 提供以下模型：
-
-* `v0-1.0-md` - v0 的多模态模型，支持文本和图像输入
-* `v0-1.5-lg` - 复合模型（[了解更多](https://vercel.com/blog/v0-composite-model-family)）
-* `v0-1.5.md` - 复合模型（[了解更多](https://vercel.com/blog/v0-composite-model-family)）
-
-## 故障排除
-
-* **“无效 API 密钥”：** 仔细检查您是否正确输入了 API 密钥。
-* **“模型未找到”：** 确保您使用的是正确的模型 ID（`v0-1.0-md`）。
-* **连接错误：** 验证基本 URL 是否正确（`https://api.v0.dev/v1`）。
-* **访问问题：** 确认您的 Vercel v0 团队帐户处于活动状态并已正确设置。
-
-## 附加资源
-
-* [v0 官方文档](https://v0.dev)
-* [Vercel AI 文档](https://vercel.com/docs/ai)
\ No newline at end of file
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/providers/vertex.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/providers/vertex.md
deleted file mode 100644
index 17d3e84cff8..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/providers/vertex.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-sidebar_label: GCP Vertex AI
----
-
-# 在 Kilo Code 中使用 GCP Vertex AI
-
-Kilo Code 支持通过 Google Cloud Platform 的 Vertex AI 访问模型，这是一个托管的机器学习平台，提供对多种基础模型的访问，包括 Anthropic 的 Claude 系列。
-
-**网站:** [https://cloud.google.com/vertex-ai](https://cloud.google.com/vertex-ai)
-
-## 先决条件
-
-* **Google Cloud 账户:** 您需要一个活跃的 Google Cloud Platform (GCP) 账户。
-* **项目:** 您需要一个启用了 Vertex AI API 的 GCP 项目。
-* **模型访问权限:** 您必须请求并获准访问您想要使用的特定 Claude 模型。请参阅 [Google Cloud 文档](https://cloud.google.com/vertex-ai/generative-ai/docs/partner-models/use-claude#before_you_begin) 获取说明。
-* **应用程序默认凭据 (ADC):** Kilo Code 使用应用程序默认凭据来与 Vertex AI 进行身份验证。最简单的设置方法是：
- 1. 安装 Google Cloud CLI: [https://cloud.google.com/sdk/docs/install](https://cloud.google.com/sdk/docs/install)
- 2. 使用以下命令进行身份验证：`gcloud auth application-default login`
-* **服务帐户密钥（替代方案）：** 或者，您可以使用 Google Cloud 服务帐户密钥文件进行身份验证。您需要在 GCP 项目中生成此密钥。请参阅 [Google Cloud 文档中关于创建服务帐户密钥](https://cloud.google.com/iam/docs/creating-managing-service-account-keys)的部分。
-
-## 支持的模型
-
-Kilo Code 通过 Vertex AI 支持以下模型（基于源代码）：
-
-* **Google Gemini 模型：**
- * `gemini-2.5-flash-preview-05-20`
- * `gemini-2.0-flash-001`
- * `gemini-2.5-pro-exp-03-25`
- * `gemini-2.0-pro-exp-02-05`
- * `gemini-2.0-flash-lite-001`
- * `gemini-2.0-flash-thinking-exp-01-21`
- * `gemini-1.5-flash-002`
- * `gemini-1.5-pro-002`
-* **Anthropic Claude 模型：**
- * `claude-opus-4@20250514:thinking`
- * `claude-opus-4@20250514`
- * `claude-sonnet-4@20250514:thinking`
- * `claude-sonnet-4@20250514`
- * `claude-3-7-sonnet@20250219:thinking`
- * `claude-3-7-sonnet@20250219`
- * `claude-3-5-sonnet-v2@20241022`
- * `claude-3-5-sonnet@20240620`
- * `claude-3-5-haiku@20241022`
- * `claude-3-opus@20240229`
- * `claude-3-haiku@20240307`
-
-请参阅 [Google Cloud 关于 Vertex AI 模型的文档](https://cloud.google.com极客/vertex-ai/generative-ai/docs/learn/models) 获取最新可用模型及其 ID 列表。
-
-## 在 Kilo Code 中配置
-
-1. **打开 Kilo Code 设置:** 点击 Kilo Code 面板中的齿轮图标 (
-
-3. **添加提供商档案：**
-
- - 在配置面板中，点击 **"添加档案"** 按钮在列表中创建一个新条目。
- - 点击新条目上的下拉菜单，选择你其他已预配置的提供商档案之一（例如，"OpenAI"、"Chutes AI 免费层级"）。
-
-4. **设置使用限制（可选）：**
-
- - 添加配置后，你可以指定使用限制。如果将这些字段留空，则不会对该特定指标强制执行任何限制。
- - **每分钟/小时/天的令牌数：** 根据处理的令牌总数（输入 + 输出）限制使用量。
- - **每分钟/小时/天的请求数：** 限制发出的 API 调用总数。
-
-5. **排列你的提供商：**
-
- - 档案的顺序至关重要，因为它定义了回退优先级。顶部的提供商将首先被使用。
- - 使用每个档案旁边的 **上下箭头** 来更改其在列表中的位置。
-
-6. **添加更多提供商：** 重复步骤 3-5 来构建你的完整回退链。你可以添加任意数量的已配置档案。
-
-
-
-## 使用监控
-
-配置屏幕还充当监控列表中每个提供商当前使用情况的仪表板。
-
-- 你可以看到最后一分钟、一小时和一天内使用的令牌数和请求数。
-- 如果需要重置这些计数器，请点击 **"清除使用数据"** 按钮。这将把所有统计数据重置为零，并立即重新启用因超出限制而暂时禁用的任何提供商。
-
-## 使用案例示例
-
-假设你配置了两个档案：
-
-1. **Chutes AI 免费：** 一个免费层级提供商，限制为每小时 5,000 个令牌。
-2. **OpenAI 付费：** 你个人的按需付费 OpenAI 账户。
-
-**配置：**
-
-- 将 "Chutes AI 免费" 放在列表的第一位。
-- 将其 "每小时令牌数" 限制设置为 `5000`。
-- 将 "OpenAI 付费" 放在列表的第二位，不定义任何限制。
-
-**结果：**
-Kilo Code 将把所有请求发送到 Chutes AI。一旦你在一小时内使用的令牌数超过 5,000 个，它将自动切换到你的 OpenAI 账户。当配额窗口在下一小时重置时，系统将切换回 Chutes AI。
-
-## 提示和注意事项
-
-- **优先级是关键：** 始终仔细检查你的档案顺序。预期的主要或免费层级提供商应位于顶部。
-- **基于错误的回退：** 如果你没有为档案设置任何限制，则只有在提供商的 API 返回错误时才会发生回退（例如，服务本身的硬性速率限制、网络问题或无效的 API 密钥）。
-- **无嵌套：** 你不能在此提供商的配置中选择另一个 "virtual quota fallback" 档案，因为这会创建循环依赖。
diff --git a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/providers/vscode-lm.md b/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/providers/vscode-lm.md
deleted file mode 100644
index b48371a3a8d..00000000000
--- a/packages/kilo-docs/i18n/zh-CN/docusaurus-plugin-content-docs/current/providers/vscode-lm.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-sidebar_label: VS Code 语言模型 API
----
-
-# 在 Kilo Code 中使用 VS Code 语言模型 API
-
-Kilo Code 包含对 [VS Code 语言模型 API](https://code.visualstudio.com/api/language-extensions/language-model-access) 的*实验性*支持。该 API 允许扩展直接在 VS Code 中提供对语言模型的访问。这意味着您可以潜在使用以下模型：
-
-* **GitHub Copilot:** 如果您有 Copilot 订阅并安装了该扩展。
-* **其他 VS Code 扩展:** 任何实现语言模型 API 的扩展。
-
-**重要提示:** 此集成是高度实验性的，可能无法按预期工作。它依赖于其他扩展正确实现 VS Code 语言模型 API。
-
-## 先决条件
-
-* **VS Code:** 语言模型 API 通过 VS Code 提供（目前不支持 Cursor）。
-* **语言模型提供者扩展:** 您需要一个提供语言模型的扩展。示例包括：
- * **GitHub Copilot:** 如果您有 Copilot 订阅，GitHub Copilot 和 GitHub Copilot Chat 扩展可以提供模型。
- * **其他扩展:** 在 VS Code 市场搜索提到 "Language Model API" 或 "lm" 的扩展。可能会有其他实验性扩展可用。
-
-## 配置
-
-1. **打开 Kilo Code 设置:** 点击 Kilo Code 面板中的齿轮图标 (
+
+
+ )
+}
+
+// This tells Next.js to use a different layout approach
+Custom404.is404 = true
diff --git a/packages/kilo-docs/pages/_app.tsx b/packages/kilo-docs/pages/_app.tsx
new file mode 100644
index 00000000000..0f27a122493
--- /dev/null
+++ b/packages/kilo-docs/pages/_app.tsx
@@ -0,0 +1,243 @@
+import React, { useState, useEffect } from "react"
+import Head from "next/head"
+import Link from "next/link"
+import { useRouter } from "next/router"
+
+import { CopyPageButton, SideNav, TableOfContents, TopNav } from "../components"
+
+import "prismjs"
+// Import other Prism themes here
+import "prismjs/components/prism-bash.min"
+import "prismjs/themes/prism.css"
+
+import "../public/globals.css"
+
+import type { AppProps } from "next/app"
+import type { MarkdocNextJsPageProps } from "@markdoc/next.js"
+
+const TITLE = "Kilo Code Documentation"
+const DESCRIPTION = "Build, ship, and iterate faster with the most popular open source coding agent."
+
+function collectHeadings(node, sections = []) {
+ if (node) {
+ // Skip headings inside tabs - they're not always visible
+ if (node.name === "Tabs") {
+ return sections
+ }
+
+ if (node.name === "Heading") {
+ const title = node.children[0]
+
+ if (typeof title === "string") {
+ sections.push({
+ ...node.attributes,
+ title,
+ })
+ }
+ }
+
+ if (node.children) {
+ for (const child of node.children) {
+ collectHeadings(child, sections)
+ }
+ }
+ }
+
+ return sections
+}
+
+export type MyAppProps = MarkdocNextJsPageProps
+
+export default function MyApp({ Component, pageProps }: AppProps
+ {/* Terminal Window */}
+
+
+
+
+
+
+ {/* Message */}
+
+
+
+
+
+
+
+ terminal
+
+
+
+ $
+ GET /requested-path
+
+
+ Error 404: Page not found
+
+
+
+ 404
+
+
+
+
+ {/* Actions */}
+ Page not found
+The page you requested does not exist or has been moved.
+
+
+ Return to Documentation
+
+
+ Getting Started
+
+
+
+
+
+
+ )}
+
+
+ )
+}
diff --git a/packages/kilo-docs/pages/ai-providers/anthropic.md b/packages/kilo-docs/pages/ai-providers/anthropic.md
new file mode 100644
index 00000000000..dc96d0d4016
--- /dev/null
+++ b/packages/kilo-docs/pages/ai-providers/anthropic.md
@@ -0,0 +1,31 @@
+---
+sidebar_label: Anthropic
+---
+
+# Using Anthropic With Kilo Code
+
+Anthropic is an AI safety and research company that builds reliable, interpretable, and steerable AI systems. Their Claude models are known for their strong reasoning abilities, helpfulness, and honesty.
+
+**Website:** [https://www.anthropic.com/](https://www.anthropic.com/)
+
+## Getting an API Key
+
+1. **Sign Up/Sign In:** Go to the [Anthropic Console](https://console.anthropic.com/). Create an account or sign in.
+2. **Navigate to API Keys:** Go to the [API keys](https://console.anthropic.com/settings/keys) section.
+3. **Create a Key:** Click "Create Key". Give your key a descriptive name (e.g., "Kilo Code").
+4. **Copy the Key:** **Important:** Copy the API key _immediately_. You will not be able to see it again. Store it securely.
+
+## Configuration in Kilo Code
+
+1. **Open Kilo Code Settings:** Click the gear icon ({% codicon name="gear" /%}) in the Kilo Code panel.
+2. **Select Provider:** Choose "Anthropic" from the "API Provider" dropdown.
+3. **Enter API Key:** Paste your Anthropic API key into the "Anthropic API Key" field.
+4. **Select Model:** Choose your desired Claude model from the "Model" dropdown.
+5. **(Optional) Custom Base URL:** If you need to use a custom base URL for the Anthropic API, check "Use custom base URL" and enter the URL. Most people won't need to adjust this.
+
+## Tips and Notes
+
+- **Prompt Caching:** Claude 3 models support [prompt caching](https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching), which can significantly reduce costs and latency for repeated prompts.
+- **Context Window:** Claude models have large context windows (200,000 tokens), allowing you to include a significant amount of code and context in your prompts.
+- **Pricing:** Refer to the [Anthropic Pricing](https://www.anthropic.com/pricing) page for the latest pricing information.
+- **Rate Limits:** Anthropic has strict rate limits based on [usage tiers](https://docs.anthropic.com/en/api/rate-limits#requirements-to-advance-tier). If you're repeatedly hitting rate limits, consider contacting Anthropic sales or accessing Claude through a different provider like [OpenRouter](/providers/openrouter) or [Requesty](/providers/requesty).
diff --git a/packages/kilo-docs/docs/providers/bedrock.md b/packages/kilo-docs/pages/ai-providers/bedrock.md
similarity index 64%
rename from packages/kilo-docs/docs/providers/bedrock.md
rename to packages/kilo-docs/pages/ai-providers/bedrock.md
index bb7eae0730b..f0077fe6cb0 100644
--- a/packages/kilo-docs/docs/providers/bedrock.md
+++ b/packages/kilo-docs/pages/ai-providers/bedrock.md
@@ -32,50 +32,9 @@ You have three options for configuring AWS credentials:
3. **AWS Profile:**
- Configure an AWS profile using the AWS CLI or by manually editing your AWS credentials file. See the [AWS CLI documentation](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html) for details.
-## Supported Models
-
-Kilo Code supports the following models through Bedrock (based on source code):
-
-- **Amazon:**
- - `amazon.nova-pro-v1:0`
- - `amazon.nova-pro-latency-optimized-v1:0`
- - `amazon.nova-lite-v1:0`
- - `amazon.nova-micro-v1:0`
- - `amazon.titan-text-lite-v1:0`
- - `amazon.titan-text-express-v1:0`
- - `amazon.titan-text-embeddings-v1:0`
- - `amazon.titan-text-embeddings-v2:0`
-- **Anthropic:**
- - `anthropic.claude-3-7-sonnet-20250219-v1:0`
- - `anthropic.claude-3-5-sonnet-20241022-v2:0`
- - `anthropic.claude-3-5-haiku-20241022-v1:0`
- - `anthropic.claude-3-5-sonnet-20240620-v1:0`
- - `anthropic.claude-3-opus-20240229-v1:0`
- - `anthropic.claude-3-sonnet-20240229-v1:0`
- - `anthropic.claude-3-haiku-20240307-v1:0`
- - `anthropic.claude-2-1-v1:0`
- - `anthropic.claude-2-0-v1:0`
- - `anthropic.claude-instant-v1:0`
-- **DeepSeek:**
- - `deepseek.r1-v1:0`
-- **Meta:**
- - `meta.llama3-3-70b-instruct-v1:0`
- - `meta.llama3-2-90b-instruct-v1:0`
- - `meta.llama3-2-11b-instruct-v1:0`
- - `meta.llama3-2-3b-instruct-v1:0`
- - `meta.llama3-2-1b-instruct-v1:0`
- - `meta.llama3-1-405b-instruct-v1:0`
- - `meta.llama3-1-70b-instruct-v1:0`
- - `meta.llama3-1-70b-instruct-latency-optimized-v1:0`
- - `meta.llama3-1-8b-instruct-v1:0`
- - `meta.llama3-70b-instruct-v1:0`
- - `meta.llama3-8b-instruct-v1:0`
-
-Refer to the [Amazon Bedrock documentation](https://docs.aws.amazon.com/bedrock/latest/userguide/models-supported.html) for the most up-to-date list of available models and their IDs. Make sure to use the _model ID_ when configuring Kilo Code, not the model name.
-
## Configuration in Kilo Code
-1. **Open Kilo Code Settings:** Click the gear icon (
+
+
+
+
+ {markdoc &&
+ icon).
-- Click the Settings gear icon (
+
+## Troubleshooting
+
+- **"Invalid API Key":** Double-check that you've entered the API key correctly.
+- **"Model Not Found":** Make sure you're using the correct model ID (`v0-1.0-md`).
+- **Connection Errors:** Verify the Base URL is correct (`https://api.v0.dev/v1`).
+- **Access Issues:** Confirm that your Vercel v0 team account is active and properly set up.
+
+## Additional Resources
+
+- [v0 Official Documentation](https://v0.dev)
+- [Vercel AI Documentation](https://vercel.com/docs/ai)
diff --git a/packages/kilo-docs/docs/providers/vercel-ai-gateway.md b/packages/kilo-docs/pages/ai-providers/vercel-ai-gateway.md
similarity index 96%
rename from packages/kilo-docs/docs/providers/vercel-ai-gateway.md
rename to packages/kilo-docs/pages/ai-providers/vercel-ai-gateway.md
index 5b255e1753b..1eeb750adb7 100644
--- a/packages/kilo-docs/docs/providers/vercel-ai-gateway.md
+++ b/packages/kilo-docs/pages/ai-providers/vercel-ai-gateway.md
@@ -54,7 +54,7 @@ Check the model description in the dropdown for specific capabilities.
## Configuration in Kilo Code
-1. **Open Kilo Code Settings:** Click the gear icon (
+
+3. **Add a Provider Profile:**
+
+ - In the configuration panel, click the **"Add Profile"** button to create a new entry in the list.
+ - Click the dropdown menu on the new entry to select one of your other pre-configured provider profiles (e.g., "OpenAI", "Chutes AI Free Tier").
+
+4. **Set Usage Limits (Optional):**
+
+ - Once a profile is added, you can specify usage limits. If you leave these fields blank, no limit will be enforced for that specific metric.
+ - **Tokens per minute/hour/day:** Limits usage based on the total number of tokens processed (input + output).
+ - **Requests per minute/hour/day:** Limits the total number of API calls made.
+
+5. **Order Your Providers:**
+
+ - The order of the profiles is crucial, as it defines the fallback priority. The provider at the top is used first.
+ - Use the **up and down arrows** next to each profile to change its position in the list.
+
+6. **Add More Providers:** Repeat steps 3-5 to build your complete fallback chain. You can add as many profiles as you have configured.
+
+
+
+## Usage Monitoring
+
+The configuration screen also serves as a dashboard for monitoring the current usage of each provider in your list.
+
+- You can see the tokens and requests used within the last minute, hour, and day.
+- If you need to reset these counters, click the **"Clear Usage Data"** button. This will reset all statistics to zero and immediately re-enable any providers that were temporarily disabled due to exceeding their limits.
+
+## Example Use Case
+
+Imagine you have two profiles configured:
+
+1. **Chutes AI Free:** A free-tier provider with a limit of 5,000 tokens per hour.
+2. **OpenAI Paid:** Your personal pay-as-you-go OpenAI account.
+
+**Configuration:**
+
+- Place "Chutes AI Free" first in the list.
+- Set its "Tokens per hour" limit to `5000`.
+- Place "OpenAI Paid" second in the list, with no limits defined.
+
+**Result:**
+Kilo Code will send all requests to Chutes AI. Once your usage exceeds 5,000 tokens within an hour, it will automatically switch to your OpenAI account. The system will switch back to Chutes AI in the next hour when its quota window has reset.
+
+## Tips and Notes
+
+- **Priority is Key:** Always double-check the order of your profiles. The intended primary or free-tier providers should be at the top.
+- **Error-Based Fallback:** If you don't set any limits for a profile, fallback will only occur if the provider's API returns an error (e.g., a hard rate limit from the service itself, a network issue, or an invalid API key).
+- **No Nesting:** You cannot select another "Virtual Quota Fallback" profile within this provider's configuration, as this would create a circular dependency.
diff --git a/packages/kilo-docs/pages/ai-providers/vscode-lm.md b/packages/kilo-docs/pages/ai-providers/vscode-lm.md
new file mode 100644
index 00000000000..4e0a0ff1783
--- /dev/null
+++ b/packages/kilo-docs/pages/ai-providers/vscode-lm.md
@@ -0,0 +1,45 @@
+---
+sidebar_label: VS Code Language Model API
+---
+
+# Using VS Code Language Model API With Kilo Code
+
+Kilo Code includes _experimental_ support for the [VS Code Language Model API](https://code.visualstudio.com/api/language-extensions/language-model-access). This API allows extensions to provide access to language models directly within VS Code. This means you can potentially use models from:
+
+- **GitHub Copilot:** If you have a Copilot subscription and the extension installed.
+- **Other VS Code Extensions:** Any extension that implements the Language Model API.
+
+**Important:** This integration is highly experimental and may not work as expected. It is dependent on other extensions correctly implementing the VS Code Language Model API.
+
+## Prerequisites
+
+- **VS Code:** The Language Model API is available through VS Code (and is not currently supported by Cursor).
+- **A Language Model Provider Extension:** You need an extension that provides a language model. Examples include:
+ - **GitHub Copilot:** If you have a Copilot subscription, the GitHub Copilot and GitHub Copilot Chat extensions can provide models.
+ - **Other Extensions:** Search the VS Code Marketplace for extensions that mention "Language Model API" or "lm". There may be other experimental extensions available.
+
+## Configuration
+
+1. **Open Kilo Code Settings:** Click the gear icon ({% codicon name="gear" /%}) in the Kilo Code panel.
+2. **Select Provider:** Choose "VS Code LM API" from the "API Provider" dropdown.
+3. **Select Model:** The "Language Model" dropdown will (eventually) list available models. The format is `vendor/family`. For example, if you have Copilot, you might see options like:
+ - `copilot - claude-3.5-sonnet`
+ - `copilot - o3-mini`
+ - `copilot - o1-ga`
+ - `copilot - gemini-2.0-flash`
+
+## Limitations
+
+- **Experimental API:** The VS Code Language Model API is still under development. Expect changes and potential instability.
+- **Extension Dependent:** This feature relies entirely on other extensions providing models. Kilo Code cannot directly control which models are available.
+- **Limited Functionality:** The VS Code Language Model API may not support all the features of other API providers (e.g., image input, streaming, detailed usage information).
+- **No Direct Cost Control:** You are subject to the pricing and terms of the extension providing the model. Kilo Code cannot directly track or limit costs.
+- **GitHub Copilot Rate Limits:** When using the VS Code LM API with GitHub Copilot, be aware that GitHub may impose rate limits on Copilot usage. These limits are controlled by GitHub, not Kilo Code.
+
+## Troubleshooting
+
+- **No Models Appear:**
+ - Ensure you have VS Code installed.
+ - Ensure you have a language model provider extension installed and enabled (e.g., GitHub Copilot, GitHub Copilot Chat).
+ - If using Copilot, make sure that you have sent a Copilot Chat message using the model you would like to use.
+- **Unexpected Behavior:** If you encounter unexpected behavior, it's likely an issue with the underlying Language Model API or the provider extension. Consider reporting the issue to the provider extension's developers.
diff --git a/packages/kilo-docs/pages/ai-providers/xai.md b/packages/kilo-docs/pages/ai-providers/xai.md
new file mode 100644
index 00000000000..309bd4f0c35
--- /dev/null
+++ b/packages/kilo-docs/pages/ai-providers/xai.md
@@ -0,0 +1,49 @@
+---
+sidebar_label: xAI (Grok)
+---
+
+# Using xAI (Grok) With Kilo Code
+
+xAI is the company behind Grok, a large language model known for its conversational abilities and large context window. Grok models are designed to provide helpful, informative, and contextually relevant responses.
+
+**Website:** [https://x.ai/](https://x.ai/)
+
+## Getting an API Key
+
+1. **Sign Up/Sign In:** Go to the [xAI Console](https://console.x.ai/). Create an account or sign in.
+2. **Navigate to API Keys:** Go to the API keys section in your dashboard.
+3. **Create a Key:** Click to create a new API key. Give your key a descriptive name (e.g., "Kilo Code").
+4. **Copy the Key:** **Important:** Copy the API key _immediately_. You will not be able to see it again. Store it securely.
+
+## Configuration in Kilo Code
+
+1. **Open Kilo Code Settings:** Click the gear icon ({% codicon name="gear" /%}) in the Kilo Code panel.
+2. **Select Provider:** Choose "xAI" from the "API Provider" dropdown.
+3. **Enter API Key:** Paste your xAI API key into the "xAI API Key" field.
+4. **Select Model:** Choose your desired Grok model from the "Model" dropdown.
+
+## Reasoning Capabilities
+
+Some models feature specialized reasoning capabilities, allowing them to "think before responding" - particularly useful for complex problem-solving tasks.
+
+### Controlling Reasoning Effort
+
+When using reasoning-enabled models, you can control how hard the model thinks with the `reasoning_effort` parameter:
+
+- `low`: Minimal thinking time, using fewer tokens for quick responses
+- `high`: Maximum thinking time, leveraging more tokens for complex problems
+
+Choose `low` for simple queries that should complete quickly, and `high` for harder problems where response latency is less important.
+
+### Key Features
+
+- **Step-by-Step Problem Solving**: The model thinks through problems methodically before delivering an answer
+- **Math & Quantitative Strength**: Excels at numerical challenges and logic puzzles
+- **Reasoning Trace Access**: The model's thinking process is available via the `reasoning_content` field in the response completion object
+
+## Tips and Notes
+
+- **Context Window:** Most Grok models feature large context windows (up to 131K tokens), allowing you to include substantial amounts of code and context in your prompts.
+- **Vision Capabilities:** Select vision-enabled models (`grok-2-vision-latest`, `grok-2-vision`, etc.) when you need to process or analyze images.
+- **Pricing:** Pricing varies by model, with input costs ranging from $0.3 to $5.0 per million tokens and output costs from $0.5 to $25.0 per million tokens. Refer to the xAI documentation for the most current pricing information.
+- **Performance Tradeoffs:** "Fast" variants typically offer quicker response times but may have higher costs, while "mini" variants are more economical but may have reduced capabilities.
diff --git a/packages/kilo-docs/pages/api/llms.txt.ts b/packages/kilo-docs/pages/api/llms.txt.ts
new file mode 100644
index 00000000000..d3ca9ac8647
--- /dev/null
+++ b/packages/kilo-docs/pages/api/llms.txt.ts
@@ -0,0 +1,85 @@
+import type { NextApiRequest, NextApiResponse } from "next"
+import fs from "fs"
+import path from "path"
+
+/**
+ * Recursively finds all markdown files in a directory
+ */
+function findMarkdownFiles(dir: string, baseDir: string = dir): string[] {
+ const files: string[] = []
+ const entries = fs.readdirSync(dir, { withFileTypes: true })
+
+ for (const entry of entries) {
+ const fullPath = path.join(dir, entry.name)
+
+ if (entry.isDirectory()) {
+ // Skip api directory
+ if (entry.name === "api") continue
+ files.push(...findMarkdownFiles(fullPath, baseDir))
+ } else if (entry.name.endsWith(".md")) {
+ files.push(fullPath)
+ }
+ }
+
+ return files
+}
+
+/**
+ * Converts a file path to a URL path
+ */
+function filePathToUrlPath(filePath: string, pagesDir: string): string {
+ let relativePath = path.relative(pagesDir, filePath)
+ // Remove .md extension
+ relativePath = relativePath.replace(/\.md$/, "")
+ // Handle index files
+ relativePath = relativePath.replace(/\/index$/, "")
+ // Convert to URL path
+ return "/" + relativePath
+}
+
+export default async function handler(req: NextApiRequest, res: NextApiResponse) {
+ if (req.method !== "GET") {
+ return res.status(405).json({ error: "Method not allowed" })
+ }
+
+ try {
+ const pagesDir = path.join(process.cwd(), "pages")
+ const markdownFiles = findMarkdownFiles(pagesDir)
+
+ // Sort files for consistent output
+ markdownFiles.sort()
+
+ const sections: string[] = []
+
+ // Add header
+ sections.push("# Kilo Code Documentation")
+ sections.push("")
+ sections.push(
+ "This file contains the complete documentation for Kilo Code, the leading open source agentic engineering platform.",
+ )
+ sections.push("")
+ sections.push("---")
+ sections.push("")
+
+ for (const filePath of markdownFiles) {
+ const urlPath = filePathToUrlPath(filePath, pagesDir)
+ const content = fs.readFileSync(filePath, "utf-8")
+
+ sections.push(`## Source: ${urlPath}`)
+ sections.push("")
+ sections.push(content)
+ sections.push("")
+ sections.push("---")
+ sections.push("")
+ }
+
+ const output = sections.join("\n")
+
+ res.setHeader("Content-Type", "text/plain; charset=utf-8")
+ res.setHeader("Cache-Control", "public, max-age=3600") // Cache for 1 hour
+ res.status(200).send(output)
+ } catch (error) {
+ console.error("Error generating llms.txt:", error)
+ res.status(500).json({ error: "Internal server error" })
+ }
+}
diff --git a/packages/kilo-docs/pages/api/raw-markdown.ts b/packages/kilo-docs/pages/api/raw-markdown.ts
new file mode 100644
index 00000000000..66dca9424e2
--- /dev/null
+++ b/packages/kilo-docs/pages/api/raw-markdown.ts
@@ -0,0 +1,47 @@
+import type { NextApiRequest, NextApiResponse } from "next"
+import fs from "fs"
+import path from "path"
+
+export default async function handler(req: NextApiRequest, res: NextApiResponse) {
+ if (req.method !== "GET") {
+ return res.status(405).json({ error: "Method not allowed" })
+ }
+
+ const { path: mdPath } = req.query
+
+ if (!mdPath || typeof mdPath !== "string") {
+ return res.status(400).json({ error: "Missing path parameter" })
+ }
+
+ try {
+ // Sanitize the path to prevent directory traversal
+ const sanitizedPath = mdPath.replace(/\.\./g, "").replace(/^\/+/, "")
+
+ // Construct the file path - try .md extension
+ const pagesDir = path.join(process.cwd(), "pages")
+ let filePath = path.join(pagesDir, `${sanitizedPath}.md`)
+
+ // Check if it's an index file
+ if (!fs.existsSync(filePath)) {
+ filePath = path.join(pagesDir, sanitizedPath, "index.md")
+ }
+
+ // Verify the path is within the pages directory
+ const resolvedPath = path.resolve(filePath)
+ if (!resolvedPath.startsWith(path.resolve(pagesDir))) {
+ return res.status(403).json({ error: "Access denied" })
+ }
+
+ if (!fs.existsSync(resolvedPath)) {
+ return res.status(404).json({ error: "File not found" })
+ }
+
+ const content = fs.readFileSync(resolvedPath, "utf-8")
+
+ res.setHeader("Content-Type", "text/plain; charset=utf-8")
+ res.status(200).send(content)
+ } catch (error) {
+ console.error("Error reading markdown file:", error)
+ res.status(500).json({ error: "Internal server error" })
+ }
+}
diff --git a/packages/kilo-docs/docs/advanced-usage/agent-manager.md b/packages/kilo-docs/pages/automate/agent-manager.md
similarity index 98%
rename from packages/kilo-docs/docs/advanced-usage/agent-manager.md
rename to packages/kilo-docs/pages/automate/agent-manager.md
index a2f71224288..bf1497d4958 100644
--- a/packages/kilo-docs/docs/advanced-usage/agent-manager.md
+++ b/packages/kilo-docs/pages/automate/agent-manager.md
@@ -1,3 +1,8 @@
+---
+title: "Agent Manager"
+description: "Manage and orchestrate multiple AI agents"
+---
+
# Agent Manager
The Agent Manager is a dedicated control panel for running and supervising Kilo Code agents as interactive CLI processes. It supports:
diff --git a/packages/kilo-docs/docs/advanced-usage/code-reviews.md b/packages/kilo-docs/pages/automate/code-reviews.md
similarity index 95%
rename from packages/kilo-docs/docs/advanced-usage/code-reviews.md
rename to packages/kilo-docs/pages/automate/code-reviews.md
index de8621bca86..01a334189c6 100644
--- a/packages/kilo-docs/docs/advanced-usage/code-reviews.md
+++ b/packages/kilo-docs/pages/automate/code-reviews.md
@@ -1,12 +1,12 @@
---
-title: Code Reviews
-sidebar_label: Code Reviews
+title: "Code Reviews"
+description: "Automate code reviews with AI assistance"
---
+# Code Reviews
+
Kilo's **Code Reviews** feature automatically analyzes your pull requests using an AI model of your choice. It can review code the moment a PR is opened or updated, surface issues, and provide structured feedback across performance, security, style, and test coverage.
----
-
## What Code Reviews Enable
- Automated AI review on every pull request
@@ -15,8 +15,6 @@ Kilo's **Code Reviews** feature automatically analyzes your pull requests using
- Deep reasoning over changed files, diffs, and repo context
- Customizable review strictness and focus areas
----
-
## Prerequisites
Before enabling Code Reviews:
@@ -24,8 +22,6 @@ Before enabling Code Reviews:
- **GitHub Integration must be configured**
Connect your account via the [Integrations tab](https://app.kilo.ai/integrations) so that the Review Agent can access your repositories.
----
-
## Cost
- **Compute and review time are free during limited beta**
@@ -33,8 +29,6 @@ Before enabling Code Reviews:
- [Kilo Discord](https://discord.gg/hZnd57qN)
- **Kilo Code credits are still used** when the agent performs model reasoning during a review.
----
-
## How to Use
1. Go to the **Review Agent** section in your Kilo Code [personal](https://app.kilo.ai/profile) or [Organization](https://app.kilo.ai/organizations) dashboard.
@@ -57,8 +51,6 @@ Before enabling Code Reviews:
Once configured, the Review Agent will run automatically on PR events.
----
-
## How Code Reviews Work
- When a pull request is opened or updated:
@@ -75,8 +67,6 @@ Once configured, the Review Agent will run automatically on PR events.
Reviews are posted directly in GitHub as if coming from a team reviewer.
----
-
## Review Styles
### Strict
@@ -97,8 +87,6 @@ Reviews are posted directly in GitHub as if coming from a team reviewer.
- Encouraging and lightweight
- Ideal for exploratory PRs, prototypes, or early WIP reviews
----
-
## Focus Areas
You can tailor what the Review Agent pays attention to:
@@ -138,8 +126,6 @@ You can tailor what the Review Agent pays attention to:
- Missing comments
- Unclear APIs
----
-
## Perfect For
The Review Agent is ideal for:
@@ -151,13 +137,10 @@ The Review Agent is ideal for:
- **Security-focused environments requiring strict gates**
- **Educating junior developers with rich explanations**
----
-
## Limitations and Guidance
- Reviews can run for **up to 30 minutes** depending on your setting.
- The agent reviews **only the changed files**, not the entire repository.
- Some highly dynamic or domain-specific code may require additional context in custom instructions.
- The agent will only run on **selected repositories**.
-- **PRs from forks are not supported**. Only pull requests from branches within the same repository can be automatically reviewed.
- During beta, review capacity may be throttled for extremely large PRs.
diff --git a/packages/kilo-docs/docs/features/auto-launch-configuration.md b/packages/kilo-docs/pages/automate/extending/auto-launch.md
similarity index 95%
rename from packages/kilo-docs/docs/features/auto-launch-configuration.md
rename to packages/kilo-docs/pages/automate/extending/auto-launch.md
index 02b860e1fa6..77cd7e046b9 100644
--- a/packages/kilo-docs/docs/features/auto-launch-configuration.md
+++ b/packages/kilo-docs/pages/automate/extending/auto-launch.md
@@ -1,10 +1,15 @@
+---
+title: "Auto-launch Configuration"
+description: "Configure automatic agent launching"
+---
+
# Auto-Launch Configuration
Auto-Launch Configuration allows you to automatically start a Kilo Code task when opening a workspace, with support for specific profiles and modes. This was originally developed as an internal test feature, but we decided to expose it to users in case anyone finds it useful!
-:::info
+{% callout type="info" %}
Auto-Launch Configuration is particularly useful for testing the same prompt against multiple models or project directories.
-:::
+{% /callout %}
## How It Works
@@ -48,7 +53,7 @@ This happens seamlessly in the background, requiring no manual intervention.
- `"ask"` - Questions and explanations
- `"debug"` - Problem diagnosis and troubleshooting
- `"test"` - Testing-focused workflows
- - Custom mode slugs (if you have [custom modes](/features/custom-modes))
+ - Custom mode slugs (if you have [custom modes](/agent-behavior/custom-modes))
## Example Configurations
diff --git a/packages/kilo-docs/pages/automate/extending/local-models.md b/packages/kilo-docs/pages/automate/extending/local-models.md
new file mode 100644
index 00000000000..67919082a67
--- /dev/null
+++ b/packages/kilo-docs/pages/automate/extending/local-models.md
@@ -0,0 +1,44 @@
+---
+title: "Local Models"
+description: "Run AI models locally with Kilo Code"
+---
+
+# Using Local Models
+
+Kilo 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 Kilo Code even without an internet connection.
+- **Cost Savings:** Avoid API usage fees associated with cloud-based models.
+- **Customization:** Experiment with different models and configurations.
+
+**However, using local models also has some drawbacks:**
+
+- **Resource Requirements:** Local models can be resource-intensive, requiring a powerful computer with a good CPU and, ideally, a dedicated GPU.
+- **Setup Complexity:** Setting up local models can be more complex than using cloud-based APIs.
+- **Model Performance:** The performance of local models can vary significantly. While some are excellent, they may not always match the capabilities of the largest, most advanced cloud models.
+- **Limited Features**: Local models (and many online models) often do not support advanced features such as prompt caching, computer use, and others.
+
+## Supported Local Model Providers
+
+Kilo 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.
+
+## Setting Up Local Models
+
+For detailed setup instructions, see:
+
+- [Setting up Ollama](/providers/ollama)
+- [Setting up LM Studio](/providers/lmstudio)
+
+Both providers offer similar capabilities but with different user interfaces and workflows. Ollama provides more control through its command-line interface, while LM Studio offers a more user-friendly graphical interface.
+
+## 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 Kilo 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.
+
+- **Model Not Found:** Ensure you have typed in the name of the model correctly. If you're using Ollama, use the same name that you provide in the `ollama run` command.
diff --git a/packages/kilo-docs/docs/features/shell-integration.md b/packages/kilo-docs/pages/automate/extending/shell-integration.md
similarity index 76%
rename from packages/kilo-docs/docs/features/shell-integration.md
rename to packages/kilo-docs/pages/automate/extending/shell-integration.md
index 059761a98ac..1a3d6ab6599 100644
--- a/packages/kilo-docs/docs/features/shell-integration.md
+++ b/packages/kilo-docs/pages/automate/extending/shell-integration.md
@@ -1,3 +1,8 @@
+---
+title: "Shell Integration"
+description: "Integrate Kilo Code with your shell environment"
+---
+
# Terminal Shell Integration
Terminal Shell Integration is a key feature that enables Kilo Code to execute commands in your terminal and intelligently process their output. This bidirectional communication between the AI and your development environment unlocks powerful automation capabilities.
@@ -31,33 +36,36 @@ Kilo Code provides several settings to fine-tune shell integration. Access these
### Basic Settings
#### Terminal Output Limit
-
+
+{% image src="/docs/img/shell-integration/terminal-output-limit.png" alt="Terminal output limit slider set to 500" width="500" caption="Terminal output limit slider set to 500" /%}
Controls the maximum number of lines captured from terminal output. When exceeded, it keeps 20% of the beginning and 80% of the end with a truncation message in between. This prevents excessive token usage while maintaining context. Default: 500 lines.
Controls the maximum number of lines captured from terminal output. When exceeded, lines are removed from the middle to save tokens. Default: 500 lines.
#### Terminal Shell Integration Timeout
-
+
+{% image src="/docs/img/shell-integration/shell-integration-timeout.png" alt="Terminal shell integration timeout slider set to 15s" width="500" caption="Terminal shell integration timeout slider set to 15s" /%}
Maximum time to wait for shell integration to initialize before executing commands. Increase this value if you experience "Shell Integration Unavailable" errors. Default: 15 seconds.
#### Terminal Command Delay
-
+
+{% image src="/docs/img/shell-integration/terminal-command-delay.png" alt="Terminal command delay slider set to 0ms" width="500" caption="Terminal command delay slider set to 0ms" /%}
Adds a small pause after running commands to help Kilo Code capture all output correctly. This setting can significantly impact shell integration reliability due to VSCode's implementation of terminal integration across different operating systems and shell configurations:
- **Default**: 0ms
- **Common Values**:
- * 0ms: Works best for some users with newer VSCode versions
- * 50ms: Historical default, still effective for many users
- * 150ms: Recommended for PowerShell users
+ - 0ms: Works best for some users with newer VSCode versions
+ - 50ms: Historical default, still effective for many users
+ - 150ms: Recommended for PowerShell users
- **Note**: Different values may work better depending on your:
- * VSCode version
- * Shell customizations (oh-my-zsh, powerlevel10k, etc.)
- * Operating system and environment
+ - VSCode version
+ - Shell customizations (oh-my-zsh, powerlevel10k, etc.)
+ - Operating system and environment
### Advanced Settings
-:::info Important
+{% callout type="info" title="Important" %}
**Terminal restart required for these settings**
Changes to advanced terminal settings only take effect after restarting your terminals. To restart a terminal:
@@ -66,30 +74,35 @@ Changes to advanced terminal settings only take effect after restarting your ter
2. Open a new terminal with Terminal → New Terminal or Ctrl+` (backtick)
Always restart all open terminals after changing any of these settings.
-:::
+{% /callout %}
#### PowerShell Counter Workaround
-
+
+{% image src="/docs/img/shell-integration/power-shell-workaround.png" alt="PowerShell counter workaround checkbox" width="600" caption="PowerShell counter workaround checkbox" /%}
Helps PowerShell run the same command multiple times in a row. Enable this if you notice Kilo Code can't run identical commands consecutively in PowerShell.
#### Clear ZSH EOL Mark
-
+
+{% image src="/docs/img/shell-integration/clear-zsh-eol-mark.png" alt="Clear ZSH EOL mark checkbox" width="600" caption="Clear ZSH EOL mark checkbox" /%}
Prevents ZSH from adding special characters at the end of output lines that can confuse Kilo Code when reading terminal results.
#### Oh My Zsh Integration
-
+
+{% image src="/docs/img/shell-integration/oh-my-zsh.png" alt="Enable Oh My Zsh integration checkbox" width="600" caption="Enable Oh My Zsh integration checkbox" /%}
Makes Kilo Code work better with the popular [Oh My Zsh](https://ohmyz.sh/) shell customization framework. Turn this on if you use Oh My Zsh and experience terminal issues.
#### Powerlevel10k Integration
-
+
+{% image src="/docs/img/shell-integration/power10k.png" alt="Enable Powerlevel10k integration checkbox" width="600" caption="Enable Powerlevel10k integration checkbox" /%}
Improves compatibility if you use the Powerlevel10k theme for ZSH. Turn this on if your fancy terminal prompt causes issues with Kilo Code.
#### ZDOTDIR Handling
-
+
+{% image src="/docs/img/shell-integration/zdotdir.png" alt="Enable ZDOTDIR handling checkbox" width="600" caption="Enable ZDOTDIR handling checkbox" /%}
Helps Kilo Code work with custom ZSH configurations without interfering with your personal shell settings and customizations.
@@ -104,6 +117,7 @@ PowerShell restricts script execution by default. To configure:
3. Set appropriate policy: `Set-ExecutionPolicy RemoteSigned -Scope CurrentUser`
Common policies:
+
- `Restricted`: No scripts allowed (default)
- `RemoteSigned`: Local scripts can run; downloaded scripts need signing
- `Unrestricted`: All scripts run with warnings
@@ -114,21 +128,25 @@ Common policies:
If automatic integration fails, add the appropriate line to your shell configuration:
**Bash** (`~/.bashrc`):
+
```bash
[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash)"
```
**Zsh** (`~/.zshrc`):
+
```bash
[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"
```
**PowerShell** (`$Profile`):
+
```powershell
if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }
```
**Fish** (`~/.config/fish/config.fish`):
+
```fish
string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration-path fish)
```
@@ -138,6 +156,7 @@ string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration
If you use terminal customization tools:
**Powerlevel10k**:
+
```bash
# Add before sourcing powerlevel10k in ~/.zshrc
typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true
@@ -150,6 +169,7 @@ typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true
Confirm shell integration is active with these commands:
**Bash**:
+
```bash
set | grep -i '[16]33;'
echo "$PROMPT_COMMAND" | grep vsc
@@ -157,24 +177,28 @@ trap -p DEBUG | grep vsc
```
**Zsh**:
+
```zsh
functions | grep -i vsc
typeset -p precmd_functions preexec_functions
```
**PowerShell**:
+
```powershell
Get-Command -Name "*VSC*" -CommandType Function
Get-Content Function:\Prompt | Select-String "VSCode"
```
**Fish**:
+
```fish
functions | grep -i vsc
functions fish_prompt | grep -i vsc
```
Visual indicators of active shell integration:
+
1. Shell integration indicator in terminal title bar
2. Command detection highlighting
3. Working directory updates in terminal title
@@ -187,6 +211,7 @@ When using Windows Subsystem for Linux (WSL), there are two distinct ways to use
### Method 1: VSCode Windows with WSL Terminal
In this setup:
+
- VSCode runs natively in Windows
- You use the WSL terminal integration feature in VSCode
- Shell commands are executed through the WSL bridge
@@ -196,6 +221,7 @@ In this setup:
### Method 2: VSCode Running Within WSL
In this setup:
+
- You launch VSCode directly from within WSL using `code .`
- VSCode server runs natively in the Linux environment
- Direct access to Linux filesystem and tools
@@ -204,6 +230,7 @@ In this setup:
- Recommended approach for WSL development
For optimal shell integration with WSL, we recommend:
+
1. Open your WSL distribution
2. Navigate to your project directory
3. Launch VSCode using `code .`
@@ -216,10 +243,12 @@ For optimal shell integration with WSL, we recommend:
For fellow Windows users running Fish terminal within a Cygwin environment, here's how VS Code's shell integration works:
1. **(Optional) Locate the Shell Integration Script:**
- Open your Fish terminal *within VS Code* and run the following command:
+ Open your Fish terminal _within VS Code_ and run the following command:
+
```bash
code --locate-shell-integration-path fish
```
+
This will output the path to the `shellIntegration.fish` script. Note down this path.
2. **Update Your Fish Configuration:**
@@ -239,7 +268,8 @@ For fellow Windows users running Fish terminal within a Cygwin environment, here
# source "/cygdrive/c/Users/YourUser/.vscode/extensions/..../shellIntegration.fish"
end
```
- *Remember to replace the example path with the actual path from Step 1, correctly formatted for Cygwin.*
+
+ _Remember to replace the example path with the actual path from Step 1, correctly formatted for Cygwin._
3. **Configure VS Code Terminal Profile:**
Open your VS Code `settings.json` file (Ctrl+Shift+P -> "Preferences: Open User Settings (JSON)"). Update or add the Fish profile under `terminal.integrated.profiles.windows` like this:
@@ -277,38 +307,42 @@ For fellow Windows users running Fish terminal within a Cygwin environment, here
// ... other settings ...
}
```
- *Note: Using `bash.exe --login -i -c "exec fish"` is often more reliable in Cygwin environments for ensuring the correct environment setup before `fish` starts. However, if that approach doesn't work, try the `fish-direct` profile configuration.*
+
+ _Note: Using `bash.exe --login -i -c "exec fish"` is often more reliable in Cygwin environments for ensuring the correct environment setup before `fish` starts. However, if that approach doesn't work, try the `fish-direct` profile configuration._
4. **Restart VS Code:**
Close and reopen Visual Studio Code completely to apply the changes.
5. **Verify:**
- Open a new Fish terminal in VS Code. The shell integration features (like command decorations, better command history navigation, etc.) should now be active. You can test basic functionality by running simple commands like `echo "Hello from integrated Fish!"`.
+ Open a new Fish terminal in VS Code. The shell integration features (like command decorations, better command history navigation, etc.) should now be active. You can test basic functionality by running simple commands like `echo "Hello from integrated Fish!"`. {% image src="/docs/img/shell-integration/shell-integration-8.png" alt="Fish Cygwin Integration Example" width="600" caption="Fish Cygwin Integration Example" /%}
This setup works reliably on Windows systems using Cygwin, Fish, and the Starship prompt, and should assist users with similar configurations.
-
### Shell Integration Failures After VSCode 1.98
**Issue**: After VSCode updates beyond version 1.98, shell integration may fail with the error "VSCE output start escape sequence (]633;C or ]133;C) not received".
**Solutions**:
+
1. **Set Terminal Command Delay**:
- - Set the Terminal Command Delay to 50ms in Kilo Code settings
- - Restart all terminals after changing this setting
- - This matches older default behavior and may resolve the issue, however some users have reported that a value of 0ms works better. This is a workaround for upstream VSCode problems.
+
+ - Set the Terminal Command Delay to 50ms in Kilo Code settings
+ - Restart all terminals after changing this setting
+ - This matches older default behavior and may resolve the issue, however some users have reported that a value of 0ms works better. This is a workaround for upstream VSCode problems.
2. **Roll Back VSCode Version**:
- - Download VSCode v1.98 from [VSCode Updates](https://code.visualstudio.com/updates/v1_98)
- - Replace your current VSCode installation
- - No backup of Kilo settings needed
+
+ - Download VSCode v1.98 from [VSCode Updates](https://code.visualstudio.com/updates/v1_98)
+ - Replace your current VSCode installation
+ - No backup of Kilo settings needed
3. **WSL-Specific Workaround**:
- - If using WSL, ensure you launch VSCode from within WSL using `code .`
+
+ - If using WSL, ensure you launch VSCode from within WSL using `code .`
4. **ZSH Users**:
- - Try enabling some or all ZSH-related workarounds in Kilo Code settings
- - These settings can help regardless of your operating system
+ - Try enabling some or all ZSH-related workarounds in Kilo Code settings
+ - These settings can help regardless of your operating system
## Known Issues and Workarounds
@@ -340,37 +374,41 @@ This setup works reliably on Windows systems using Cygwin, Fish, and the Starshi
## Troubleshooting Resources
### Checking Debug Logs
+
When shell integration issues occur, check the debug logs:
+
1. Open Help → Toggle Developer Tools → Console
2. Set "Show All Levels" to see all log messages
3. Look for messages containing `[Terminal Process]`
4. Check `preOutput` content in error messages:
- - Empty preOutput (`''`) means VSCode sent no data
- - This indicates a potential VSCode shell integration issue, or an upstream bug that is out of our control
- - The absence of shell integration markers may require adjusting settings to work around possible upstream bugs or local workstation configuration issues related to shell initialization and VSCode's loading of special shell integration hooks
+ - Empty preOutput (`''`) means VSCode sent no data
+ - This indicates a potential VSCode shell integration issue, or an upstream bug that is out of our control
+ - The absence of shell integration markers may require adjusting settings to work around possible upstream bugs or local workstation configuration issues related to shell initialization and VSCode's loading of special shell integration hooks
### Using the VSCode Terminal Integration Test Extension
+
The [VSCode Terminal Integration Test Extension](https://github.com/KJ7LNW/vsce-test-terminal-integration) helps diagnose shell integration issues by testing different settings combinations:
-
1. **When Commands Stall**:
- - If you see "command already running" warnings, click "Reset Stats" to reset the terminal state
- - These warnings indicate shell integration is not working
- - Try different settings combinations until you find one that works
- - If it really gets stuck, restart the extension by closing the window and pressing F5
+
+ - If you see "command already running" warnings, click "Reset Stats" to reset the terminal state
+ - These warnings indicate shell integration is not working
+ - Try different settings combinations until you find one that works
+ - If it really gets stuck, restart the extension by closing the window and pressing F5
2. **Testing Settings**:
- - Systematically try different combinations of:
- * Terminal Command Delay
- * Shell Integration settings
- - Document which combinations succeed or fail
- - This helps identify patterns in shell integration issues
+
+ - Systematically try different combinations of:
+ - Terminal Command Delay
+ - Shell Integration settings
+ - Document which combinations succeed or fail
+ - This helps identify patterns in shell integration issues
3. **Reporting Issues**:
- - Once you find a problematic configuration
- - Document the exact settings combination
- - Note your environment (OS, VSCode version, shell, and any shell prompt customization)
- - Open an issue with these details to help improve shell integration
+ - Once you find a problematic configuration
+ - Document the exact settings combination
+ - Note your environment (OS, VSCode version, shell, and any shell prompt customization)
+ - Open an issue with these details to help improve shell integration
## Support
@@ -379,4 +417,4 @@ If you've followed these steps and are still experiencing problems, please:
1. Check the [Kilo Code GitHub Issues](https://github.com/Kilo-Org/kilocode/issues) to see if others have reported similar problems
2. If not, create a new issue with details about your operating system, VSCode/Cursor version, and the steps you've tried
-For additional help, join our [Discord](https://kilocode.ai/discord).
+For additional help, join our [Discord](https://kilo.ai/discord).
diff --git a/packages/kilo-docs/pages/automate/index.md b/packages/kilo-docs/pages/automate/index.md
new file mode 100644
index 00000000000..8a574a0f560
--- /dev/null
+++ b/packages/kilo-docs/pages/automate/index.md
@@ -0,0 +1,20 @@
+---
+title: "Automate"
+description: "Automate your development workflows with Kilo Code"
+---
+
+# Automate
+
+{% callout type="info" title="Coming Soon" %}
+This page is under construction. Check back soon for comprehensive documentation.
+{% /callout %}
+
+
diff --git a/packages/kilo-docs/docs/advanced-usage/integrations.md b/packages/kilo-docs/pages/automate/integrations.md
similarity index 96%
rename from packages/kilo-docs/docs/advanced-usage/integrations.md
rename to packages/kilo-docs/pages/automate/integrations.md
index e39b46d3fad..b9468a8f3ba 100644
--- a/packages/kilo-docs/docs/advanced-usage/integrations.md
+++ b/packages/kilo-docs/pages/automate/integrations.md
@@ -1,20 +1,18 @@
---
-title: Kilo Integrations
-sidebar_label: Kilo Integrations
+title: "Integrations"
+description: "Overview of Kilo Code integrations"
---
+# Kilo Code Integrations
+
Kilo Integrations lets you connect your GitHub account (and soon, GitLab and Bitbucket) to enable advanced features inside Kilo Code. Once connected, Kilo can access your repositories securely through the **KiloConnect** GitHub App, enabling features like **Cloud Agents** and **Kilo Deploy**.
----
-
## What You Can Do With Integrations
- **Connect GitHub to Kilo Code** in a few clicks
- **Authorize the KiloConnect App** for repo access
- **Enable advanced features** like Cloud Agents and Kilo Deploy
----
-
## Prerequisites
Before connecting:
@@ -23,8 +21,6 @@ Before connecting:
- You need permission to install GitHub Apps for the repositories you want Kilo to access.
- (Optional) If you're connecting an organization, you must be an **org admin** or have app installation permissions.
----
-
## Connecting GitHub to Kilo
### 1. Open the Integrations Page
@@ -54,8 +50,6 @@ Once approved:
- Github will show a **Connected** status.
- Your Kilo workspace can now access GitHub repositories securely.
----
-
## What Happens After Connecting
Once GitHub is connected, the following features will be enabled in Kilo:
diff --git a/packages/kilo-docs/docs/features/mcp/mcp-vs-api.md b/packages/kilo-docs/pages/automate/mcp/mcp-vs-api.md
similarity index 67%
rename from packages/kilo-docs/docs/features/mcp/mcp-vs-api.md
rename to packages/kilo-docs/pages/automate/mcp/mcp-vs-api.md
index 92ba206aa7f..25d1484c214 100644
--- a/packages/kilo-docs/docs/features/mcp/mcp-vs-api.md
+++ b/packages/kilo-docs/pages/automate/mcp/mcp-vs-api.md
@@ -1,6 +1,6 @@
---
-title: MCP vs API
-sidebar_label: MCP vs API
+title: "MCP vs API"
+description: "Comparing MCP to traditional APIs"
---
# MCP vs REST APIs: A Fundamental Distinction
@@ -9,14 +9,14 @@ Comparing REST APIs to the Model Context Protocol (MCP) is a category error. The
## Architectural Differences
-| Feature | MCP | REST APIs |
-|---------|-----|-----------|
-| State Management | **Stateful** - maintains context across interactions | **Stateless** - each request is independent |
-| Connection Type | Persistent, bidirectional connections | One-way request/response |
-| Communication Style | JSON-RPC based with ongoing sessions | HTTP-based with discrete requests |
-| Context Handling | Context is intrinsic to the protocol | Context must be manually managed |
-| Tool Discovery | Runtime discovery of available tools | Design-time integration requiring prior knowledge |
-| Integration Approach | Runtime integration with dynamic capabilities | Design-time integration requiring code changes |
+| Feature | MCP | REST APIs |
+| -------------------- | ---------------------------------------------------- | ------------------------------------------------- |
+| State Management | **Stateful** - maintains context across interactions | **Stateless** - each request is independent |
+| Connection Type | Persistent, bidirectional connections | One-way request/response |
+| Communication Style | JSON-RPC based with ongoing sessions | HTTP-based with discrete requests |
+| Context Handling | Context is intrinsic to the protocol | Context must be manually managed |
+| Tool Discovery | Runtime discovery of available tools | Design-time integration requiring prior knowledge |
+| Integration Approach | Runtime integration with dynamic capabilities | Design-time integration requiring code changes |
## Different Layers, Different Purposes
@@ -43,23 +43,23 @@ MCP enables an AI to discover and use tools at runtime:
```json
// AI discovers available tools
{
- "tools": [
- {
- "name": "readFile",
- "description": "Reads content from a file",
- "parameters": {
- "path": { "type": "string", "description": "File path" }
- }
- },
- {
- "name": "createTicket",
- "description": "Creates a ticket in issue tracker",
- "parameters": {
- "title": { "type": "string" },
- "description": { "type": "string" }
- }
- }
- ]
+ "tools": [
+ {
+ "name": "readFile",
+ "description": "Reads content from a file",
+ "parameters": {
+ "path": { "type": "string", "description": "File path" }
+ }
+ },
+ {
+ "name": "createTicket",
+ "description": "Creates a ticket in issue tracker",
+ "parameters": {
+ "title": { "type": "string" },
+ "description": { "type": "string" }
+ }
+ }
+ ]
}
```
@@ -70,11 +70,13 @@ This "plug-and-play" capability allows new tools to be added without redeploying
Consider a task requiring multiple services: "Check recent commits, create a JIRA ticket for the bug fix, and post to Slack."
**REST-based approach**:
+
- Requires separate integrations for Git, JIRA, and Slack APIs
- Needs custom code to manage context between calls
- Breaks if any service changes its API
**MCP-based approach**:
+
- One unified protocol for all tools
- Maintains context across the entire workflow
- New tools can be swapped in without code changes
@@ -94,4 +96,4 @@ MCP creates a universal connector between Kilo Code and external services, with
MCP doesn't replace REST APIs - it builds upon them. REST excels at providing discrete services, while MCP excels at orchestrating those services for AI agents.
-The critical distinction is that MCP is AI-native: it treats the model as a first-class user, providing the contextual, stateful interaction layer that AI agents need to function effectively in complex environments.
\ No newline at end of file
+The critical distinction is that MCP is AI-native: it treats the model as a first-class user, providing the contextual, stateful interaction layer that AI agents need to function effectively in complex environments.
diff --git a/packages/kilo-docs/docs/features/mcp/overview.md b/packages/kilo-docs/pages/automate/mcp/overview.md
similarity index 97%
rename from packages/kilo-docs/docs/features/mcp/overview.md
rename to packages/kilo-docs/pages/automate/mcp/overview.md
index 5938c8e898a..3204ac0bf61 100644
--- a/packages/kilo-docs/docs/features/mcp/overview.md
+++ b/packages/kilo-docs/pages/automate/mcp/overview.md
@@ -1,6 +1,6 @@
---
-title: MCP Overview
-sidebar_label: MCP Overview
+title: "MCP Overview"
+description: "Overview of the Model Context Protocol"
---
# Model Context Protocol (MCP)
diff --git a/packages/kilo-docs/pages/automate/mcp/server-transports.md b/packages/kilo-docs/pages/automate/mcp/server-transports.md
new file mode 100644
index 00000000000..b8dc6eb8964
--- /dev/null
+++ b/packages/kilo-docs/pages/automate/mcp/server-transports.md
@@ -0,0 +1,199 @@
+---
+title: "Server Transports"
+description: "Understanding MCP server transport options"
+---
+
+# MCP Server Transports: STDIO & SSE
+
+Model Context Protocol (MCP) supports two primary transport mechanisms for communication between Kilo Code and MCP servers: Standard Input/Output (STDIO) and Server-Sent Events (SSE). Each has distinct characteristics, advantages, and use cases.
+
+## STDIO Transport
+
+STDIO transport runs locally on your machine and communicates via standard input/output streams.
+
+### How STDIO Transport Works
+
+1. The client (Kilo Code) spawns an MCP server as a child process
+2. Communication happens through process streams: client writes to server's STDIN, server responds to STDOUT
+3. Each message is delimited by a newline character
+4. Messages are formatted as JSON-RPC 2.0
+
+```
+Client Server
+ | |
+ |---- JSON message ------>| (via STDIN)
+ | | (processes request)
+ |<---- JSON message ------| (via STDOUT)
+ | |
+```
+
+### STDIO Characteristics
+
+- **Locality**: Runs on the same machine as Kilo Code
+- **Performance**: Very low latency and overhead (no network stack involved)
+- **Simplicity**: Direct process communication without network configuration
+- **Relationship**: One-to-one relationship between client and server
+- **Security**: Inherently more secure as no network exposure
+
+### When to Use STDIO
+
+STDIO transport is ideal for:
+
+- Local integrations and tools running on the same machine
+- Security-sensitive operations
+- Low-latency requirements
+- Single-client scenarios (one Kilo Code instance per server)
+- Command-line tools or IDE extensions
+
+### STDIO Implementation Example
+
+```typescript
+import { Server } from "@modelcontextprotocol/sdk/server/index.js"
+import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
+
+const server = new Server({ name: "local-server", version: "1.0.0" })
+// Register tools...
+
+// Use STDIO transport
+const transport = new StdioServerTransport(server)
+transport.listen()
+```
+
+## SSE Transport
+
+Server-Sent Events (SSE) transport runs on a remote server and communicates over HTTP/HTTPS.
+
+### How SSE Transport Works
+
+1. The client (Kilo Code) connects to the server's SSE endpoint via HTTP GET request
+2. This establishes a persistent connection where the server can push events to the client
+3. For client-to-server communication, the client makes HTTP POST requests to a separate endpoint
+4. Communication happens over two channels:
+ - Event Stream (GET): Server-to-client updates
+ - Message Endpoint (POST): Client-to-server requests
+
+```
+Client Server
+ | |
+ |---- HTTP GET /events ----------->| (establish SSE connection)
+ |<---- SSE event stream -----------| (persistent connection)
+ | |
+ |---- HTTP POST /message --------->| (client request)
+ |<---- SSE event with response ----| (server response)
+ | |
+```
+
+### SSE Characteristics
+
+- **Remote Access**: Can be hosted on a different machine from Kilo Code
+- **Scalability**: Can handle multiple client connections concurrently
+- **Protocol**: Works over standard HTTP (no special protocols needed)
+- **Persistence**: Maintains a persistent connection for server-to-client messages
+- **Authentication**: Can use standard HTTP authentication mechanisms
+
+### When to Use SSE
+
+SSE transport is better for:
+
+- Remote access across networks
+- Multi-client scenarios
+- Public services
+- Centralized tools that many users need to access
+- Integration with web services
+
+### SSE Implementation Example
+
+```typescript
+import { Server } from "@modelcontextprotocol/sdk/server/index.js"
+import { SSEServerTransport } from "@modelcontextprotocol/sdk/server/sse.js"
+import express from "express"
+
+const app = express()
+const server = new Server({ name: "remote-server", version: "1.0.0" })
+// Register tools...
+
+// Use SSE transport
+const transport = new SSEServerTransport(server)
+app.use("/mcp", transport.requestHandler())
+app.listen(3000, () => {
+ console.log("MCP server listening on port 3000")
+})
+```
+
+## Local vs. Hosted: Deployment Aspects
+
+The choice between STDIO and SSE transports directly impacts how you'll deploy and manage your MCP servers.
+
+### STDIO: Local Deployment Model
+
+STDIO servers run locally on the same machine as Kilo Code, which has several important implications:
+
+- **Installation**: The server executable must be installed on each user's machine
+- **Distribution**: You need to provide installation packages for different operating systems
+- **Updates**: Each instance must be updated separately
+- **Resources**: Uses the local machine's CPU, memory, and disk
+- **Access Control**: Relies on the local machine's filesystem permissions
+- **Integration**: Easy integration with local system resources (files, processes)
+- **Execution**: Starts and stops with Kilo Code (child process lifecycle)
+- **Dependencies**: Any dependencies must be installed on the user's machine
+
+#### Practical Example
+
+A local file search tool using STDIO would:
+
+- Run on the user's machine
+- Have direct access to the local filesystem
+- Start when needed by Kilo Code
+- Not require network configuration
+- Need to be installed alongside Kilo Code or via a package manager
+
+### SSE: Hosted Deployment Model
+
+SSE servers can be deployed to remote servers and accessed over the network:
+
+- **Installation**: Installed once on a server, accessed by many users
+- **Distribution**: Single deployment serves multiple clients
+- **Updates**: Centralized updates affect all users immediately
+- **Resources**: Uses server resources, not local machine resources
+- **Access Control**: Managed through authentication and authorization systems
+- **Integration**: More complex integration with user-specific resources
+- **Execution**: Runs as an independent service (often continuously)
+- **Dependencies**: Managed on the server, not on user machines
+
+#### Practical Example
+
+A database query tool using SSE would:
+
+- Run on a central server
+- Connect to databases with server-side credentials
+- Be continuously available for multiple users
+- Require proper network security configuration
+- Be deployed using container or cloud technologies
+
+### Hybrid Approaches
+
+Some scenarios benefit from a hybrid approach:
+
+1. **STDIO with Network Access**: A local STDIO server that acts as a proxy to remote services
+2. **SSE with Local Commands**: A remote SSE server that can trigger operations on the client machine through callbacks
+3. **Gateway Pattern**: STDIO servers for local operations that connect to SSE servers for specialized functions
+
+## Choosing Between STDIO and SSE
+
+| Consideration | STDIO | SSE |
+| -------------------- | ------------------------ | ----------------------------------- |
+| **Location** | Local machine only | Local or remote |
+| **Clients** | Single client | Multiple clients |
+| **Performance** | Lower latency | Higher latency (network overhead) |
+| **Setup Complexity** | Simpler | More complex (requires HTTP server) |
+| **Security** | Inherently secure | Requires explicit security measures |
+| **Network Access** | Not needed | Required |
+| **Scalability** | Limited to local machine | Can distribute across network |
+| **Deployment** | Per-user installation | Centralized installation |
+| **Updates** | Distributed updates | Centralized updates |
+| **Resource Usage** | Uses client resources | Uses server resources |
+| **Dependencies** | Client-side dependencies | Server-side dependencies |
+
+## Configuring Transports in Kilo Code
+
+For detailed information on configuring STDIO and SSE transports in Kilo Code, including example configurations, see the [Understanding Transport Types](/features/mcp/using-mcp-in-kilo-code#understanding-transport-types) section in the Using MCP in Kilo Code guide.
diff --git a/packages/kilo-docs/docs/features/mcp/using-mcp-in-cli.md b/packages/kilo-docs/pages/automate/mcp/using-in-cli.md
similarity index 97%
rename from packages/kilo-docs/docs/features/mcp/using-mcp-in-cli.md
rename to packages/kilo-docs/pages/automate/mcp/using-in-cli.md
index b19295c6282..9dcec693ba5 100644
--- a/packages/kilo-docs/docs/features/mcp/using-mcp-in-cli.md
+++ b/packages/kilo-docs/pages/automate/mcp/using-in-cli.md
@@ -1,6 +1,6 @@
---
-title: Using MCP in the CLI
-sidebar_label: Using MCP in CLI
+title: "Using MCP in CLI"
+description: "How to use MCP servers in the CLI"
---
# Using MCP in the CLI
diff --git a/packages/kilo-docs/docs/features/mcp/using-mcp-in-kilo-code.md b/packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md
similarity index 85%
rename from packages/kilo-docs/docs/features/mcp/using-mcp-in-kilo-code.md
rename to packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md
index 01bc384f0be..2913200e200 100644
--- a/packages/kilo-docs/docs/features/mcp/using-mcp-in-kilo-code.md
+++ b/packages/kilo-docs/pages/automate/mcp/using-in-kilo-code.md
@@ -1,16 +1,13 @@
---
-title: Using MCP in Kilo Code
-sidebar_label: Using MCP in Kilo Code
+title: "Using MCP in Kilo Code"
+description: "How to use MCP servers in Kilo Code"
---
# Using MCP in Kilo Code
Model Context Protocol (MCP) extends Kilo Code's capabilities by connecting to external tools and services. This guide covers everything you need to know about using MCP with Kilo Code.
-
+{% image src="/docs/img/using-mcp-in-kilo-code/mcp-installed-config.png" alt="Edit Global MCP and Edit Project MCP buttons" width="600" caption="Edit Global MCP and Edit Project MCP buttons" /%}
Both files use a JSON format with a `mcpServers` object containing named server configurations:
@@ -148,18 +145,18 @@ SSE configuration example:
### Deleting a Server
-1. Press the
+{% image src="/docs/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-5.png" alt="Delete confirmation box" width="400" caption="Delete confirmation box" /%}
### Restarting a Server
-1. Press the
+{% image src="/docs/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-6.png" alt="Network Timeout pulldown" width="400" caption="Network Timeout pulldown" /%}
### Auto Approve Tools
@@ -177,7 +174,7 @@ MCP tool auto-approval works on a per-tool basis and is disabled by default. To
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
-
+{% image src="/docs/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-7.png" alt="Always allow checkbox for MCP tools" width="120" caption="Always allow checkbox for MCP tools" /%}
When enabled, Kilo Code will automatically approve this specific tool without prompting. Note that the global "Use MCP servers" setting takes precedence - if it's disabled, no MCP tools will be auto-approved.
@@ -235,7 +232,7 @@ This Windows-specific configuration:
- The `-y` flag automatically answers "yes" to any prompts during installation
- Runs the `@modelcontextprotocol/server-puppeteer` package which provides browser automation capabilities
-:::note
+{% callout type="note" %}
For macOS or Linux, you would use a different configuration:
```json
@@ -249,6 +246,6 @@ For macOS or Linux, you would use a different configuration:
}
```
-:::
+{% /callout %}
The same approach can be used for other MCP servers on Windows, adjusting the package name as needed for different server types.
diff --git a/packages/kilo-docs/docs/features/mcp/what-is-mcp.md b/packages/kilo-docs/pages/automate/mcp/what-is-mcp.md
similarity index 95%
rename from packages/kilo-docs/docs/features/mcp/what-is-mcp.md
rename to packages/kilo-docs/pages/automate/mcp/what-is-mcp.md
index 8e957940ed3..92112df74bf 100644
--- a/packages/kilo-docs/docs/features/mcp/what-is-mcp.md
+++ b/packages/kilo-docs/pages/automate/mcp/what-is-mcp.md
@@ -1,6 +1,6 @@
---
-title: What is MCP?
-sidebar_label: What is MCP?
+title: "What is MCP"
+description: "Introduction to the Model Context Protocol"
---
# What is MCP?
@@ -46,4 +46,4 @@ Ready to dig deeper? Check out these guides:
- [MCP Overview](/features/mcp/overview) - A quick glance at the MCP documentation structure
- [Using MCP in Kilo Code](/features/mcp/using-mcp-in-kilo-code) - Get started with MCP in Kilo Code, including creating simple servers
- [MCP vs API](/features/mcp/mcp-vs-api) - Technical advantages compared to traditional APIs
-- [STDIO & SSE Transports](/features/mcp/server-transports) - Local vs. hosted deployment models
\ No newline at end of file
+- [STDIO & SSE Transports](/features/mcp/server-transports) - Local vs. hosted deployment models
diff --git a/packages/kilo-docs/docs/basic-usage/the-chat-interface.md b/packages/kilo-docs/pages/code-with-ai/agents/chat-interface.md
similarity index 80%
rename from packages/kilo-docs/docs/basic-usage/the-chat-interface.md
rename to packages/kilo-docs/pages/code-with-ai/agents/chat-interface.md
index ad5f71b4206..fb68b418b6d 100644
--- a/packages/kilo-docs/docs/basic-usage/the-chat-interface.md
+++ b/packages/kilo-docs/pages/code-with-ai/agents/chat-interface.md
@@ -1,22 +1,21 @@
-import Image from '@site/src/components/Image';
+---
+title: "The Chat Interface"
+description: "Learn how to use the Kilo Code chat interface effectively"
+---
# Chatting with Kilo Code
-:::tip
-
+{% callout type="tip" %}
**Bottom line:** Kilo Code is an AI coding assistant that lives in VS Code. You chat with it in plain English, and it writes, edits, and explains code for you.
+{% /callout %}
-:::
-
-:::note[Prefer quick completions?]
-
+{% callout type="note" title="Prefer quick completions?" %}
If you're typing code in the editor and want AI to finish your line or block, check out [Autocomplete](/basic-usage/autocomplete) instead. Chat is best for larger tasks, explanations, and multi-file changes.
-
-:::
+{% /callout %}
## Quick Setup
-Find the Kilo Code icon () in VS Code's Primary Side Bar. Click it to open the chat panel.
+Find the Kilo Code icon ({% kilo-code-icon /%}) in VS Code's Primary Side Bar. Click it to open the chat panel.
**Lost the panel?** Go to View > Open View... and search for "Kilo Code"
@@ -24,7 +23,7 @@ Find the Kilo Code icon () in VS C
**The key insight:** Just type what you want in normal English. No special commands needed.
-
+ {% image src="/docs/img/modes/modes.png" alt="Using the dropdown menu to switch modes" width="400" /%}
2. **Slash command:** Type `/architect`, `/ask`, `/debug`, or `/code` in the chat input
-
+ {% image src="/docs/img/modes/modes-1.png" alt="Using slash commands to switch modes" width="400" /%}
3. **Toggle command/Keyboard shortcut:** Use the keyboard shortcut below, applicable to your operating system. Each press cycles through the available modes in sequence, wrapping back to the first mode after reaching the end.
@@ -36,7 +38,7 @@ Four ways to switch modes:
4. **Accept suggestions:** Click on mode switch suggestions that Kilo Code offers when appropriate
-
+ {% image src="/docs/img/modes/modes-2.png" alt="Accepting a mode switch suggestion from Kilo Code" width="400" /%}
## Built-in Modes
@@ -96,4 +98,11 @@ Four ways to switch modes:
## Custom Modes
-Create your own specialized assistants by defining tool access, file permissions, and behavior instructions. Custom modes help enforce team standards or create purpose-specific assistants. See [Custom Modes documentation](/agent-behavior/custom-modes) for setup instructions.
+Create your own specialized assistants by defining tool access, file permissions, and behavior instructions. Custom modes help enforce team standards or create purpose-specific assistants. See [Custom Modes documentation](/features/custom-modes) for setup instructions.
+
+
diff --git a/packages/kilo-docs/docs/advanced-usage/appbuilder.md b/packages/kilo-docs/pages/code-with-ai/app-builder.md
similarity index 97%
rename from packages/kilo-docs/docs/advanced-usage/appbuilder.md
rename to packages/kilo-docs/pages/code-with-ai/app-builder.md
index 51c4e50daaf..684a96b5307 100644
--- a/packages/kilo-docs/docs/advanced-usage/appbuilder.md
+++ b/packages/kilo-docs/pages/code-with-ai/app-builder.md
@@ -1,8 +1,10 @@
---
-title: App Builder
-sidebar_label: App Builder
+title: "App Builder"
+description: "Build complete applications with Kilo Code"
---
+# App Builder
+
Kilo's **App Builder** lets you create end-to-end applications through natural language conversation. Describe what you want to build, watch it come to life in a real-time preview, and deploy directly from your Kilo dashboard. No local environment setup required.
---
diff --git a/packages/kilo-docs/docs/features/codebase-indexing.md b/packages/kilo-docs/pages/code-with-ai/context/codebase-indexing.md
similarity index 90%
rename from packages/kilo-docs/docs/features/codebase-indexing.md
rename to packages/kilo-docs/pages/code-with-ai/context/codebase-indexing.md
index a6e719d80bf..2a302e32efc 100644
--- a/packages/kilo-docs/docs/features/codebase-indexing.md
+++ b/packages/kilo-docs/pages/code-with-ai/context/codebase-indexing.md
@@ -1,14 +1,13 @@
-import Codicon from '@site/src/components/Codicon';
+---
+title: "Codebase Indexing"
+description: "Index your codebase for improved AI understanding"
+---
# Codebase Indexing
-
+{% image src="/docs/img/codebase-indexing/codebase-indexing.png" alt="Codebase Indexing Settings" width="800" caption="Codebase Indexing Settings" /%}
## What It Does
@@ -76,16 +75,16 @@ docker run -p 6333:6333 qdrant/qdrant
**Using Docker Compose:**
```yaml
-version: '3.8'
+version: "3.8"
services:
- qdrant:
- image: qdrant/qdrant
- ports:
- - '6333:6333'
- volumes:
- - qdrant_storage:/qdrant/storage
+ qdrant:
+ image: qdrant/qdrant
+ ports:
+ - "6333:6333"
+ volumes:
+ - qdrant_storage:/qdrant/storage
volumes:
- qdrant_storage:
+ qdrant_storage:
```
### Production Deployment
@@ -102,9 +101,9 @@ For team or production use:
2. Navigate to **Codebase Indexing** section
3. Enable **"Enable Codebase Indexing"** using the toggle switch
4. Configure your embedding provider:
- - **OpenAI**: Enter API key and select model
- - **Gemini**: Enter Google AI API key and select embedding model
- - **Ollama**: Enter base URL and select model
+ - **OpenAI**: Enter API key and select model
+ - **Gemini**: Enter Google AI API key and select embedding model
+ - **Ollama**: Enter base URL and select model
5. Set Qdrant URL and optional API key
6. Configure **Max Search Results** (default: 20, range: 1-100)
7. Click **Save** to start initial indexing
@@ -137,9 +136,9 @@ The interface shows real-time status with color indicators:
- **Markdown Support**: Full support for markdown files and documentation
- **Fallback**: Line-based chunking for unsupported file types
- **Block Sizing**:
- - Minimum: 100 characters
- - Maximum: 1,000 characters
- - Splits large functions intelligently
+ - Minimum: 100 characters
+ - Maximum: 1,000 characters
+ - Splits large functions intelligently
### Automatic File Filtering
diff --git a/packages/kilo-docs/docs/advanced-usage/large-projects.md b/packages/kilo-docs/pages/code-with-ai/context/large-projects.md
similarity index 57%
rename from packages/kilo-docs/docs/advanced-usage/large-projects.md
rename to packages/kilo-docs/pages/code-with-ai/context/large-projects.md
index d52c26bd117..a0aab196f0a 100644
--- a/packages/kilo-docs/docs/advanced-usage/large-projects.md
+++ b/packages/kilo-docs/pages/code-with-ai/context/large-projects.md
@@ -1,27 +1,32 @@
+---
+title: "Large Projects"
+description: "Best practices for using Kilo Code with large codebases"
+---
+
# Working with Large Projects
Kilo 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
-Kilo 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.
+Kilo 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 Kilo Code).
-* The conversation history.
-* The content of any files you mention using `@`.
-* The output of any commands or tools Kilo Code uses.
+- The system prompt (instructions for Kilo Code).
+- The conversation history.
+- The content of any files you mention using `@`.
+- The output of any commands or tools Kilo Code uses.
## Strategies for Managing Context
-1. **Be Specific:** When referring to files or code, use specific file paths and function names. Avoid vague references like "the main file."
+1. **Be Specific:** When referring to files or code, use specific file paths and function names. Avoid vague references like "the main file."
-2. **Use Context Mentions Effectively:** Use `@/path/to/file.ts` to include specific files. Use `@problems` to include current errors and warnings. Use `@` followed by a commit hash to reference specific Git commits.
+2. **Use Context Mentions Effectively:** Use `@/path/to/file.ts` to include specific files. Use `@problems` to include current errors and warnings. Use `@` followed by a commit hash to reference specific Git commits.
-3. **Break Down Tasks:** Divide large tasks into smaller, more manageable sub-tasks. This helps keep the context focused.
+3. **Break Down Tasks:** Divide large tasks into smaller, more manageable sub-tasks. This helps keep the context focused.
-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.
+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:** Kilo 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.
@@ -29,18 +34,20 @@ The context window includes:
## Example: Refactoring a Large File
-Let's say you need to refactor a large TypeScript file (`src/components/MyComponent.tsx`). Here's a possible approach:
+Let's say you need to refactor a large TypeScript file (`src/components/MyComponent.tsx`). Here's a possible approach:
1. **Initial Overview:**
+
```
@/src/components/MyComponent.tsx List the functions and classes in this file.
```
2. **Target Specific Functions:**
+
```
@/src/components/MyComponent.tsx Refactor the `processData` function to use `async/await` instead of Promises.
```
-3. **Iterative Changes:** Make small, incremental changes, reviewing and approving each step.
+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.
\ No newline at end of file
+By breaking down the task and providing specific context, you can work effectively with large files even with a limited context window.
diff --git a/packages/kilo-docs/docs/advanced-usage/memory-bank.md b/packages/kilo-docs/pages/code-with-ai/context/memory-bank.md
similarity index 90%
rename from packages/kilo-docs/docs/advanced-usage/memory-bank.md
rename to packages/kilo-docs/pages/code-with-ai/context/memory-bank.md
index 6243fa547b4..4405441c048 100644
--- a/packages/kilo-docs/docs/advanced-usage/memory-bank.md
+++ b/packages/kilo-docs/pages/code-with-ai/context/memory-bank.md
@@ -1,17 +1,13 @@
+---
+title: "Memory Bank"
+description: "Persistent context storage for long-term projects"
+---
+
# Memory Bank
## Overview
-
- 
+{% image src="/docs/img/custom-modes/custom-modes.png" alt="Overview of custom modes interface" width="600" caption="Overview of custom modes interface" /%}
_Kilo Code's interface for creating and managing custom modes._
@@ -47,7 +52,7 @@ Easily share, back up, and template your custom modes. This feature lets you exp
**Exporting a Mode:**
-1. Navigate to Settings > Agent Behaviour > Modes
+1. Navigate to the Modes view
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
@@ -55,7 +60,7 @@ Easily share, back up, and template your custom modes. This feature lets you exp
**Importing a Mode:**
-1. Click the Import Mode button (upload icon) in the Agent Behaviour > Modes view
+1. Click the Import Mode button (upload icon) in the 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,13 +88,13 @@ 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 Agent Behaviour Tab
+### 2. Using the Prompts Tab
-1. **Open Agent Behaviour Tab:** Click the 
+{% image src="/docs/img/custom-modes/custom-modes-2.png" alt="Custom mode creation interface in the Prompts tab" width="600" caption="Custom mode creation interface in the Prompts tab" /%}
_The custom mode creation interface showing fields for name, slug, description, save location, role definition, available tools, custom instructions._
@@ -99,8 +104,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 Settings > Agent Behaviour > Modes >
+
+The easiest way to create and manage rules is through the built-in UI:
+
+1. Access the rules management interface from the Kilo Code panel
+2. Choose between creating project-specific or global rules
+3. Use the interface to create, edit, or toggle rules
+4. Rules are automatically saved and applied immediately
+
+### Using the File System
+
+To create rules manually:
+
+**For Project Rules:**
+
+1. Create the `.kilocode/rules/` directory if it doesn't already exist
+2. Create a new Markdown file with a descriptive name in this directory
+3. Write your rule using Markdown formatting
+4. Save the file
+
+**For Global Rules:**
+
+1. Create the `~/.kilocode/rules/` directory if it doesn't already exist
+2. Create a new Markdown file with a descriptive name in this directory
+3. Write your rule using Markdown formatting
+4. Save the file
+
+Rules will be automatically applied to all future Kilo Code interactions. Any new changes will be applied immediately.
+
+## Example Rules
+
+### Example 1: Table Formatting
+
+```markdown
+# Tables
+
+When printing tables, always add an exclamation mark to each column header
+```
+
+This simple rule instructs the AI to add exclamation marks to all table column headers when generating tables in your project.
+
+### Example 2: Restricted File Access
+
+```markdown
+# Restricted files
+
+Files in the list contain sensitive data, they MUST NOT be read
+
+- supersecrets.txt
+- credentials.json
+- .env
+```
+
+This rule prevents the AI from reading or accessing sensitive files, even if explicitly requested to do so.
+
+
+
+## Use Cases
+
+Custom rules can be applied to a wide variety of scenarios:
+
+- **Code Style**: Enforce consistent formatting, naming conventions, and documentation styles
+- **Security Controls**: Prevent access to sensitive files or directories
+- **Project Structure**: Define where different types of files should be created
+- **Documentation Requirements**: Specify documentation formats and requirements
+- **Testing Patterns**: Define how tests should be structured
+- **API Usage**: Specify how APIs should be used and documented
+- **Error Handling**: Define error handling conventions
+
+## Examples of Custom Rules
+
+- "Strictly follow code style guide [your project-specific code style guide]"
+- "Always use spaces for indentation, with a width of 4 spaces"
+- "Use camelCase for variable names"
+- "Write unit tests for all new functions"
+- "Explain your reasoning before providing code"
+- "Focus on code readability and maintainability"
+- "Prioritize using the most common library in the community"
+- "When adding new features to websites, ensure they are responsive and accessible"
+
+## Best Practices
+
+- **Be Specific**: Clearly define the scope and intent of each rule
+- **Use Categories**: Organize related rules under common headers
+- **Separate Concerns**: Use different files for different types of rules
+- **Use Examples**: Include examples to illustrate the expected behavior
+- **Keep It Simple**: Rules should be concise and easy to understand
+- **Update Regularly**: Review and update rules as project requirements change
+
+:::tip Pro Tip: File-Based Team Standards
+When working in team environments, placing `.kilocode/rules/codestyle.md` files under version control allows you to standardize Kilo's behavior across your entire development team. This ensures consistent code style, documentation practices, and development workflows for everyone on the project.
+:::
+
+## Limitations
+
+- Rules are applied on a best-effort basis by the AI models
+- Complex rules may require multiple examples for clear understanding
+- Project rules apply only to the project in which they are defined
+- Global rules apply across all projects
+
+## Troubleshooting
+
+If your custom rules aren't being properly followed:
+
+1. **Check rule status in the UI**: Use the rules management interface to verify that your rules are active and properly loaded
+1. **Verify rule formatting**: Ensure that your rules are properly formatted with clear Markdown structure
+1. **Check rule locations**: Ensure that your rules are located in supported locations:
+ - Global rules: `~/.kilocode/rules/` directory
+ - Project rules: `.kilocode/rules/` directory
+ - Legacy files: `.kilocoderules`, `.roorules`, or `.clinerules`
+1. **Rule specificity**: Verify that the rules are specific and unambiguous
+1. **Restart VS Code**: Restart VS Code to ensure the rules are properly loaded
+
+## Related Features
+
+- [Custom Modes](/docs/features/custom-modes)
+- [Custom Instructions](/advanced-usage/custom-instructions)
+- [Settings Management](/docs/features/settings-management)
+- [Auto-Approval Settings](/docs/features/auto-approving-actions)
diff --git a/packages/kilo-docs/pages/code-with-ai/customization/prompt-engineering.md b/packages/kilo-docs/pages/code-with-ai/customization/prompt-engineering.md
new file mode 100644
index 00000000000..dcd1606c6fd
--- /dev/null
+++ b/packages/kilo-docs/pages/code-with-ai/customization/prompt-engineering.md
@@ -0,0 +1,98 @@
+---
+title: "Prompt Engineering"
+description: "Best practices for writing effective prompts"
+---
+
+# Prompt Engineering
+
+Prompt engineering is the art of crafting effective instructions for AI models like Kilo Code. Well-written prompts lead to better results, fewer errors, and a more efficient workflow.
+
+## General Principles
+
+- **Be Clear and Specific:** Clearly state what you want Kilo Code to do. Avoid ambiguity.
+
+ - **Bad:** Fix the code.
+ - **Good:** Fix the bug in the `calculateTotal` function that causes it to return incorrect results.
+
+- **Provide Context:** Use [Context Mentions](/basic-usage/context-mentions) to refer to specific files, folders, or problems.
+
+ - **Good:** `@/src/utils.ts` Refactor the `calculateTotal` function to use async/await.
+
+- **Break Down Tasks:** Divide complex tasks into smaller, well-defined steps.
+
+- **Give Examples:** If you have a specific coding style or pattern in mind, provide examples.
+
+- **Specify Output Format:** If you need the output in a particular format (e.g., JSON, Markdown), specify it in the prompt.
+
+- **Iterate:** Don't be afraid to refine your prompt if the initial results aren't what you expect.
+
+## Thinking vs. Doing
+
+It's often helpful to guide Kilo Code through a "think-then-do" process:
+
+1. **Analyze:** Ask Kilo Code to analyze the current code, identify problems, or plan the approach.
+2. **Plan:** Have Kilo Code outline the steps it will take to complete the task.
+3. **Execute:** Instruct Kilo Code to implement the plan, one step at a time.
+4. **Review:** Carefully review the results of each step before proceeding.
+
+## Using Custom Instructions
+
+You can provide custom instructions to further tailor Kilo Code's behavior. There are two types of custom instructions:
+
+- **Global Custom Instructions:** Apply to all modes.
+- **Mode-Specific Custom Instructions:** Apply only to a specific mode (e.g., Code, Architect, Ask, Debug, or a custom mode).
+
+Custom instructions are added to the system prompt, providing persistent guidance to the AI model. You can use these to:
+
+- Enforce coding style guidelines.
+- Specify preferred libraries or frameworks.
+- Define project-specific conventions.
+- Adjust Kilo Code's tone or personality.
+
+See the [Custom Instructions](/agent-behavior/custom-instructions) section for more details.
+
+## Handling Ambiguity
+
+If your request is ambiguous or lacks sufficient detail, Kilo Code might:
+
+- **Make Assumptions:** It might proceed based on its best guess, which may not be what you intended.
+- **Ask Follow-Up Questions:** It might use the `ask_followup_question` tool to clarify your request.
+
+It's generally better to provide clear and specific instructions from the start to avoid unnecessary back-and-forth.
+
+## Providing Feedback
+
+If Kilo Code doesn't produce the desired results, you can provide feedback by:
+
+- **Rejecting Actions:** Click the "Reject" button when Kilo Code proposes an action you don't want.
+- **Providing Explanations:** When rejecting, explain _why_ you're rejecting the action. This helps Kilo Code learn from its mistakes.
+- **Rewording Your Request:** Try rephrasing your initial task or providing more specific instructions.
+- **Manually Correcting:** If there are a few small issues, you can also directly modify the code before accepting the changes.
+
+## Examples
+
+**Good Prompt:**
+
+> `@/src/components/Button.tsx` Refactor the `Button` component to use the `useState` hook instead of the `useReducer` hook.
+
+**Bad Prompt:**
+
+> Fix the button.
+
+**Good Prompt:**
+
+> Create a new file named `utils.py` and add a function called `calculate_average` that takes a list of numbers and returns their average.
+
+**Bad Prompt:**
+
+> Write some Python code.
+
+**Good Prompt:**
+
+> `@problems` Address all errors and warnings in the current file.
+
+**Bad Prompt:**
+
+> Fix everything.
+
+By following these tips, you can write effective prompts that get the most out of Kilo Code's capabilities.
diff --git a/packages/kilo-docs/docs/agent-behavior/skills.md b/packages/kilo-docs/pages/code-with-ai/customization/skills.md
similarity index 99%
rename from packages/kilo-docs/docs/agent-behavior/skills.md
rename to packages/kilo-docs/pages/code-with-ai/customization/skills.md
index afaab6176c3..59ef48f2894 100644
--- a/packages/kilo-docs/docs/agent-behavior/skills.md
+++ b/packages/kilo-docs/pages/code-with-ai/customization/skills.md
@@ -1,3 +1,8 @@
+---
+title: "Skills"
+description: "Extend Kilo Code capabilities with skills"
+---
+
# Skills
Kilo Code implements [Agent Skills](https://agentskills.io/), a lightweight, open format for extending AI agent capabilities with specialized knowledge and workflows.
diff --git a/packages/kilo-docs/pages/code-with-ai/customization/workflows.md b/packages/kilo-docs/pages/code-with-ai/customization/workflows.md
new file mode 100644
index 00000000000..3dfd7166222
--- /dev/null
+++ b/packages/kilo-docs/pages/code-with-ai/customization/workflows.md
@@ -0,0 +1,96 @@
+---
+title: "Workflows"
+description: "Create automated workflows with Kilo Code"
+---
+
+# Workflows
+
+Workflows automate repetitive tasks by defining step-by-step instructions for Kilo Code to execute. Invoke any workflow by typing `/[workflow-name.md]` in the chat.
+
+{% image src="/docs/img/slash-commands/workflows.png" alt="Workflows tab in Kilo Code" width="600" caption="Workflows tab in Kilo Code" /%}
+
+## Creating Workflows
+
+Workflows are markdown files stored in `.kilocode/workflows/`:
+
+- **Global workflows**: `~/.kilocode/workflows/` (available in all projects)
+- **Project workflows**: `[project]/.kilocode/workflows/` (project-specific)
+
+### Basic Setup
+
+1. Create a `.md` file with step-by-step instructions
+2. Save it in your workflows directory
+3. Type `/filename.md` to execute
+
+### Workflow Capabilities
+
+Workflows can leverage:
+
+- [Built-in tools](/features/tools/tool-use-overview): [`read_file()`](/features/tools/read-file), [`search_files()`](/features/tools/search-files), [`execute_command()`](/features/tools/execute-command)
+- CLI tools: `gh`, `docker`, `npm`, custom scripts
+- [MCP integrations](/features/mcp/overview): Slack, databases, APIs
+- [Mode switching](/basic-usage/using-modes): [`new_task()`](/features/tools/new-task) for specialized contexts
+
+## Common Workflow Patterns
+
+**Release Management**
+
+```markdown
+1. Gather merged PRs since last release
+2. Generate changelog from commit messages
+3. Update version numbers
+4. Create release branch and tag
+5. Deploy to staging environment
+```
+
+**Project Setup**
+
+```markdown
+1. Clone repository template
+2. Install dependencies (`npm install`, `pip install -r requirements.txt`)
+3. Configure environment files
+4. Initialize database/services
+5. Run initial tests
+```
+
+**Code Review Preparation**
+
+```markdown
+1. Search for TODO comments and debug statements
+2. Run linting and formatting
+3. Execute test suite
+4. Generate PR description from recent commits
+```
+
+## Example: PR Submission Workflow
+
+Let's walk through creating a workflow for submitting a pull request. This workflow handles the entire process from code review to deployment notification.
+
+Create a file called `submit-pr.md` in your `.kilocode/workflows` directory:
+
+```markdown
+# Submit PR Workflow
+
+You are helping submit a pull request. Follow these steps:
+
+1. First, use `search_files` to check for any TODO comments or console.log statements that shouldn't be committed
+2. Run tests using `execute_command` with `npm test` or the appropriate test command
+3. If tests pass, stage and commit changes with a descriptive commit message
+4. Push the branch and create a pull request using `gh pr create`
+5. Use `ask_followup_question` to get the PR title and description from the user
+
+Parameters needed (ask if not provided):
+
+- Branch name
+- Reviewers to assign
+```
+
+Now you can trigger this workflow by typing `/submit-pr.md` in the chat. Kilo Code will:
+
+- Scan your code for common issues before committing
+- Run your test suite to catch problems early
+- Handle the Git operations and PR creation
+- Notify your team automatically
+- Set up follow-up tasks for deployment
+
+This saves you from manually running the same 7-step process every time you want to submit code for review.
diff --git a/packages/kilo-docs/pages/code-with-ai/features/autocomplete.md b/packages/kilo-docs/pages/code-with-ai/features/autocomplete.md
new file mode 100644
index 00000000000..c7a2ff8c3b6
--- /dev/null
+++ b/packages/kilo-docs/pages/code-with-ai/features/autocomplete.md
@@ -0,0 +1,18 @@
+---
+title: "Autocomplete"
+description: "AI-powered code autocompletion in Kilo Code"
+---
+
+# Autocomplete
+
+{% callout type="info" title="Coming Soon" %}
+This page is under construction. Check back soon for comprehensive documentation.
+{% /callout %}
+
+
diff --git a/packages/kilo-docs/docs/features/browser-use.md b/packages/kilo-docs/pages/code-with-ai/features/browser-use.md
similarity index 69%
rename from packages/kilo-docs/docs/features/browser-use.md
rename to packages/kilo-docs/pages/code-with-ai/features/browser-use.md
index 8d553eff77d..35253aa6e4d 100644
--- a/packages/kilo-docs/docs/features/browser-use.md
+++ b/packages/kilo-docs/pages/code-with-ai/features/browser-use.md
@@ -1,14 +1,20 @@
+---
+title: "Browser Use"
+description: "Using Kilo Code to interact with web browsers"
+---
+
# Browser Use
Kilo Code provides sophisticated browser automation capabilities that let you interact with websites directly from VS Code. This feature enables testing web applications, automating browser tasks, and capturing screenshots without leaving your development environment.
-:::info Model Support Required
+{% callout type="info" title="Model Support Required" %}
Browser Use within Kilo Code requires the use and advanced agentic model, and has only been tested with Claude Sonnet 3.5, 3.7, and 4
-:::
+{% /callout %}
## How Browser Use Works
By default, Kilo Code uses a built-in browser that:
+
- Launches automatically when you ask Kilo to visit a website
- Captures screenshots of web pages
- Allows Kilo to interact with web elements
@@ -39,13 +45,14 @@ Can you check if my website at https://kilocode.ai is displaying correctly?
Browse http://localhost:3000, scroll down to the bottom of the page and check if the footer information is displaying correctly.
```
-
+{% image src="/docs/features/KiloCodeBrowser.png" alt="Browser use example" width="300" /%}
## How Browser Actions Work
The browser_action tool controls a browser instance that returns screenshots and console logs after each action, allowing you to see the results of interactions.
Key characteristics:
+
- Each browser session must start with `launch` and end with `close`
- Only one browser action can be used per message
- While the browser is active, no other tools can be used
@@ -53,40 +60,42 @@ Key characteristics:
### Available Browser Actions
-| Action | Description | When to Use |
-|--------|-------------|------------|
-| `launch` | Opens a browser at a URL | Starting a new browser session |
-| `click` | Clicks at specific coordinates | Interacting with buttons, links, etc. |
-| `type` | Types text into active element | Filling forms, search boxes |
-| `scroll_down` | Scrolls down by one page | Viewing content below the fold |
-| `scroll_up` | Scrolls up by one page | Returning to previous content |
-| `close` | Closes the browser | Ending a browser session |
+| Action | Description | When to Use |
+| ------------- | ------------------------------ | ------------------------------------- |
+| `launch` | Opens a browser at a URL | Starting a new browser session |
+| `click` | Clicks at specific coordinates | Interacting with buttons, links, etc. |
+| `type` | Types text into active element | Filling forms, search boxes |
+| `scroll_down` | Scrolls down by one page | Viewing content below the fold |
+| `scroll_up` | Scrolls up by one page | Returning to previous content |
+| `close` | Closes the browser | Ending a browser session |
## Browser Use Configuration/Settings
-:::info Default Browser Settings
+{% callout type="info" title="Default Browser Settings" %}
+
- **Enable browser tool**: Enabled
- **Viewport size**: Small Desktop (900x600)
- **Screenshot quality**: 75%
- **Use remote browser connection**: Disabled
-:::
+ {% /callout %}
### Accessing Settings
To change Browser / Computer Use settings in Kilo:
-1. Open Settings by clicking the gear icon
+ {% image src="/docs/img/browser-use/browser-use.png" alt="Browser settings menu" width="600" /%}
### Enable/Disable Browser Use
**Purpose**: Master toggle that enables Kilo to interact with websites using a Puppeteer-controlled browser.
To change this setting:
+
1. Check or uncheck the "Enable browser tool" checkbox within your Browser / Computer Use settings
-
+ {% image src="/docs/img/browser-use/browser-use-2.png" alt="Enable browser tool setting" width="300" /%}
### Viewport Size
@@ -95,15 +104,16 @@ To change this setting:
**Tradeoff**: Higher values provide a larger viewport but increase token usage.
To change this setting:
+
1. Click the dropdown menu under "Viewport size" within your Browser / Computer Use settings
2. Select one of the available options:
- - Large Desktop (1280x800)
- - Small Desktop (900x600) - Default
- - Tablet (768x1024)
- - Mobile (360x640)
-2. Select your desired resolution.
+ - Large Desktop (1280x800)
+ - Small Desktop (900x600) - Default
+ - Tablet (768x1024)
+ - Mobile (360x640)
+3. Select your desired resolution.
-
+ {% image src="/docs/img/browser-use/browser-use-3.png" alt="Viewport size setting" width="600" /%}
### Screenshot Quality
@@ -112,20 +122,23 @@ To change this setting:
**Tradeoff**: Higher values provide clearer screenshots but increase token usage.
To change this setting:
+
1. Adjust the slider under "Screenshot quality" within your Browser / Computer Use settings
2. Set a value between 1-100% (default is 75%)
3. Higher values provide clearer screenshots but increase token usage:
- - 40-50%: Good for basic text-based websites
- - 60-70%: Balanced for most general browsing
- - 80%+: Use when fine visual details are critical
-
+ - 40-50%: Good for basic text-based websites
+ - 60-70%: Balanced for most general browsing
+ - 80%+: Use when fine visual details are critical
+
+ {% image src="/docs/img/browser-use/browser-use-4.png" alt="Screenshot quality setting" width="600" /%}
### Remote Browser Connection
**Purpose**: Connect Kilo to an existing Chrome browser instead of using the built-in browser.
**Benefits**:
+
- Works in containerized environments and remote development workflows
- Maintains authenticated sessions between browser uses
- Eliminates repetitive login steps
@@ -134,10 +147,11 @@ To change this setting:
**Requirements**: Chrome must be running with remote debugging enabled.
To enable this feature:
+
1. Check the "Use remote browser connection" box in Browser / Computer Use settings
2. Click "Test Connection" to verify
-
+ {% image src="/docs/img/browser-use/browser-use-5.png" alt="Remote browser connection setting" width="600" /%}
#### Common Use Cases
@@ -150,16 +164,19 @@ To enable this feature:
Connect to a visible Chrome window to observe Kilo's interactions in real-time:
**macOS**
+
```bash
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug --no-first-run
```
**Windows**
+
```bash
"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir=C:\chrome-debug --no-first-run
```
**Linux**
+
```bash
google-chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug --no-first-run
```
diff --git a/packages/kilo-docs/docs/features/checkpoints.md b/packages/kilo-docs/pages/code-with-ai/features/checkpoints.md
similarity index 67%
rename from packages/kilo-docs/docs/features/checkpoints.md
rename to packages/kilo-docs/pages/code-with-ai/features/checkpoints.md
index bcf77e69e63..6fb006542dc 100644
--- a/packages/kilo-docs/docs/features/checkpoints.md
+++ b/packages/kilo-docs/pages/code-with-ai/features/checkpoints.md
@@ -1,29 +1,36 @@
+---
+title: "Checkpoints"
+description: "Save and restore code states with checkpoints"
+---
+
# Checkpoints
Checkpoints automatically version your workspace files during Kilo Code tasks, enabling non-destructive exploration of AI suggestions and easy recovery from unwanted changes.
Checkpoints let you:
+
- Safely experiment with AI-suggested changes
- Easily recover from undesired modifications
- Compare different implementation approaches
- Revert to previous project states without losing work
-:::info Important Notes
+{% callout type="info" title="Important Notes" %}
+
- **Checkpoints are enabled by default.**
- **Git must be installed** for checkpoints to function - [see installation instructions](#git-installation)
- No GitHub account or repository is required
- No Git personal information configuration is needed
- The shadow Git repository operates independently from your project's existing Git configuration
-:::
+ {% /callout %}
## Configuration Options
Access checkpoint settings in Kilo Code settings under the "Checkpoints" section:
-1. Open Settings by clicking the gear icon
+ {% image src="/docs/img/checkpoints/checkpoints.png" alt="Checkpoint settings in Kilo Code configuration" width="500" /%}
## How Checkpoints Work
@@ -44,10 +51,10 @@ Checkpoints are integrated directly into your workflow through the chat interfac
Checkpoints appear directly in your chat history in two forms:
- **Initial checkpoint** marks your starting project state
-
+ {% image src="/docs/img/checkpoints/checkpoints-1.png" alt="Initial checkpoint indicator in chat" width="500" /%}
- **Regular checkpoints** appear after file modifications or command execution
-
+ {% image src="/docs/img/checkpoints/checkpoints-2.png" alt="Regular checkpoint indicator in chat" width="500" /%}
Each checkpoint provides two primary functions:
@@ -58,16 +65,16 @@ To compare your current workspace with a previous checkpoint:
1. Locate the checkpoint in your chat history
2. Click the checkpoint's `View Differences` button
-
+ {% image src="/docs/img/checkpoints/checkpoints-6.png" alt="View Differences button interface" width="100" /%}
3. Review the differences in the comparison view:
- - Added lines are highlighted in green
- - Removed lines are highlighted in red
- - Modified files are listed with detailed changes
- - Renamed and moved files are tracked with their path changes
- - New or deleted files are clearly marked
+ - Added lines are highlighted in green
+ - Removed lines are highlighted in red
+ - Modified files are listed with detailed changes
+ - Renamed and moved files are tracked with their path changes
+ - New or deleted files are clearly marked
-
+{% image src="/docs/img/checkpoints/checkpoints-3.png" alt="View differences option for checkpoints" width="800" /%}
### Restoring Checkpoints
@@ -75,16 +82,15 @@ To restore a project to a previous checkpoint state:
1. Locate the checkpoint in your chat history
2. Click the checkpoint's `Restore Checkpoint` button
-
+ {% image src="/docs/img/checkpoints/checkpoints-7.png" alt="Restore checkpoint button interface" width="100" /%}
3. Choose one of these restoration options:
-
-
- - **Restore Files Only** - Reverts only workspace files to checkpoint state without modifying conversation history. Ideal for comparing alternative implementations while maintaining chat context, allowing you to seamlessly switch between different project states. This option does not require confirmation and lets you quickly switch between different implementations.
-
- - **Restore Files & Task** - Reverts both workspace files AND removes all subsequent conversation messages. Use when you want to completely reset both your code and conversation back to the checkpoint's point in time. This option requires confirmation in a dialog as it cannot be undone.
+ {% image src="/docs/img/checkpoints/checkpoints-4.png" alt="Restore checkpoint option" width="300" /%}
-
+ - **Restore Files Only** - Reverts only workspace files to checkpoint state without modifying conversation history. Ideal for comparing alternative implementations while maintaining chat context, allowing you to seamlessly switch between different project states. This option does not require confirmation and lets you quickly switch between different implementations.
+ - **Restore Files & Task** - Reverts both workspace files AND removes all subsequent conversation messages. Use when you want to completely reset both your code and conversation back to the checkpoint's point in time. This option requires confirmation in a dialog as it cannot be undone.
+
+ {% image src="/docs/img/checkpoints/checkpoints-9.png" alt="Confirmation dialog for restoring checkpoint with files & task" width="300" /%}
### Limitations and Considerations
@@ -102,16 +108,18 @@ The checkpoint system consists of:
1. **Shadow Git Repository**: A separate Git repository created specifically for checkpoint tracking that functions as the persistent storage mechanism for checkpoint state.
2. **Checkpoint Service**: Handles Git operations and state management through:
- - Repository initialization
- - Checkpoint creation and storage
- - Diff computation
- - State restoration
+
+ - Repository initialization
+ - Checkpoint creation and storage
+ - Diff computation
+ - State restoration
3. **UI Components**: Interface elements displayed in the chat that enable interaction with checkpoints.
### Restoration Process
When restoration executes, Kilo Code:
+
- Performs a hard reset to the specified checkpoint commit
- Copies all files from the shadow repository to your workspace
- Updates internal checkpoint tracking state
@@ -123,6 +131,7 @@ Checkpoints are task-scoped, meaning they are specific to a single task.
### Diff Computation
Checkpoint comparison uses Git's underlying diff capabilities to produce structured file differences:
+
- Modified files show line-by-line changes
- Binary files are properly detected and handled
- Renamed and moved files are tracked correctly
@@ -135,6 +144,7 @@ The checkpoint system uses intelligent file exclusion to track only relevant fil
#### Built-in Exclusions
The system has comprehensive built-in exclusion patterns that automatically ignore:
+
- Build artifacts and dependency directories (`node_modules/`, `dist/`, `build/`)
- Media files and binary assets (images, videos, audio)
- Cache and temporary files (`.cache/`, `.tmp/`, `.bak`)
@@ -147,6 +157,7 @@ These patterns are written to the shadow repository's `.git/info/exclude` file d
#### .gitignore Support
The checkpoint system respects `.gitignore` patterns in your workspace:
+
- Files excluded by `.gitignore` won't trigger checkpoint creation
- Excluded files won't appear in checkpoint diffs
- Standard Git ignore rules apply when staging file changes
@@ -154,6 +165,7 @@ The checkpoint system respects `.gitignore` patterns in your workspace:
#### .kilocodeignore Behavior
The `.kilocodeignore` file (which controls AI access to files) is separate from checkpoint tracking:
+
- Files excluded by `.kilocodeignore` but not by `.gitignore` will still be checkpointed
- Changes to AI-inaccessible files can still be restored through checkpoints
@@ -162,6 +174,7 @@ This separation is intentional, as `.kilocodeignore` limits which files the AI c
#### Nested Git Repositories
The checkpoint system includes special handling for nested Git repositories:
+
- Temporarily renames nested `.git` directories to `.git_disabled` during operations
- Restores them after operations complete
- Allows proper tracking of files in nested repositories
@@ -178,59 +191,67 @@ Checkpoints require Git to be installed on your system. The implementation uses
### macOS
1. **Install with Homebrew (recommended)**:
- ```
- brew install git
- ```
+
+ ```
+ brew install git
+ ```
2. **Alternative: Install with Xcode Command Line Tools**:
- ```
- xcode-select --install
- ```
+
+ ```
+ xcode-select --install
+ ```
3. **Verify installation**:
- - Open Terminal
- - Type `git --version`
- - You should see a version number like `git version 2.40.0`
+ - Open Terminal
+ - Type `git --version`
+ - You should see a version number like `git version 2.40.0`
### Windows
1. **Download Git for Windows**:
- - Visit https://git-scm.com/download/win
- - The download should start automatically
+
+ - Visit https://git-scm.com/download/win
+ - The download should start automatically
2. **Run the installer**:
- - Accept the license agreement
- - Choose installation location (default is recommended)
- - Select components (default options are typically sufficient)
- - Choose the default editor
- - Choose how to use Git from the command line (recommended: Git from the command line and also from 3rd-party software)
- - Configure line ending conversions (recommended: Checkout Windows-style, commit Unix-style)
- - Complete the installation
+
+ - Accept the license agreement
+ - Choose installation location (default is recommended)
+ - Select components (default options are typically sufficient)
+ - Choose the default editor
+ - Choose how to use Git from the command line (recommended: Git from the command line and also from 3rd-party software)
+ - Configure line ending conversions (recommended: Checkout Windows-style, commit Unix-style)
+ - Complete the installation
3. **Verify installation**:
- - Open Command Prompt or PowerShell
- - Type `git --version`
- - You should see a version number like `git version 2.40.0.windows.1`
+ - Open Command Prompt or PowerShell
+ - Type `git --version`
+ - You should see a version number like `git version 2.40.0.windows.1`
### Linux
**Debian/Ubuntu**:
+
```
sudo apt update
sudo apt install git
```
**Fedora**:
+
```
sudo dnf install git
```
**Arch Linux**:
+
```
sudo pacman -S git
```
**Verify installation**:
+
- Open Terminal
- Type `git --version`
- You should see a version number
diff --git a/packages/kilo-docs/docs/features/code-actions.md b/packages/kilo-docs/pages/code-with-ai/features/code-actions.md
similarity index 81%
rename from packages/kilo-docs/docs/features/code-actions.md
rename to packages/kilo-docs/pages/code-with-ai/features/code-actions.md
index 4e72655b00d..c36e900e7f6 100644
--- a/packages/kilo-docs/docs/features/code-actions.md
+++ b/packages/kilo-docs/pages/code-with-ai/features/code-actions.md
@@ -1,18 +1,12 @@
-import Image from '@site/src/components/Image';
+---
+title: "Code Actions"
+description: "Quick code actions and refactoring with Kilo Code"
+---
# Code Actions
Code Actions are a powerful feature of VS Code that provide quick fixes, refactorings, and other code-related suggestions directly within the editor. Kilo Code integrates with this system to offer AI-powered assistance for common coding tasks.
-:::tip Code Actions vs Autocomplete
-**Code Actions** and **Autocomplete** are two different ways Kilo Code can assist you:
-
-- **Code Actions** (this page) are **explicit and user-triggered**. You invoke them via the lightbulb icon, right-click context menu, or keyboard shortcut (`Ctrl+.` / `Cmd+.`). They operate on selected code and open a conversation in the chat panel.
-- **[Autocomplete](/basic-usage/autocomplete)** is **inline and automatic**. It suggests completions as you type, appearing as ghost text directly in the editor. You accept suggestions with `Tab`.
-
-Use Code Actions when you want to explain, fix, or improve existing code. Use Autocomplete when you want AI to help you write new code as you type.
-:::
-
## What are Code Actions?
Code Actions appear as a lightbulb icon (💡) in the editor gutter (the area to the left of the line numbers). They can also be accessed via the right-click context menu, or via keyboard shortcut. They are triggered when:
@@ -23,7 +17,7 @@ Code Actions appear as a lightbulb icon (💡) in the editor gutter (the area to
Clicking the lightbulb, right-clicking and selecting "Kilo Code", or using the keyboard shortcut (`Ctrl+.` or `Cmd+.` on macOS, by default), displays a menu of available actions.
-
+{% image src="/docs/img/fast-edits/fast-edits-5.png" alt="Kilo Code settings showing Enable editing through diffs" width="500" /%}
+
1. **Faster File Editing**: Kilo modifies files more quickly by applying only the necessary changes.
2. **Prevents Truncated Writes**: The system automatically detects and rejects attempts by the AI to write incomplete file content, which can happen with large files or complex instructions. This helps prevent corrupted files.
-:::note Disabling Fast Edits
+{% callout type="note" title="Disabling Fast Edits" %}
If you uncheck **Enable editing through diffs**, Kilo will revert to writing the entire file content for every edit using the [`write_to_file`](/features/tools/write-to-file) tool, instead of applying targeted changes with [`apply_diff`](/features/tools/apply-diff). This full-write approach is generally slower for modifying existing files and leads to higher token usage.
-:::
+{% /callout %}
## Match Precision
This slider controls how closely the code sections identified by the AI must match the actual code in your file before a change is applied.
-
+{% image src="/docs/img/fast-edits/fast-edits-4.png" alt="Kilo Code settings showing Enable editing through diffs checkbox and Match precision slider" width="500" /%}
-* **100% (Default)**: Requires an exact match. This is the safest option, minimizing the risk of incorrect changes.
-* **Lower Values (80%-99%)**: Allows for "fuzzy" matching. Kilo can apply changes even if the code section has minor differences from what the AI expected. This can be useful if the file has been slightly modified, but **increases the risk** of applying changes in the wrong place.
+- **100% (Default)**: Requires an exact match. This is the safest option, minimizing the risk of incorrect changes.
+- **Lower Values (80%-99%)**: Allows for "fuzzy" matching. Kilo can apply changes even if the code section has minor differences from what the AI expected. This can be useful if the file has been slightly modified, but **increases the risk** of applying changes in the wrong place.
**Use values below 100% with extreme caution.** Lower precision might be necessary occasionally, but always review the proposed changes carefully.
-Internally, this setting adjusts a `fuzzyMatchThreshold` used with algorithms like Levenshtein distance to compare code similarity.
\ No newline at end of file
+Internally, this setting adjusts a `fuzzyMatchThreshold` used with algorithms like Levenshtein distance to compare code similarity.
diff --git a/packages/kilo-docs/docs/basic-usage/git-commit-generation.md b/packages/kilo-docs/pages/code-with-ai/features/git-commit-generation.md
similarity index 89%
rename from packages/kilo-docs/docs/basic-usage/git-commit-generation.md
rename to packages/kilo-docs/pages/code-with-ai/features/git-commit-generation.md
index ec5007149bf..c4a4307ac8a 100644
--- a/packages/kilo-docs/docs/basic-usage/git-commit-generation.md
+++ b/packages/kilo-docs/pages/code-with-ai/features/git-commit-generation.md
@@ -1,14 +1,20 @@
+---
+title: "Git Commit Generation"
+description: "Automatically generate meaningful git commit messages"
+---
+
# Generate Commit Messages
Generate descriptive commit messages automatically based on your staged git changes. Kilo Code analyzes your staged files and creates conventional commit messages that follow best practices.
-:::info
+{% callout type="info" %}
This feature only analyzes **staged changes**. Make sure to stage your files using `git add` or via `VS Code` interface before generating commit messages.
-:::
+{% /callout %}
## How It Works
The git commit message generator:
+
- Analyzes only your **staged changes** (not unstaged or untracked files)
- Uses AI to understand the context and purpose of your changes
- Creates descriptive commit messages that explain what was changed and why following the [Conventional Commits](https://www.conventionalcommits.org/) (by default, customizable)
@@ -21,10 +27,9 @@ The git commit message generator:
2. In the VS Code Source Control panel, look for the `Kilo Code` logo next to the commit message field)
3. Click the logo to generate a commit message
-
The generated message will appear in the commit message field, ready for you to review and modify if needed.
-
+{% image src="/docs/img/git-commit-generation/git-commit-1.png" alt="Generated commit message example" width="600" /%}
### Conventional Commit Format
@@ -37,6 +42,7 @@ By default, generated messages follow the Conventional Commits specification:
```
Common types include:
+
- `feat`: New features
- `fix`: Bug fixes
- `docs`: Documentation changes
@@ -51,13 +57,14 @@ Common types include:
You can customize how commit messages are generated by modifying the prompt template:
-1. Open Settings by clicking the gear icon
+{% image src="/docs/img/git-commit-generation/git-commit-2.png" alt="Commit message generation settings" width="600" /%}
The default template creates conventional commit messages, but you can modify it to:
+
- Use different commit message formats
- Include specific information relevant to your project
- Follow your team's commit message conventions
@@ -70,23 +77,26 @@ You can configure which API profile to use for commit message generation:
1. In the `Prompts` settings, scroll to "API Configuration"
2. Select a specific profile or use the currently selected one
-:::tip
+{% callout type="tip" %}
Consider creating a dedicated [API configuration profile](/features/api-configuration-profiles) with a faster, more cost-effective model specifically for commit message generation.
-:::
+{% /callout %}
## Best Practices
### Staging Strategy
+
- Stage related changes together for more coherent commit messages
- Avoid staging unrelated changes in a single commit
- Use `git add -p` for partial file staging when needed
### Message Review
+
- Always review generated messages before committing
- Edit messages to add context the AI might have missed
- Ensure the message accurately describes the changes
### Custom Templates
+
- Tailor the prompt template to your project's needs
- Include project-specific terminology or conventions
- Add instructions for handling specific types of changes
@@ -121,7 +131,9 @@ setup steps for new contributors
## Troubleshooting
### No Staged Changes
+
If the button doesn't appear or generation fails, ensure you have staged changes:
+
```bash
git add
+{% image src="/docs/img/task-todo-list/task-todo-list-1.png" alt="Task Todo List overview showing interactive checklist in Kilo Code" width="500" /%}
## How to trigger todo lists
**Automatic triggers**:
+
- Complex tasks with multiple steps
- Working in Architect mode
- Multi-phase workflows with dependencies
**Manual triggers**:
+
- Ask Kilo to "use the [update_todo_list tool](/features/tools/update-todo-list)"
- Say "create a todo list"
@@ -34,10 +41,11 @@
**1. Task Header Summary**
Quick progress overview with your next important item
-
+{% image src="/docs/img/task-todo-list/task-header.png" alt="Task header summary showing todo list progress" width="500" /%}
**2. Interactive Tool Block**
Full todo interface in chat where you can:
+
- See all items and their status
- Edit descriptions when Kilo asks for approval
- Stage changes using the "Edit" button
@@ -49,19 +57,19 @@ Background "REMINDERS" table that keeps Kilo informed about current progress
**Pending** → Empty checkbox (not started)
-
+{% image src="/docs/img/task-todo-list/not-started.png" alt="Pending todo item with empty checkbox" width="300" /%}
---
**In Progress** → Yellow dot (currently working)
-
+{% image src="/docs/img/task-todo-list/in-progress.png" alt="In progress todo item with yellow dot indicator" width="300" /%}
---
**Completed** → Green checkmark (finished)
-
+{% image src="/docs/img/task-todo-list/complete.png" alt="Completed todo item with green checkmark" width="300" /%}
---
@@ -78,10 +86,7 @@ Design choice. Kilo maintains authority over task management to ensure consisten
---
-:::tip
-
-## Pro tip: Auto-approval
-
+{% callout type="tip" title="Pro tip: Auto-approval" %}
**What it does**: Automatically approves todo list updates without confirmation prompts.
**When to use it**: Long workflows where constant interruptions slow you down.
@@ -89,5 +94,4 @@ Design choice. Kilo maintains authority over task management to ensure consisten
**How to enable it**: Check the [Update Todo List auto-approval settings](/features/auto-approving-actions#update-todo-list).
**The catch**: Less control, but faster execution.
-
-:::
\ No newline at end of file
+{% /callout %}
diff --git a/packages/kilo-docs/pages/code-with-ai/index.md b/packages/kilo-docs/pages/code-with-ai/index.md
new file mode 100644
index 00000000000..103feb5d5f7
--- /dev/null
+++ b/packages/kilo-docs/pages/code-with-ai/index.md
@@ -0,0 +1,19 @@
+---
+title: "Code with AI"
+description: "Learn how to use Kilo Code across different platforms and interfaces"
+---
+
+# Code with AI
+
+{% callout type="info" title="Coming Soon" %}
+This page is under construction. Check back soon for comprehensive documentation.
+{% /callout %}
+
+
diff --git a/packages/kilo-docs/docs/cli.md b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md
similarity index 99%
rename from packages/kilo-docs/docs/cli.md
rename to packages/kilo-docs/pages/code-with-ai/platforms/cli.md
index d540723c206..b4abf61b0d7 100644
--- a/packages/kilo-docs/docs/cli.md
+++ b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md
@@ -1,4 +1,9 @@
-# Kilo Code CLI
+---
+title: "Kilo CLI"
+description: "Using Kilo Code from the command line"
+---
+
+# Kilo CLI
Orchestrate agents from your terminal. Plan, debug, and code fast with keyboard-first navigation on the command line.
diff --git a/packages/kilo-docs/docs/advanced-usage/cloud-agent.md b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md
similarity index 91%
rename from packages/kilo-docs/docs/advanced-usage/cloud-agent.md
rename to packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md
index 9c62af62982..9cca4501887 100644
--- a/packages/kilo-docs/docs/advanced-usage/cloud-agent.md
+++ b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md
@@ -1,14 +1,12 @@
---
-title: Cloud Agents
-sidebar_label: Cloud Agents
+title: "Cloud Agent"
+description: "Using Kilo Code in the browser"
---
-# Cloud Agents
+# {% $markdoc.frontmatter.title %}
Cloud Agents let you run Kilo Code in the cloud from any device, without relying on your local machine. They provide a remote development environment that can read and modify your GitHub repositories, run commands, and auto-commit changes as work progresses.
----
-
## What Cloud Agents Enable
- Run Kilo Code remotely from a browser
@@ -16,26 +14,19 @@ Cloud Agents let you run Kilo Code in the cloud from any device, without relying
- Use env vars + startup commands to shape the workspace
- Work from anywhere while keeping your repo in sync
----
-
## Prerequisites
Before using Cloud Agents:
-- **GitHub Integration must be configured**
- Connect your account via the [Integrations tab](https://app.kilo.ai/integrations) so that Cloud Agents can access your repositories.
-
----
+**GitHub Integration must be configured**
+ Connect your account via the [Integrations tab](https://app.kilo.ai/integrations) so that Cloud Agents can access your repositories.
## Cost
- **Compute is free during limited beta**
- - Please provide any feedback in our Cloud Agents beta Discord channel:
- - [Kilo Discord](https://kilo.ai/discord)
+ - Please provide any feedback in our Cloud Agents beta Discord channel: [Kilo Discord](https://kilo.ai/discord)
- **Kilo Code credits are still used** when the agent performs work (model usage, operations, etc.).
----
-
## How to Use
1. **Connect your GitHub account** in the [Integrations](https://app.kilo.ai/integrations) tab of your personal or organization dashboard.
@@ -45,8 +36,6 @@ Before using Cloud Agents:
Your work is always pushed to GitHub, ensuring nothing is lost.
----
-
## How Cloud Agents Work
- Each user receives an **isolated Linux container** with common dev tools preinstalled (Node.js, git, gh CLI, etc.).
@@ -69,8 +58,6 @@ Your work is always pushed to GitHub, ensuring nothing is lost.
- Expect slightly longer setup after idle periods
- Inactive cloud agent sessions are deleted after **7 days** during the beta, expired sessions are still accessible via the CLI
----
-
## Agent Environment Profiles
Agent environment profiles are reusable bundles of environment settings for cloud-agent sessions. A profile can include:
@@ -81,8 +68,6 @@ Agent environment profiles are reusable bundles of environment settings for clou
Profiles are owned by either a user or an organization. Names are unique per owner, and each owner can have a single default profile. This lets teams share standard environment setups across multiple sessions and triggers.
----
-
## Environment Variables & Secrets & Startup Commands
You can customize each Cloud Agent session by also defining env vars and startup commands on the fly. These will override any Agent Environment Profile you've selected:
@@ -101,17 +86,13 @@ You can customize each Cloud Agent session by also defining env vars and startup
- Bootstrapping tooling
- Running setup scripts
----
-
## Skills
-Cloud Agents support project-level [skills](../cli#skills) stored in your repository. When your repo is cloned, any skills in `.kilocode/skills/` are automatically available.
+Cloud Agents support project-level [skills](./cli#skills) stored in your repository. When your repo is cloned, any skills in `.kilocode/skills/` are automatically available.
-:::note
+{% callout type="note" %}
Global skills (`~/.kilocode/skills/`) are not available in Cloud Agents since there is no persistent user home directory.
-:::
-
----
+{% /callout %}
## Perfect For
@@ -123,15 +104,13 @@ Cloud Agents are great for:
- **Automated refactors or tech debt cleanup** driven by Kilo Code
- **Offloading CI-like tasks**, experiments, or batch updates
----
-
## Webhook Triggers
Webhook triggers allow you to initiate cloud agent sessions via HTTP requests. This enables integration with external services and automation workflows.
-:::note
+{% callout type="note" %}
Webhook triggers are currently in beta and subject to change.
-:::
+{% /callout %}
### Accessing Webhooks
@@ -172,13 +151,9 @@ You can reference request data in a trigger’s prompt template using these plac
- `{{sourceIp}}` - client IP if provided (falls back to `unknown`)
- `{{timestamp}}` - capture timestamp (ISO string)
-### Security Considerations
-
-:::warning
+{% callout type="warning" title="Security Considerations" %}
Care should be taken when deciding to use webhooks as they are susceptible to prompt injection attacks. Especially in scenarios where webhook payloads may contain untrusted input. At this time we recommend using webhooks only for trusted sources.
-:::
-
----
+{% /callout %}
## General Cloud Agent Limitations and Guidance
diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/jetbrains.md b/packages/kilo-docs/pages/code-with-ai/platforms/jetbrains.md
new file mode 100644
index 00000000000..e6abe34661f
--- /dev/null
+++ b/packages/kilo-docs/pages/code-with-ai/platforms/jetbrains.md
@@ -0,0 +1,10 @@
+---
+title: "JetBrains Extension"
+description: "Using Kilo Code in JetBrains IDEs"
+---
+
+# JetBrains Extension
+
+## Installation
+
+{% partial file="install-jetbrains.md" /%}
diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/mobile.md b/packages/kilo-docs/pages/code-with-ai/platforms/mobile.md
new file mode 100644
index 00000000000..76abc8decb2
--- /dev/null
+++ b/packages/kilo-docs/pages/code-with-ai/platforms/mobile.md
@@ -0,0 +1,24 @@
+---
+title: "Mobile Apps"
+description: "Using Kilo Code on iOS and Android"
+---
+
+# Mobile Apps
+
+Kilo Code is coming to mobile! Soon you'll be able to use Kilo Code's powerful AI coding capabilities directly from your iOS or Android device.
+
+{% callout type="info" title="Coming Soon" %}
+Mobile apps for iOS and Android are currently in development. Sign up to be notified when they launch!
+{% /callout %}
+
+## iOS App
+
+The Kilo Code iOS app will bring AI-powered coding assistance to your iPhone and iPad.
+
+[Learn more about the iOS app →](https://kilo.ai/features/ios-app)
+
+## Android App
+
+The Kilo Code Android app will let you code with AI assistance on your Android phone or tablet.
+
+[Learn more about the Android app →](https://kilo.ai/features/android-app)
diff --git a/packages/kilo-docs/docs/slack.md b/packages/kilo-docs/pages/code-with-ai/platforms/slack.md
similarity index 98%
rename from packages/kilo-docs/docs/slack.md
rename to packages/kilo-docs/pages/code-with-ai/platforms/slack.md
index a21706e9f32..43b8bec5da2 100644
--- a/packages/kilo-docs/docs/slack.md
+++ b/packages/kilo-docs/pages/code-with-ai/platforms/slack.md
@@ -1,6 +1,6 @@
---
-title: Kilo for Slack
-sidebar_label: Kilo for Slack
+title: "Slack"
+description: "Using Kilo Code in Slack"
---
# Kilo for Slack
diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/vscode.md b/packages/kilo-docs/pages/code-with-ai/platforms/vscode.md
new file mode 100644
index 00000000000..a06044fe304
--- /dev/null
+++ b/packages/kilo-docs/pages/code-with-ai/platforms/vscode.md
@@ -0,0 +1,10 @@
+---
+title: "VS Code Extension"
+description: "Using Kilo Code in Visual Studio Code"
+---
+
+# VS Code Extension
+
+## Installation
+
+{% partial file="install-vscode.md" /%}
diff --git a/packages/kilo-docs/docs/plans/adoption-dashboard/for-team-leads.md b/packages/kilo-docs/pages/collaborate/adoption-dashboard/for-team-leads.md
similarity index 98%
rename from packages/kilo-docs/docs/plans/adoption-dashboard/for-team-leads.md
rename to packages/kilo-docs/pages/collaborate/adoption-dashboard/for-team-leads.md
index 451949cabd9..28dff86753a 100644
--- a/packages/kilo-docs/docs/plans/adoption-dashboard/for-team-leads.md
+++ b/packages/kilo-docs/pages/collaborate/adoption-dashboard/for-team-leads.md
@@ -1,8 +1,9 @@
---
-sidebar_label: For Team Leads
+title: "For Team Leads"
+description: "AI adoption insights for team leaders"
---
-# AI Adoption Dashboard for Team Leads
+# For Team Leads
This guide covers how engineering managers and team leads can use the AI Adoption Dashboard to drive AI integration, identify gaps, and communicate progress to stakeholders.
diff --git a/packages/kilo-docs/docs/plans/adoption-dashboard/improving-your-score.md b/packages/kilo-docs/pages/collaborate/adoption-dashboard/improving-your-score.md
similarity index 97%
rename from packages/kilo-docs/docs/plans/adoption-dashboard/improving-your-score.md
rename to packages/kilo-docs/pages/collaborate/adoption-dashboard/improving-your-score.md
index 23aa1f28d9f..d8e9909a5ab 100644
--- a/packages/kilo-docs/docs/plans/adoption-dashboard/improving-your-score.md
+++ b/packages/kilo-docs/pages/collaborate/adoption-dashboard/improving-your-score.md
@@ -1,8 +1,9 @@
---
-sidebar_label: Improving Your Score
+title: "Improving Your Score"
+description: "Tips and strategies to improve your AI adoption score"
---
-# Improving Your AI Adoption Score
+# Improving Your Score
This guide provides actionable strategies to improve each dimension of your AI Adoption Score. Click on any dimension in the dashboard to see personalized suggestions based on your team's usage patterns.
@@ -64,9 +65,9 @@ Depth increases when AI touches multiple stages of the same task. Each handoff r
2. **Build** — Use Code mode to implement it
3. **Review** — Use Code Reviews to critique it
-:::tip
+{% callout type="tip" %}
Linking coding → review → deploy actions significantly boosts your Depth score.
-:::
+{% /callout %}
### Give AI Better Context
diff --git a/packages/kilo-docs/docs/plans/adoption-dashboard/overview.md b/packages/kilo-docs/pages/collaborate/adoption-dashboard/overview.md
similarity index 97%
rename from packages/kilo-docs/docs/plans/adoption-dashboard/overview.md
rename to packages/kilo-docs/pages/collaborate/adoption-dashboard/overview.md
index 7d57061c8e0..094df214f21 100644
--- a/packages/kilo-docs/docs/plans/adoption-dashboard/overview.md
+++ b/packages/kilo-docs/pages/collaborate/adoption-dashboard/overview.md
@@ -1,8 +1,9 @@
---
-sidebar_label: AI Adoption Dashboard
+title: "Overview"
+description: "AI Adoption Dashboard overview"
---
-# AI Adoption Dashboard
+# AI Adoption Dashboard Overview
The AI Adoption Dashboard helps engineering leaders understand how deeply and consistently their teams are using AI across development workflows. It provides a single **AI Adoption Score** (0–100) that quantifies organizational AI maturity, plus detailed breakdowns by dimension.
diff --git a/packages/kilo-docs/docs/plans/adoption-dashboard/understanding-your-score.md b/packages/kilo-docs/pages/collaborate/adoption-dashboard/understanding-your-score.md
similarity index 98%
rename from packages/kilo-docs/docs/plans/adoption-dashboard/understanding-your-score.md
rename to packages/kilo-docs/pages/collaborate/adoption-dashboard/understanding-your-score.md
index ccc0a87ee91..0522bde23c9 100644
--- a/packages/kilo-docs/docs/plans/adoption-dashboard/understanding-your-score.md
+++ b/packages/kilo-docs/pages/collaborate/adoption-dashboard/understanding-your-score.md
@@ -1,8 +1,9 @@
---
-sidebar_label: Understanding Your Score
+title: "Understanding Your Score"
+description: "Learn how your AI adoption score is calculated"
---
-# Understanding Your AI Adoption Score
+# Understanding Your Score
The AI Adoption Score is a 0–100 metric representing how deeply and consistently your team uses AI across real development workflows. This page explains what each dimension measures and how to interpret your score.
diff --git a/packages/kilo-docs/docs/plans/enterprise/audit-logs.md b/packages/kilo-docs/pages/collaborate/enterprise/audit-logs.md
similarity index 97%
rename from packages/kilo-docs/docs/plans/enterprise/audit-logs.md
rename to packages/kilo-docs/pages/collaborate/enterprise/audit-logs.md
index de1a729c032..a9c7932aeaa 100644
--- a/packages/kilo-docs/docs/plans/enterprise/audit-logs.md
+++ b/packages/kilo-docs/pages/collaborate/enterprise/audit-logs.md
@@ -1,8 +1,9 @@
---
-sidebar_label: Audit Logs (Enterprise Only)
+title: "Audit Logs"
+description: "Track and audit team activity"
---
-# Audit Logs (Enterprise Only)
+# Audit Logs
Audit Logs record key actions that occur in the management of your Kilo seats, including user logins, adding or removing models, providers, and modes, and role changes.
diff --git a/packages/kilo-docs/docs/plans/migration.md b/packages/kilo-docs/pages/collaborate/enterprise/migration.md
similarity index 85%
rename from packages/kilo-docs/docs/plans/migration.md
rename to packages/kilo-docs/pages/collaborate/enterprise/migration.md
index b53f6e91fc2..50479642cbb 100644
--- a/packages/kilo-docs/docs/plans/migration.md
+++ b/packages/kilo-docs/pages/collaborate/enterprise/migration.md
@@ -1,8 +1,9 @@
---
-sidebar_label: Migrating from Other Tools
+title: "Migration"
+description: "Migrate your team to Kilo Code Enterprise"
---
-# Migrating from Other Tools
+# Migration
Switch to **Kilo Teams** or **Kilo Enterprise** from other AI coding tools and experience transparent pricing, no vendor lock-in, and superior team management capabilities.
@@ -57,7 +58,7 @@ Switch to **Kilo Teams** or **Kilo Enterprise** from other AI coding tools and e
**Step 2: Kilo Setup**
1. **Create organization** at [app.kilocode.com](https://app.kilocode.com)
-2. **Subscribe to Teams ($29/month)** or **Enterprise ($299/month)**
+2. **Subscribe to Teams ($15/month)** or **Enterprise ($150/month)**
3. **Configure team settings** and usage policies
4. **Purchase initial AI credits** based on usage estimates
@@ -186,6 +187,21 @@ Switch to **Kilo Teams** or **Kilo Enterprise** from other AI coding tools and e
- [ ] Cancel previous AI coding tool subscriptions
- [ ] Document new workflows and best practices
+## Technical Migration: Rules and Configurations
+
+Kilo Code uses a compatible rules system that supports Cursor and Windsurf patterns. Migrating your custom rules and configurations is straightforward and typically takes 5-10 minutes per project.
+
+**Quick Overview:**
+
+- **Project rules**: `.cursor/rules/*.mdc` → `.kilocode/rules/*.md` (remove YAML frontmatter, keep Markdown content)
+- **Legacy rules**: `.cursorrules` → `.kilocode/rules/legacy-rules.md`
+- **AGENTS.md**: Works identically in Kilo Code (no conversion needed)
+- **Global rules**: Recreate in `~/.kilocode/rules/*.md` directory
+
+Kilo Code also supports mode-specific rules (`.kilocode/rules-{mode}/`), which Cursor and Windsurf don't have. This allows different rules for different workflows (e.g., Code mode vs Debug mode).
+
+**👉 For detailed step-by-step instructions, format conversion examples, troubleshooting, and advanced migration scenarios, see our [Technical Migration Guide](/advanced-usage/migrating-from-cursor-windsurf).**
+
## Cost Comparison Analysis
### Hidden Costs in Other Tools
@@ -290,6 +306,12 @@ Switch to **Kilo Teams** or **Kilo Enterprise** from other AI coding tools and e
- **Solution:** Document and recreate important settings
- **Prevention:** Settings audit before migration
+**Rules and Configuration Migration**
+
+- **Issue:** Custom rules and configurations not migrating automatically
+- **Solution:** Follow the [technical migration guide](/advanced-usage/migrating-from-cursor-windsurf) to manually migrate rules
+- **Prevention:** Audit rules before migration, use version control for rules
+
### Organizational Challenges
**Change Resistance**
@@ -322,16 +344,19 @@ Switch to **Kilo Teams** or **Kilo Enterprise** from other AI coding tools and e
### Self-Service Resources
- **Migration guides** for specific tools
+- **[Technical migration guide](/advanced-usage/migrating-from-cursor-windsurf)** for rules and configurations (Cursor/Windsurf)
- **Video tutorials** for common migration scenarios
- **Community support** through Discord and forums
- **Documentation** and best practices
### Getting Migration Help
-- **Email:** migrations@kilocode.ai
+- **Email:** migrations@kilo.ai
- **Discord:** Join our migration support channel
- **Consultation:** Schedule free migration planning call
-- **Documentation:** Comprehensive migration guides
+- **Documentation:**
+ - [Business migration guide](/plans/migration) (this page)
+ - [Technical migration guide](/advanced-usage/migrating-from-cursor-windsurf) (rules and configurations)
## Success Stories
@@ -361,5 +386,6 @@ Switch to **Kilo Teams** or **Kilo Enterprise** from other AI coding tools and e
- [Get started with your team](/plans/getting-started)
- [Explore team management features](/plans/team-management)
- [Understand billing and pricing](/plans/billing)
+- [Migrate your rules and configurations](/advanced-usage/migrating-from-cursor-windsurf) (technical guide)
-Ready to make the switch? Contact our migration team at migrations@kilocode.ai to plan your transition to transparent AI coding.
+Ready to make the switch? Contact our migration team at migrations@kilo.ai to plan your transition to transparent AI coding.
diff --git a/packages/kilo-docs/docs/plans/enterprise/model-access.md b/packages/kilo-docs/pages/collaborate/enterprise/model-access-controls.md
similarity index 88%
rename from packages/kilo-docs/docs/plans/enterprise/model-access.md
rename to packages/kilo-docs/pages/collaborate/enterprise/model-access-controls.md
index ed1f8107487..f5e87b46235 100644
--- a/packages/kilo-docs/docs/plans/enterprise/model-access.md
+++ b/packages/kilo-docs/pages/collaborate/enterprise/model-access-controls.md
@@ -1,8 +1,9 @@
---
-sidebar_label: Model Access (Enterprise Only)
+title: "Model Access Controls"
+description: "Control which AI models your team can access"
---
-# Model Access (Enterprise Only)
+# Model Access Controls
**Model Access** lets organization admins control which AI models and providers are available to team members.
Admins can **enable or disable** specific models, filter by attributes, and enforce organizational data policies.
@@ -13,7 +14,7 @@ Admins can **enable or disable** specific models, filter by attributes, and enfo
2. Toggle the checkbox beside any model or provider to enable or disable access.
3. Click "Save Changes" to apply
-
+{% image src="/docs/img/teams/org_credits.png" alt="Dropdown showing different organizations available" width="600" caption="Dropdown showing different organizations available" /%}
## Managing Seats Subscriptions
diff --git a/packages/kilo-docs/docs/plans/custom-modes.md b/packages/kilo-docs/pages/collaborate/teams/custom-modes-org.md
similarity index 86%
rename from packages/kilo-docs/docs/plans/custom-modes.md
rename to packages/kilo-docs/pages/collaborate/teams/custom-modes-org.md
index 4b3bdb04b31..a718bee595a 100644
--- a/packages/kilo-docs/docs/plans/custom-modes.md
+++ b/packages/kilo-docs/pages/collaborate/teams/custom-modes-org.md
@@ -1,14 +1,15 @@
---
-sidebar_label: Custom Modes
+title: "Custom Modes (Org)"
+description: "Create organization-wide custom modes"
---
-# Custom Modes
+# Custom Modes (Org)
Custom Modes let you create tailored versions of Kilo’s built-in [modes](/basic-usage/using-modes) for your organization. You can also adjust the settings for Kilo Code's original default modes. You can define a mode’s purpose, behavior, and tool access — helping Kilo adapt to your team’s unique workflows.
-For example, Admins and Owners can extend these by creating **Custom Modes** with specialized roles or personalities (e.g. “Documentation Writer” or “Security Reviewer”).
+For example, Admins and Owners can extend these by creating **Custom Modes** with specialized roles or personalities (e.g. "Documentation Writer" or "Security Reviewer").
-
+{% image src="/docs/img/teams/custom_modes.png" alt="Create a new custom mode tab." caption="Create a new custom mode tab." /%}
## Creating a Custom Mode
diff --git a/packages/kilo-docs/docs/plans/dashboard.md b/packages/kilo-docs/pages/collaborate/teams/dashboard.md
similarity index 94%
rename from packages/kilo-docs/docs/plans/dashboard.md
rename to packages/kilo-docs/pages/collaborate/teams/dashboard.md
index b391c71777c..d578557faf0 100644
--- a/packages/kilo-docs/docs/plans/dashboard.md
+++ b/packages/kilo-docs/pages/collaborate/teams/dashboard.md
@@ -1,10 +1,11 @@
---
-sidebar_label: Dashboard Overview
+title: "Dashboard"
+description: "Manage your team from the Kilo Code dashboard"
---
-# Seats Dashboard
+# Dashboard
-The Kilo seats dashboard is the first screen that comes up when you visit [the Kilo Code web app](https://app.kilocode.ai). It provides complete visibility into your team's AI usage, costs, and management.
+The Kilo seats dashboard is the first screen that comes up when you visit [the Kilo Code web app](https://app.kilo.ai). It provides complete visibility into your team's AI usage, costs, and management.
@@ -113,7 +114,7 @@ Manage your Kilo Teams plan and seat allocation.
### Current Plan Details
- **Plan type** (Kilo Teams)
-- **Monthly cost** per seat ($29/user/month)
+- **Monthly cost** per seat ($15/user/month)
- **Billing cycle** dates and next charge
- **Plan benefits** and included features
diff --git a/packages/kilo-docs/docs/plans/getting-started.md b/packages/kilo-docs/pages/collaborate/teams/getting-started.md
similarity index 95%
rename from packages/kilo-docs/docs/plans/getting-started.md
rename to packages/kilo-docs/pages/collaborate/teams/getting-started.md
index f45b9bdbe74..41baf44ab9d 100644
--- a/packages/kilo-docs/docs/plans/getting-started.md
+++ b/packages/kilo-docs/pages/collaborate/teams/getting-started.md
@@ -1,5 +1,6 @@
---
-sidebar_label: Getting Started
+title: "Getting Started with Teams"
+description: "Set up your Kilo Code team account"
---
# Get Started with Kilo Seats in 10 Minutes
@@ -17,7 +18,7 @@ seats for Kilo in the Teams or Enterprise subscription brings transparent AI cod
### Step 1: Create Your Organization
-1. Visit [app.kilocode.ai](https://app.kilocode.ai)
+1. Visit [app.kilo.ai](https://app.kilo.ai)
2. Sign up using your company Google Workspaces or GitHub account
- Note: We recommend starting with your GitHub account rather than a personal Google account, but we can change it later.
3. Click **Organizations** in the left sidebar and then **Create New Organization**
diff --git a/packages/kilo-docs/docs/plans/team-management.md b/packages/kilo-docs/pages/collaborate/teams/team-management.md
similarity index 89%
rename from packages/kilo-docs/docs/plans/team-management.md
rename to packages/kilo-docs/pages/collaborate/teams/team-management.md
index 0e04115a780..02140941795 100644
--- a/packages/kilo-docs/docs/plans/team-management.md
+++ b/packages/kilo-docs/pages/collaborate/teams/team-management.md
@@ -1,5 +1,6 @@
---
-sidebar_label: Managing Your Team
+title: "Team Management"
+description: "Add and manage team members in Kilo Code"
---
# Managing Your Team
@@ -20,7 +21,7 @@ Members can use the Kilo Code extension and see data on the team's usage in the
4. **Select initial role** (Member or Owner)
5. Click **Send Invitation**
-
+*Image: Export, Import, and Reset buttons.*
+
+## Export Settings
+
+Clicking the **Export** button saves your current Kilo Code settings to a JSON file.
+
+- **What's Exported:** The file includes your configured API Provider Profiles and Global Settings (UI preferences, mode configurations, context settings, etc.).
+- **Security Warning:** The exported JSON file contains **all** your configured API Provider Profiles and Global Settings. Crucially, this includes **API keys in plaintext**. Treat this file as highly sensitive. Do not share it publicly or with untrusted individuals, as it grants access to your API accounts.
+- **Process:**
+ 1. Click **Export**.
+ 2. A file save dialog appears, suggesting `kilo-code-settings.json` as the filename (usually in your `~/Documents` folder).
+ 3. Choose a location and save the file.
+
+This creates a backup of your configuration or a file you can share.
+
+## Import Settings
+
+Clicking the **Import** button allows you to load settings from a previously exported JSON file.
+
+- **Process:**
+ 1. Click **Import**.
+ 2. A file open dialog appears. Select the `kilo-code-settings.json` file (or similarly named file) you want to import.
+ 3. Kilo Code reads the file, validates its contents against the expected schema, and applies the settings.
+- **Merging:** Importing settings **merges** the configurations. It adds new API profiles and updates existing ones and global settings based on the file content. It does **not** delete configurations present in your current setup but missing from the imported file.
+- **Validation:** Only valid settings matching the internal schema can be imported, preventing configuration errors. A success notification appears upon completion.
+
+## Reset Settings
+
+Clicking the **Reset** button completely clears all Kilo Code configuration data and returns the extension to its default state. This is a destructive action intended for troubleshooting or starting fresh.
+
+- **Warning:** This action is **irreversible**. It permanently deletes all API configurations (including keys stored in secret storage), custom modes, global settings, and task history.
+
+- **Process:**
+
+ 1. Click the red **Reset** button.
+ 2. A confirmation dialog appears, warning that the action cannot be undone.
+ 3. Click "Yes" to confirm.
+
+- **What is Reset:**
+
+ - **API Provider Profiles:** All configurations are deleted from settings and secret storage.
+ - **Global Settings:** All preferences (UI, modes, approvals, browser, etc.) are reset to defaults.
+ - **Custom Modes:** All user-defined modes are deleted.
+ - **Secret Storage:** All API keys and other secrets managed by Kilo Code are cleared.
+ - **Task History:** The current task stack is cleared.
+
+- **Result:** Kilo Code returns to its initial state, as if freshly installed, with default settings and no user configurations.
+
+Use this option only if you are certain you want to remove all Kilo Code data or if instructed during troubleshooting. Consider exporting your settings first if you might want to restore them later.
diff --git a/packages/kilo-docs/pages/getting-started/setup-authentication.md b/packages/kilo-docs/pages/getting-started/setup-authentication.md
new file mode 100644
index 00000000000..a201f13b5c5
--- /dev/null
+++ b/packages/kilo-docs/pages/getting-started/setup-authentication.md
@@ -0,0 +1,77 @@
+---
+title: "Setup & Authentication"
+description: "Configure Kilo Code and connect to your AI providers"
+---
+
+# Setup & Authentication
+
+When you install Kilo Code, you'll be prompted to sign in or create a free account. This automatically configures everything you need to get started.
+
+## Quick Start with Kilo Account
+
+1. Click **"Try Kilo Code for Free"** in the extension
+2. Sign in with your Google account
+3. Allow VS Code to open the authorization URL
+
+{% image src="/docs/img/signupflow.gif" alt="Sign up and registration flow with Kilo Code" /%}
+
+That's it! You're ready to [start your first task](/getting-started/quickstart).
+
+{% callout type="tip" title="Bonus Credits" %}
+[Add credits to your account](https://app.kilo.ai/profile) and get $20 bonus credits, or sign up for [Kilo Pass](https://kilo.ai/features/kilo-pass).
+{% /callout %}
+
+## Using Another API Provider
+
+If you prefer to use your own API key or existing subscription, Kilo Code supports **over 30 providers**. Here are some popular options to get started:
+
+| Provider | Best For | API Key Required |
+| --------------------------------------------------------- | ----------------------------------- | ---------------- |
+| [ChatGPT Plus/Pro](/ai-providers/openai-chatgpt-plus-pro) | Use your existing subscription | No |
+| [OpenRouter](/ai-providers/openrouter) | Access multiple models with one key | Yes |
+| [Anthropic](/ai-providers/anthropic) | Direct access to Claude models | Yes |
+| [OpenAI](/ai-providers/openai) | Access to GPT models | Yes |
+
+{% callout type="info" title="Many More Providers Available" %}
+These are just a few examples! Kilo Code supports many more providers including Google Gemini, DeepSeek, Mistral, Ollama (for local models), AWS Bedrock, Google Vertex, and more. See the complete list at [AI Providers](/ai-providers/).
+{% /callout %}
+
+### ChatGPT Plus/Pro Subscription
+
+Already have a ChatGPT subscription? You can use it with Kilo Code through the [OpenAI ChatGPT provider](/providers/openai-chatgpt-plus-pro)—no API key needed.
+
+### OpenRouter
+
+1. Go to [openrouter.ai](https://openrouter.ai/) and sign in
+2. Navigate to [API keys](https://openrouter.ai/keys) and create a new key
+3. Copy your API key
+
+{% image src="/docs/img/connecting-api-provider/connecting-api-provider-4.png" alt="OpenRouter API keys page" width="600px" caption="Create and copy your OpenRouter API key" /%}
+
+### Anthropic
+
+1. Go to [console.anthropic.com](https://console.anthropic.com/) and sign in
+2. Navigate to [API keys](https://console.anthropic.com/settings/keys) and create a new key
+3. Copy your API key immediately—it won't be shown again
+
+{% image src="/docs/img/connecting-api-provider/connecting-api-provider-5.png" alt="Anthropic console API Keys section" width="600px" caption="Copy your Anthropic API key immediately after creation" /%}
+
+### OpenAI
+
+1. Go to [platform.openai.com](https://platform.openai.com/) and sign in
+2. Navigate to [API keys](https://platform.openai.com/api-keys) and create a new key
+3. Copy your API key immediately—it won't be shown again
+
+{% image src="/docs/img/connecting-api-provider/connecting-api-provider-6.png" alt="OpenAI API keys page" width="600px" caption="Copy your OpenAI API key immediately after creation" /%}
+
+### Configuring Your Provider
+
+1. Click the {% kilo-code-icon /%} icon in the VS Code sidebar
+2. Select your API provider from the dropdown
+3. Paste your API key
+4. Choose your model:
+5. Click **"Let's go!"**
+
+{% callout type="info" title="Need Help?" %}
+Reach out to our [support team](mailto:hi@kilo.ai) or join our [Discord community](https://kilo.ai/discord).
+{% /callout %}
diff --git a/packages/kilo-docs/pages/index.tsx b/packages/kilo-docs/pages/index.tsx
new file mode 100644
index 00000000000..093bf8cc89b
--- /dev/null
+++ b/packages/kilo-docs/pages/index.tsx
@@ -0,0 +1,879 @@
+import React, { useState } from "react"
+import Link from "next/link"
+
+// Terminal content for each tab
+const terminalContent = {
+ installation: (
+ <>
+ # Install Kilo Code VS Code Extension
+ {"\n"}
+ $ code --install-extension kilocode.kilo-code
+ {"\n"}
+ {"\n"}
+ # Or install via CLI
+ {"\n"}
+ $ npm install -g @kilocode/cli
+
+ ),
+ firstTask: (
+ <>
+ # Start a new task with Kilo Code
+ {"\n"}
+ $ kilo "Create a React component for a user profile"
+ {"\n"}
+ {"\n"}
+
+ # Or for interactive sessions, just run the Kilo CLI in your project folder
+
+ {"\n"}
+ $ kilo
+ {"\n"}
+ {"\n"}
+ # Run in architect mode for planning
+ {"\n"}
+ $ kilo --mode architect "Design a REST API"
+
+ ),
+ customRules: (
+ <>
+ # Create a custom rules file in your project
+ {"\n"}
+ $ touch .kilocode/rules.md
+ {"\n"}
+ {"\n"}
+ # Or use the CLI to add rules
+ {"\n"}
+ $ kilo rules add "Always use TypeScript"
+ {"\n"}
+ $ kilo rules add "Follow React best practices"
+ {"\n"}
+ {"\n"}
+ # List all active rules
+ {"\n"}
+ $ kilo rules list
+
+ ),
+}
+
+// Category card data based on the information architecture
+const categories = [
+ {
+ title: "Get Started",
+ description: "Install Kilo Code and get up and running in minutes",
+ href: "/getting-started",
+ icon: (
+
+ ),
+ links: [
+ { title: "Installation", href: "/getting-started/installing" },
+ { title: "Quickstart", href: "/getting-started" },
+ { title: "FAQ", href: "/getting-started/faq" },
+ ],
+ },
+ {
+ title: "Code with AI",
+ description: "Learn how to use Kilo Code to write, edit, and understand code",
+ href: "/code-with-ai",
+ icon: (
+
+ ),
+ links: [
+ { title: "The Chat Interface", href: "/code-with-ai" },
+ { title: "Using Modes", href: "/code-with-ai" },
+ { title: "Custom Rules", href: "/code-with-ai" },
+ ],
+ },
+ {
+ title: "Collaborate",
+ description: "Work with teams, share sessions, and manage organizations",
+ href: "/collaborate",
+ icon: (
+
+ ),
+ links: [
+ { title: "Sessions & Sharing", href: "/collaborate" },
+ { title: "Kilo for Teams", href: "/collaborate" },
+ { title: "Enterprise", href: "/collaborate" },
+ ],
+ },
+ {
+ title: "Automate",
+ description: "Set up automated workflows, integrations, and MCP servers",
+ href: "/automate",
+ icon: (
+
+ ),
+ links: [
+ { title: "Code Reviews", href: "/automate" },
+ { title: "MCP Overview", href: "/automate" },
+ { title: "Integrations", href: "/automate" },
+ ],
+ },
+ {
+ title: "Deploy & Secure",
+ description: "Deploy your applications and ensure security best practices",
+ href: "/deploy-secure",
+ icon: (
+
+ ),
+ links: [
+ { title: "Deploy", href: "/deploy-secure" },
+ { title: "Managed Indexing", href: "/deploy-secure" },
+ { title: "Security Reviews", href: "/deploy-secure" },
+ ],
+ },
+ {
+ title: "Contributing",
+ description: "Help improve Kilo Code and learn about its architecture",
+ href: "/contributing",
+ icon: (
+
+ ),
+ links: [
+ { title: "Contributing Overview", href: "/contributing" },
+ { title: "Development Environment", href: "/contributing" },
+ { title: "Architecture", href: "/contributing" },
+ ],
+ },
+]
+
+export default function HomePage() {
+ const [activeTab, setActiveTab] = useState<"installation" | "firstTask" | "customRules">("installation")
+
+ return (
+
+ {/* Dotted background pattern */}
+
+
+ {/* Hero Section */}
+
+
+
+ {/* Browse by Category - Three Column Layout */}
+
+
+
+ {/* Category Cards Grid */}
+
+
+
+ {/* Interactive Terminal Section - Stripe Shell Style */}
+
+
+
+ {/* Footer Links */}
+
+
+
+
+
+ )
+}
diff --git a/packages/kilo-docs/postcss.config.js b/packages/kilo-docs/postcss.config.js
new file mode 100644
index 00000000000..16c5a6d44d9
--- /dev/null
+++ b/packages/kilo-docs/postcss.config.js
@@ -0,0 +1,6 @@
+module.exports = {
+ plugins: {
+ "@tailwindcss/postcss": {},
+ autoprefixer: {},
+ },
+}
diff --git a/packages/kilo-docs/previous-docs-redirects.js b/packages/kilo-docs/previous-docs-redirects.js
new file mode 100644
index 00000000000..8d6f575be16
--- /dev/null
+++ b/packages/kilo-docs/previous-docs-redirects.js
@@ -0,0 +1,623 @@
+module.exports = [
+ // ============================================
+ // GET STARTED
+ // ============================================
+ {
+ source: "/getting-started/quickstart",
+ destination: "/docs/getting-started/quickstart",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/getting-started/setting-up",
+ destination: "/docs/getting-started/setup-authentication",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/getting-started/connecting-api-provider",
+ destination: "/docs/getting-started/setup-authentication",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/getting-started/concepts",
+ destination: "/docs/getting-started",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/getting-started/your-first-task",
+ destination: "/docs/getting-started/quickstart",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/connecting-providers",
+ destination: "/docs/getting-started/ai-providers",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/providers/:path*",
+ destination: "/docs/getting-started/ai-providers",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/settings-management",
+ destination: "/docs/getting-started/settings",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/adding-credits",
+ destination: "/docs/getting-started/adding-credits",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/migrating-from-cursor-windsurf",
+ destination: "/docs/getting-started/migrating",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CODE WITH AI - Platforms
+ // ============================================
+ {
+ source: "/cli",
+ destination: "/docs/code-with-ai/platforms/cli",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/cloud-agent",
+ destination: "/docs/code-with-ai/platforms/cloud-agent",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/slack",
+ destination: "/docs/code-with-ai/platforms/slack",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CODE WITH AI - Working with Agents
+ // ============================================
+ {
+ source: "/basic-usage/the-chat-interface",
+ destination: "/docs/code-with-ai/agents/chat-interface",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/context-mentions",
+ destination: "/docs/code-with-ai/agents/context-mentions",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/using-modes",
+ destination: "/docs/code-with-ai/agents/using-modes",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/orchestrator-mode",
+ destination: "/docs/code-with-ai/agents/orchestrator-mode",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/model-selection-guide",
+ destination: "/docs/code-with-ai/agents/model-selection",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CODE WITH AI - Features
+ // ============================================
+ {
+ source: "/basic-usage/autocomplete",
+ destination: "/docs/code-with-ai/features/autocomplete",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/autocomplete/index",
+ destination: "/docs/code-with-ai/features/autocomplete",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/autocomplete/mistral-setup",
+ destination: "/docs/code-with-ai/features/autocomplete",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/code-actions",
+ destination: "/docs/code-with-ai/features/code-actions",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/browser-use",
+ destination: "/docs/code-with-ai/features/browser-use",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/git-commit-generation",
+ destination: "/docs/code-with-ai/features/git-commit-generation",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/checkpoints",
+ destination: "/docs/code-with-ai/features/checkpoints",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/enhance-prompt",
+ destination: "/docs/code-with-ai/features/enhance-prompt",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/fast-edits",
+ destination: "/docs/code-with-ai/features/fast-edits",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/task-todo-list",
+ destination: "/docs/code-with-ai/features/task-todo-list",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CODE WITH AI - Context & Indexing
+ // ============================================
+ {
+ source: "/features/codebase-indexing",
+ destination: "/docs/code-with-ai/context/codebase-indexing",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/memory-bank",
+ destination: "/docs/code-with-ai/context/memory-bank",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/large-projects",
+ destination: "/docs/code-with-ai/context/large-projects",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CODE WITH AI - Customization
+ // ============================================
+ {
+ source: "/agent-behavior/custom-modes",
+ destination: "/docs/code-with-ai/customization/custom-modes",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/agent-behavior/custom-rules",
+ destination: "/docs/code-with-ai/customization/custom-rules",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/agent-behavior/custom-instructions",
+ destination: "/docs/code-with-ai/customization/custom-instructions",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/agent-behavior/agents-md",
+ destination: "/docs/code-with-ai/customization/agents-md",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/agent-behavior/workflows",
+ destination: "/docs/code-with-ai/customization/workflows",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/agent-behavior/skills",
+ destination: "/docs/code-with-ai/customization/skills",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/agent-behavior/prompt-engineering",
+ destination: "/docs/code-with-ai/customization/prompt-engineering",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CODE WITH AI - App Builder
+ // ============================================
+ {
+ source: "/advanced-usage/appbuilder",
+ destination: "/docs/code-with-ai/app-builder",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // COLLABORATE - Sessions & Sharing
+ // ============================================
+ {
+ source: "/advanced-usage/sessions",
+ destination: "/docs/collaborate/sessions-sharing",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // COLLABORATE - Kilo for Teams
+ // ============================================
+ {
+ source: "/plans/about",
+ destination: "/docs/collaborate/teams/about-plans",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/getting-started",
+ destination: "/docs/collaborate/teams/getting-started",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/dashboard",
+ destination: "/docs/collaborate/teams/dashboard",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/team-management",
+ destination: "/docs/collaborate/teams/team-management",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/custom-modes",
+ destination: "/docs/collaborate/teams/custom-modes-org",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/billing",
+ destination: "/docs/collaborate/teams/billing",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/analytics",
+ destination: "/docs/collaborate/teams/analytics",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // COLLABORATE - AI Adoption Dashboard
+ // ============================================
+ {
+ source: "/plans/adoption-dashboard/overview",
+ destination: "/docs/collaborate/adoption-dashboard/overview",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/adoption-dashboard/understanding-your-score",
+ destination: "/docs/collaborate/adoption-dashboard/understanding-your-score",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/adoption-dashboard/improving-your-score",
+ destination: "/docs/collaborate/adoption-dashboard/improving-your-score",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/adoption-dashboard/for-team-leads",
+ destination: "/docs/collaborate/adoption-dashboard/for-team-leads",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // COLLABORATE - Enterprise
+ // ============================================
+ {
+ source: "/plans/enterprise/SSO",
+ destination: "/docs/collaborate/enterprise/sso",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/enterprise/sso",
+ destination: "/docs/collaborate/enterprise/sso",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/enterprise/model-access",
+ destination: "/docs/collaborate/enterprise/model-access-controls",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/enterprise/audit-logs",
+ destination: "/docs/collaborate/enterprise/audit-logs",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/plans/migration",
+ destination: "/docs/collaborate/enterprise/migration",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // AUTOMATE
+ // ============================================
+ {
+ source: "/advanced-usage/code-reviews",
+ destination: "/docs/automate/code-reviews",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/agent-manager",
+ destination: "/docs/automate/agent-manager",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // AUTOMATE - CI/CD & Integrations
+ // ============================================
+ {
+ source: "/advanced-usage/integrations",
+ destination: "/docs/automate/integrations/overview",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/auto-launch-configuration",
+ destination: "/docs/automate/integrations/auto-launch",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // AUTOMATE - Extending Kilo
+ // ============================================
+ {
+ source: "/advanced-usage/local-models",
+ destination: "/docs/automate/extending/local-models",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/shell-integration",
+ destination: "/docs/automate/extending/shell-integration",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // AUTOMATE - MCP
+ // ============================================
+ {
+ source: "/features/mcp/overview",
+ destination: "/docs/automate/mcp/overview",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/mcp/using-mcp-in-kilo-code",
+ destination: "/docs/automate/mcp/using-in-kilo-code",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/mcp/using-mcp-in-cli",
+ destination: "/docs/automate/mcp/using-in-cli",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/mcp/what-is-mcp",
+ destination: "/docs/automate/mcp/what-is-mcp",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/mcp/server-transports",
+ destination: "/docs/automate/mcp/server-transports",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/mcp/mcp-vs-api",
+ destination: "/docs/automate/mcp/mcp-vs-api",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // DEPLOY & SECURE
+ // ============================================
+ {
+ source: "/advanced-usage/deploy",
+ destination: "/docs/deploy-secure/deploy",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/managed-indexing",
+ destination: "/docs/deploy-secure/managed-indexing",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/security-reviews",
+ destination: "/docs/deploy-secure/security-reviews",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CONTRIBUTING
+ // ============================================
+ {
+ source: "/contributing",
+ destination: "/docs/contributing",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/index",
+ destination: "/docs/contributing",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/development-environment",
+ destination: "/docs/contributing/development-environment",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // CONTRIBUTING - Architecture
+ // ============================================
+ {
+ source: "/contributing/architecture",
+ destination: "/docs/contributing/architecture",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/index",
+ destination: "/docs/contributing/architecture",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/annual-billing",
+ destination: "/docs/contributing/architecture/annual-billing",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/enterprise-mcp-controls",
+ destination: "/docs/contributing/architecture/enterprise-mcp-controls",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/onboarding-engagement-improvements",
+ destination: "/docs/contributing/architecture/onboarding-improvements",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/organization-modes-library",
+ destination: "/docs/contributing/architecture/organization-modes-library",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/track-repo-url",
+ destination: "/docs/contributing/architecture/track-repo-url",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/vercel-ai-gateway",
+ destination: "/docs/contributing/architecture/vercel-ai-gateway",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/contributing/architecture/voice-transcription",
+ destination: "/docs/contributing/architecture/voice-transcription",
+ basePath: false,
+ permanent: true,
+ },
+
+ // ============================================
+ // PAGES TO CONDENSE (Redirects to parent pages)
+ // ============================================
+ {
+ source: "/features/system-notifications",
+ destination: "/docs/getting-started/settings",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/suggested-responses",
+ destination: "/docs/code-with-ai/agents/chat-interface",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/basic-usage/how-tools-work",
+ destination: "/docs/code-with-ai",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/auto-approving-actions",
+ destination: "/docs/getting-started/settings",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/auto-cleanup",
+ destination: "/docs/getting-started/settings",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/features/model-temperature",
+ destination: "/docs/code-with-ai/agents/model-selection",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/rate-limits-costs",
+ destination: "/docs/getting-started/adding-credits",
+ basePath: false,
+ permanent: true,
+ },
+ {
+ source: "/advanced-usage/free-and-budget-models",
+ destination: "/docs/code-with-ai/agents/model-selection",
+ basePath: false,
+ permanent: true,
+ },
+]
diff --git a/packages/kilo-docs/public/globals.css b/packages/kilo-docs/public/globals.css
new file mode 100644
index 00000000000..d1e721f8b13
--- /dev/null
+++ b/packages/kilo-docs/public/globals.css
@@ -0,0 +1,385 @@
+@import url("https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;500;600;700&display=swap");
+@import "tailwindcss";
+
+@custom-variant dark (&:where(.dark, .dark *));
+
+:root {
+ --top-nav-height: 105px;
+ --border-color: #dce6e9;
+ --bg-color: theme(colors.zinc.50);
+ --bg-secondary: theme(colors.zinc.100);
+ --text-color: rgba(60, 66, 87, 1);
+ --text-secondary: theme(colors.slate.500);
+ --text-link: #5a7ab5;
+ --text-brand: #1a1a18;
+ --accent-color: theme(colors.indigo.500);
+ --accent-hover: theme(colors.indigo.600);
+}
+
+.dark {
+ --border-color: #3f3f3f;
+ --bg-color: #1a1a18;
+ --bg-secondary: #33332d;
+ --text-color: #a3a3a2;
+ --text-header: #e9e9e9;
+ --text-secondary: theme(colors.gray.300);
+ --text-link: theme(colors.slate.400);
+ --text-brand: #f8f674;
+ --text-brand-hover: #f8f675;
+ --accent-color: #f8f675;
+ --accent-hover: #f8f675;
+}
+
+*,
+*::before,
+*::after {
+ box-sizing: border-box;
+}
+
+html,
+body {
+ overflow-x: hidden;
+ max-width: 100vw;
+}
+
+body {
+ font-family:
+ ui-sans-serif,
+ system-ui,
+ -apple-system,
+ BlinkMacSystemFont,
+ "Segoe UI",
+ Roboto,
+ "Helvetica Neue",
+ Arial,
+ "Noto Sans",
+ sans-serif,
+ "Apple Color Emoji",
+ "Segoe UI Emoji",
+ "Segoe UI Symbol",
+ "Noto Color Emoji";
+ color: var(--text-color);
+ background-color: var(--bg-color);
+ margin: 0;
+ transition:
+ background-color 0.2s ease,
+ color 0.2s ease;
+}
+
+p {
+ line-height: 1.5em;
+}
+
+.article-content {
+ width: 100%;
+}
+
+.article-content p {
+ margin: 1em 0;
+}
+
+.article-content > * {
+ max-width: 100%;
+ overflow-wrap: break-word;
+ word-wrap: break-word;
+}
+
+.font-brand {
+ font-family: "JetBrains Mono", monospace;
+ font-weight: 500;
+ color: var(--text-brand);
+}
+
+h1 {
+ font-family: "JetBrains Mono", monospace;
+ font-weight: 700;
+ color: var(--text-brand);
+}
+
+h2,
+h3,
+h4,
+h5,
+h6 {
+ font-weight: 600;
+ color: var(--text-header);
+ margin: 1em 0 0.5em;
+}
+
+h1 {
+ font-size: 40px;
+}
+
+h2 {
+ font-size: 28px;
+}
+
+h3 {
+ font-size: 20px;
+}
+
+a {
+ color: var(--text-link);
+}
+
+a:hover {
+ color: var(--text-brand-hover);
+}
+
+/* Homepage Button Styles */
+.btn {
+ display: inline-flex;
+ align-items: center;
+ justify-content: center;
+ gap: 0.5rem;
+ padding: 0.5rem 1.5rem;
+ border-radius: 4px;
+ font-family: "JetBrains Mono", monospace;
+ font-weight: 500;
+ font-size: 1rem;
+ text-decoration: none;
+ transition: all 0.15s ease;
+ border: 2px solid transparent;
+}
+
+.btn-primary {
+ background: #f8f674;
+ color: #1a1a18 !important;
+ border-color: #f8f674;
+}
+
+.btn-primary:hover {
+ background: #ffff8d;
+ border-color: #ffff8d;
+ color: #1a1a18 !important;
+ transform: translateY(-1px);
+}
+
+.btn-secondary {
+ background: transparent;
+ color: #888 !important;
+ border: 2px solid #555;
+}
+
+.btn-secondary:hover {
+ color: #f8f674 !important;
+ border-color: #f8f674;
+}
+
+/* Terminal Syntax Highlighting */
+.terminal-comment {
+ color: #6a9955;
+}
+
+.terminal-prompt {
+ color: #dcdcaa;
+}
+
+/* Lists - Override Tailwind's reset to restore default list styling */
+.article-content ul,
+.article-content ol {
+ margin: 1em 0;
+ padding-left: 1.5em;
+ line-height: 1.75;
+}
+
+.article-content ul {
+ list-style-type: disc;
+}
+
+.article-content ol {
+ list-style-type: decimal;
+}
+
+.article-content li {
+ margin: 0.5em 0;
+}
+
+/* Dark mode code syntax highlighting */
+.dark pre[class*="language-"] {
+ background: #1f2937 !important;
+ text-shadow: none;
+ color: #e5e7eb;
+}
+
+.dark pre[class*="language-"] *,
+.dark code[class*="language-"] {
+ color: #e5e7eb;
+ text-shadow: none;
+}
+
+/* Ensure inline code also has proper color in dark mode */
+.dark code {
+ color: #e5e7eb;
+}
+
+.dark .token.comment,
+.dark .token.prolog,
+.dark .token.doctype,
+.dark .token.cdata {
+ color: #6b7280;
+}
+
+.dark .token.punctuation {
+ color: #9ca3af;
+}
+
+.dark .token.property,
+.dark .token.tag,
+.dark .token.boolean,
+.dark .token.number,
+.dark .token.constant,
+.dark .token.symbol,
+.dark .token.deleted {
+ color: #f87171;
+}
+
+.dark .token.selector,
+.dark .token.attr-name,
+.dark .token.string,
+.dark .token.char,
+.dark .token.builtin,
+.dark .token.inserted {
+ color: #34d399;
+}
+
+.dark .token.operator,
+.dark .token.entity,
+.dark .token.url,
+.dark .language-css .token.string,
+.dark .style .token.string {
+ color: #fbbf24;
+}
+
+.dark .token.atrule,
+.dark .token.attr-value,
+.dark .token.keyword {
+ color: #60a5fa;
+}
+
+.dark .token.function,
+.dark .token.class-name {
+ color: #f472b6;
+}
+
+.dark .token.regex,
+.dark .token.important,
+.dark .token.variable {
+ color: #fbbf24;
+}
+
+/* Mobile Responsive Styles */
+@media (max-width: 1024px) {
+ :root {
+ --top-nav-height: 60px;
+ }
+
+ /* Hide table of contents on tablet and below */
+ .toc-container {
+ display: none;
+ }
+}
+
+@media (max-width: 768px) {
+ :root {
+ --top-nav-height: 60px;
+ }
+
+ /* Hide desktop sidenav, show via mobile toggle */
+ .sidenav-desktop {
+ display: none;
+ }
+
+ /* Mobile sidenav overlay */
+ .sidenav-mobile-overlay {
+ position: fixed;
+ top: 0;
+ left: 0;
+ right: 0;
+ bottom: 0;
+ background: rgba(0, 0, 0, 0.5);
+ z-index: 40;
+ opacity: 0;
+ visibility: hidden;
+ transition:
+ opacity 0.3s ease,
+ visibility 0.3s ease;
+ }
+
+ .sidenav-mobile-overlay.open {
+ opacity: 1;
+ visibility: visible;
+ }
+
+ /* Mobile sidenav drawer */
+ .sidenav-mobile {
+ position: fixed;
+ top: var(--top-nav-height);
+ left: 0;
+ width: 280px;
+ height: calc(100vh - var(--top-nav-height));
+ background: var(--bg-color);
+ z-index: 50;
+ transform: translateX(-100%);
+ transition: transform 0.3s ease;
+ overflow-y: auto;
+ border-right: 1px solid var(--border-color);
+ }
+
+ .sidenav-mobile.open {
+ transform: translateX(0);
+ }
+
+ /* Hide desktop nav items */
+ .desktop-nav {
+ display: none !important;
+ }
+
+ /* Mobile menu button */
+ .mobile-menu-btn {
+ display: flex !important;
+ }
+
+ h1 {
+ font-size: 28px;
+ }
+
+ h2 {
+ font-size: 22px;
+ }
+
+ h3 {
+ font-size: 18px;
+ }
+}
+
+/* Hamburger menu icon */
+.hamburger {
+ display: flex;
+ flex-direction: column;
+ justify-content: space-between;
+ width: 20px;
+ height: 14px;
+ cursor: pointer;
+}
+
+.hamburger span {
+ display: block;
+ width: 100%;
+ height: 2px;
+ background: var(--text-color);
+ border-radius: 1px;
+ transition: all 0.3s ease;
+}
+
+.hamburger.open span:nth-child(1) {
+ transform: rotate(45deg) translate(4px, 4px);
+}
+
+.hamburger.open span:nth-child(2) {
+ opacity: 0;
+}
+
+.hamburger.open span:nth-child(3) {
+ transform: rotate(-45deg) translate(4px, -4px);
+}
diff --git a/packages/kilo-docs/static/img/browser-use/browser-use-1.png b/packages/kilo-docs/public/img/browser-use/browser-use-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/browser-use/browser-use-1.png
rename to packages/kilo-docs/public/img/browser-use/browser-use-1.png
diff --git a/packages/kilo-docs/static/img/browser-use/browser-use-2.png b/packages/kilo-docs/public/img/browser-use/browser-use-2.png
similarity index 100%
rename from packages/kilo-docs/static/img/browser-use/browser-use-2.png
rename to packages/kilo-docs/public/img/browser-use/browser-use-2.png
diff --git a/packages/kilo-docs/static/img/browser-use/browser-use-3.png b/packages/kilo-docs/public/img/browser-use/browser-use-3.png
similarity index 100%
rename from packages/kilo-docs/static/img/browser-use/browser-use-3.png
rename to packages/kilo-docs/public/img/browser-use/browser-use-3.png
diff --git a/packages/kilo-docs/static/img/browser-use/browser-use-4.png b/packages/kilo-docs/public/img/browser-use/browser-use-4.png
similarity index 100%
rename from packages/kilo-docs/static/img/browser-use/browser-use-4.png
rename to packages/kilo-docs/public/img/browser-use/browser-use-4.png
diff --git a/packages/kilo-docs/static/img/browser-use/browser-use-5.png b/packages/kilo-docs/public/img/browser-use/browser-use-5.png
similarity index 100%
rename from packages/kilo-docs/static/img/browser-use/browser-use-5.png
rename to packages/kilo-docs/public/img/browser-use/browser-use-5.png
diff --git a/packages/kilo-docs/static/img/browser-use/browser-use.png b/packages/kilo-docs/public/img/browser-use/browser-use.png
similarity index 100%
rename from packages/kilo-docs/static/img/browser-use/browser-use.png
rename to packages/kilo-docs/public/img/browser-use/browser-use.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints-1.png b/packages/kilo-docs/public/img/checkpoints/checkpoints-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints-1.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints-1.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints-2.png b/packages/kilo-docs/public/img/checkpoints/checkpoints-2.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints-2.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints-2.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints-3.png b/packages/kilo-docs/public/img/checkpoints/checkpoints-3.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints-3.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints-3.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints-4.png b/packages/kilo-docs/public/img/checkpoints/checkpoints-4.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints-4.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints-4.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints-6.png b/packages/kilo-docs/public/img/checkpoints/checkpoints-6.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints-6.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints-6.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints-7.png b/packages/kilo-docs/public/img/checkpoints/checkpoints-7.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints-7.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints-7.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints-9.png b/packages/kilo-docs/public/img/checkpoints/checkpoints-9.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints-9.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints-9.png
diff --git a/packages/kilo-docs/static/img/checkpoints/checkpoints.png b/packages/kilo-docs/public/img/checkpoints/checkpoints.png
similarity index 100%
rename from packages/kilo-docs/static/img/checkpoints/checkpoints.png
rename to packages/kilo-docs/public/img/checkpoints/checkpoints.png
diff --git a/packages/kilo-docs/public/img/code-actions/add-to-context.gif b/packages/kilo-docs/public/img/code-actions/add-to-context.gif
new file mode 100644
index 00000000000..7aee21a402d
--- /dev/null
+++ b/packages/kilo-docs/public/img/code-actions/add-to-context.gif
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:55548769d458acc44b8bd8597bda3e9e88a684eb75c831c59083c503499b57be
+size 26797913
diff --git a/packages/kilo-docs/static/img/code-actions/code-actions-1.png b/packages/kilo-docs/public/img/code-actions/code-actions-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/code-actions/code-actions-1.png
rename to packages/kilo-docs/public/img/code-actions/code-actions-1.png
diff --git a/packages/kilo-docs/static/img/codebase-indexing/codebase-indexing.png b/packages/kilo-docs/public/img/codebase-indexing/codebase-indexing.png
similarity index 100%
rename from packages/kilo-docs/static/img/codebase-indexing/codebase-indexing.png
rename to packages/kilo-docs/public/img/codebase-indexing/codebase-indexing.png
diff --git a/packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-4.png b/packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-4.png
similarity index 100%
rename from packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-4.png
rename to packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-4.png
diff --git a/packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-5.png b/packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-5.png
similarity index 100%
rename from packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-5.png
rename to packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-5.png
diff --git a/packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-6.png b/packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-6.png
similarity index 100%
rename from packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-6.png
rename to packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-6.png
diff --git a/packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-7.png b/packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-7.png
similarity index 100%
rename from packages/kilo-docs/static/img/connecting-api-provider/connecting-api-provider-7.png
rename to packages/kilo-docs/public/img/connecting-api-provider/connecting-api-provider-7.png
diff --git a/packages/kilo-docs/static/img/context-mentions/context-mentions-1.png b/packages/kilo-docs/public/img/context-mentions/context-mentions-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/context-mentions/context-mentions-1.png
rename to packages/kilo-docs/public/img/context-mentions/context-mentions-1.png
diff --git a/packages/kilo-docs/static/img/context-mentions/context-mentions-2.png b/packages/kilo-docs/public/img/context-mentions/context-mentions-2.png
similarity index 100%
rename from packages/kilo-docs/static/img/context-mentions/context-mentions-2.png
rename to packages/kilo-docs/public/img/context-mentions/context-mentions-2.png
diff --git a/packages/kilo-docs/static/img/context-mentions/context-mentions-3.png b/packages/kilo-docs/public/img/context-mentions/context-mentions-3.png
similarity index 100%
rename from packages/kilo-docs/static/img/context-mentions/context-mentions-3.png
rename to packages/kilo-docs/public/img/context-mentions/context-mentions-3.png
diff --git a/packages/kilo-docs/static/img/context-mentions/context-mentions-4.png b/packages/kilo-docs/public/img/context-mentions/context-mentions-4.png
similarity index 100%
rename from packages/kilo-docs/static/img/context-mentions/context-mentions-4.png
rename to packages/kilo-docs/public/img/context-mentions/context-mentions-4.png
diff --git a/packages/kilo-docs/static/img/context-mentions/context-mentions-5.png b/packages/kilo-docs/public/img/context-mentions/context-mentions-5.png
similarity index 100%
rename from packages/kilo-docs/static/img/context-mentions/context-mentions-5.png
rename to packages/kilo-docs/public/img/context-mentions/context-mentions-5.png
diff --git a/packages/kilo-docs/static/img/context-mentions/context-mentions-6.png b/packages/kilo-docs/public/img/context-mentions/context-mentions-6.png
similarity index 100%
rename from packages/kilo-docs/static/img/context-mentions/context-mentions-6.png
rename to packages/kilo-docs/public/img/context-mentions/context-mentions-6.png
diff --git a/packages/kilo-docs/static/img/context-mentions/context-mentions.png b/packages/kilo-docs/public/img/context-mentions/context-mentions.png
similarity index 100%
rename from packages/kilo-docs/static/img/context-mentions/context-mentions.png
rename to packages/kilo-docs/public/img/context-mentions/context-mentions.png
diff --git a/packages/kilo-docs/static/img/custom-instructions/custom-instructions-2.png b/packages/kilo-docs/public/img/custom-instructions/custom-instructions-2.png
similarity index 100%
rename from packages/kilo-docs/static/img/custom-instructions/custom-instructions-2.png
rename to packages/kilo-docs/public/img/custom-instructions/custom-instructions-2.png
diff --git a/packages/kilo-docs/static/img/custom-instructions/custom-instructions-3.png b/packages/kilo-docs/public/img/custom-instructions/custom-instructions-3.png
similarity index 100%
rename from packages/kilo-docs/static/img/custom-instructions/custom-instructions-3.png
rename to packages/kilo-docs/public/img/custom-instructions/custom-instructions-3.png
diff --git a/packages/kilo-docs/static/img/custom-instructions/custom-instructions.png b/packages/kilo-docs/public/img/custom-instructions/custom-instructions.png
similarity index 100%
rename from packages/kilo-docs/static/img/custom-instructions/custom-instructions.png
rename to packages/kilo-docs/public/img/custom-instructions/custom-instructions.png
diff --git a/packages/kilo-docs/static/img/custom-modes/custom-modes-2.png b/packages/kilo-docs/public/img/custom-modes/custom-modes-2.png
similarity index 100%
rename from packages/kilo-docs/static/img/custom-modes/custom-modes-2.png
rename to packages/kilo-docs/public/img/custom-modes/custom-modes-2.png
diff --git a/packages/kilo-docs/static/img/custom-modes/custom-modes.png b/packages/kilo-docs/public/img/custom-modes/custom-modes.png
similarity index 100%
rename from packages/kilo-docs/static/img/custom-modes/custom-modes.png
rename to packages/kilo-docs/public/img/custom-modes/custom-modes.png
diff --git a/packages/kilo-docs/static/img/custom-rules/custom-rules.png b/packages/kilo-docs/public/img/custom-rules/custom-rules.png
similarity index 100%
rename from packages/kilo-docs/static/img/custom-rules/custom-rules.png
rename to packages/kilo-docs/public/img/custom-rules/custom-rules.png
diff --git a/packages/kilo-docs/static/img/custom-rules/rules-ui.png b/packages/kilo-docs/public/img/custom-rules/rules-ui.png
similarity index 100%
rename from packages/kilo-docs/static/img/custom-rules/rules-ui.png
rename to packages/kilo-docs/public/img/custom-rules/rules-ui.png
diff --git a/packages/kilo-docs/static/img/enhance-prompt/after.png b/packages/kilo-docs/public/img/enhance-prompt/after.png
similarity index 100%
rename from packages/kilo-docs/static/img/enhance-prompt/after.png
rename to packages/kilo-docs/public/img/enhance-prompt/after.png
diff --git a/packages/kilo-docs/static/img/enhance-prompt/before.png b/packages/kilo-docs/public/img/enhance-prompt/before.png
similarity index 100%
rename from packages/kilo-docs/static/img/enhance-prompt/before.png
rename to packages/kilo-docs/public/img/enhance-prompt/before.png
diff --git a/packages/kilo-docs/static/img/enhance-prompt/custom-enhance-profile.png b/packages/kilo-docs/public/img/enhance-prompt/custom-enhance-profile.png
similarity index 100%
rename from packages/kilo-docs/static/img/enhance-prompt/custom-enhance-profile.png
rename to packages/kilo-docs/public/img/enhance-prompt/custom-enhance-profile.png
diff --git a/packages/kilo-docs/static/img/fast-edits/fast-edits-1.png b/packages/kilo-docs/public/img/fast-edits/fast-edits-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/fast-edits/fast-edits-1.png
rename to packages/kilo-docs/public/img/fast-edits/fast-edits-1.png
diff --git a/packages/kilo-docs/static/img/fast-edits/fast-edits-3.png b/packages/kilo-docs/public/img/fast-edits/fast-edits-3.png
similarity index 100%
rename from packages/kilo-docs/static/img/fast-edits/fast-edits-3.png
rename to packages/kilo-docs/public/img/fast-edits/fast-edits-3.png
diff --git a/packages/kilo-docs/static/img/fast-edits/fast-edits-4.png b/packages/kilo-docs/public/img/fast-edits/fast-edits-4.png
similarity index 100%
rename from packages/kilo-docs/static/img/fast-edits/fast-edits-4.png
rename to packages/kilo-docs/public/img/fast-edits/fast-edits-4.png
diff --git a/packages/kilo-docs/static/img/fast-edits/fast-edits-5.png b/packages/kilo-docs/public/img/fast-edits/fast-edits-5.png
similarity index 100%
rename from packages/kilo-docs/static/img/fast-edits/fast-edits-5.png
rename to packages/kilo-docs/public/img/fast-edits/fast-edits-5.png
diff --git a/packages/kilo-docs/static/img/fast-edits/fast-edits.png b/packages/kilo-docs/public/img/fast-edits/fast-edits.png
similarity index 100%
rename from packages/kilo-docs/static/img/fast-edits/fast-edits.png
rename to packages/kilo-docs/public/img/fast-edits/fast-edits.png
diff --git a/packages/kilo-docs/static/img/installing/installing-2.png b/packages/kilo-docs/public/img/installing-vsix.png
similarity index 100%
rename from packages/kilo-docs/static/img/installing/installing-2.png
rename to packages/kilo-docs/public/img/installing-vsix.png
diff --git a/packages/kilo-docs/static/img/kilo-v1-white.svg b/packages/kilo-docs/public/img/kilo-v1-white.svg
similarity index 100%
rename from packages/kilo-docs/static/img/kilo-v1-white.svg
rename to packages/kilo-docs/public/img/kilo-v1-white.svg
diff --git a/packages/kilo-docs/static/img/kilo-v1.svg b/packages/kilo-docs/public/img/kilo-v1.svg
similarity index 100%
rename from packages/kilo-docs/static/img/kilo-v1.svg
rename to packages/kilo-docs/public/img/kilo-v1.svg
diff --git a/packages/kilo-docs/public/img/logo.svg b/packages/kilo-docs/public/img/logo.svg
new file mode 100755
index 00000000000..aadb7d16cd2
--- /dev/null
+++ b/packages/kilo-docs/public/img/logo.svg
@@ -0,0 +1,6 @@
+
+
diff --git a/packages/kilo-docs/static/img/memory-bank/at-work.png b/packages/kilo-docs/public/img/memory-bank/at-work.png
similarity index 100%
rename from packages/kilo-docs/static/img/memory-bank/at-work.png
rename to packages/kilo-docs/public/img/memory-bank/at-work.png
diff --git a/packages/kilo-docs/static/img/modes/modes-1.png b/packages/kilo-docs/public/img/modes/modes-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/modes/modes-1.png
rename to packages/kilo-docs/public/img/modes/modes-1.png
diff --git a/packages/kilo-docs/static/img/modes/modes-2.png b/packages/kilo-docs/public/img/modes/modes-2.png
similarity index 100%
rename from packages/kilo-docs/static/img/modes/modes-2.png
rename to packages/kilo-docs/public/img/modes/modes-2.png
diff --git a/packages/kilo-docs/static/img/modes/modes.png b/packages/kilo-docs/public/img/modes/modes.png
similarity index 100%
rename from packages/kilo-docs/static/img/modes/modes.png
rename to packages/kilo-docs/public/img/modes/modes.png
diff --git a/packages/kilo-docs/static/img/settings-management/settings-management.png b/packages/kilo-docs/public/img/settings-management/settings-management.png
similarity index 100%
rename from packages/kilo-docs/static/img/settings-management/settings-management.png
rename to packages/kilo-docs/public/img/settings-management/settings-management.png
diff --git a/packages/kilo-docs/public/img/signupflow.gif b/packages/kilo-docs/public/img/signupflow.gif
new file mode 100644
index 00000000000..90a8f070b4b
--- /dev/null
+++ b/packages/kilo-docs/public/img/signupflow.gif
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46d07832f84a9980e414ae0700574438607aad581c0de79e9ae342d690b04d4f
+size 3679623
diff --git a/packages/kilo-docs/static/img/slash-commands/workflows.png b/packages/kilo-docs/public/img/slash-commands/workflows.png
similarity index 100%
rename from packages/kilo-docs/static/img/slash-commands/workflows.png
rename to packages/kilo-docs/public/img/slash-commands/workflows.png
diff --git a/packages/kilo-docs/static/img/task-todo-list/complete.png b/packages/kilo-docs/public/img/task-todo-list/complete.png
similarity index 100%
rename from packages/kilo-docs/static/img/task-todo-list/complete.png
rename to packages/kilo-docs/public/img/task-todo-list/complete.png
diff --git a/packages/kilo-docs/static/img/task-todo-list/in-progress.png b/packages/kilo-docs/public/img/task-todo-list/in-progress.png
similarity index 100%
rename from packages/kilo-docs/static/img/task-todo-list/in-progress.png
rename to packages/kilo-docs/public/img/task-todo-list/in-progress.png
diff --git a/packages/kilo-docs/static/img/task-todo-list/not-started.png b/packages/kilo-docs/public/img/task-todo-list/not-started.png
similarity index 100%
rename from packages/kilo-docs/static/img/task-todo-list/not-started.png
rename to packages/kilo-docs/public/img/task-todo-list/not-started.png
diff --git a/packages/kilo-docs/static/img/task-todo-list/task-header.png b/packages/kilo-docs/public/img/task-todo-list/task-header.png
similarity index 100%
rename from packages/kilo-docs/static/img/task-todo-list/task-header.png
rename to packages/kilo-docs/public/img/task-todo-list/task-header.png
diff --git a/packages/kilo-docs/static/img/task-todo-list/task-todo-list-1.png b/packages/kilo-docs/public/img/task-todo-list/task-todo-list-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/task-todo-list/task-todo-list-1.png
rename to packages/kilo-docs/public/img/task-todo-list/task-todo-list-1.png
diff --git a/packages/kilo-docs/static/img/teams/invite-member.png b/packages/kilo-docs/public/img/team-management/invite-member.png
similarity index 100%
rename from packages/kilo-docs/static/img/teams/invite-member.png
rename to packages/kilo-docs/public/img/team-management/invite-member.png
diff --git a/packages/kilo-docs/static/img/teams/create-team.png b/packages/kilo-docs/public/img/teams/create-team.png
similarity index 100%
rename from packages/kilo-docs/static/img/teams/create-team.png
rename to packages/kilo-docs/public/img/teams/create-team.png
diff --git a/packages/kilo-docs/static/img/teams/custom_modes.png b/packages/kilo-docs/public/img/teams/custom_modes.png
similarity index 100%
rename from packages/kilo-docs/static/img/teams/custom_modes.png
rename to packages/kilo-docs/public/img/teams/custom_modes.png
diff --git a/packages/kilo-docs/static/img/teams/dashboard.png b/packages/kilo-docs/public/img/teams/dashboard.png
similarity index 100%
rename from packages/kilo-docs/static/img/teams/dashboard.png
rename to packages/kilo-docs/public/img/teams/dashboard.png
diff --git a/packages/kilo-docs/public/img/teams/invite-member.png b/packages/kilo-docs/public/img/teams/invite-member.png
new file mode 100644
index 00000000000..976e37b0c5e
Binary files /dev/null and b/packages/kilo-docs/public/img/teams/invite-member.png differ
diff --git a/packages/kilo-docs/static/img/teams/org_credits.png b/packages/kilo-docs/public/img/teams/org_credits.png
similarity index 100%
rename from packages/kilo-docs/static/img/teams/org_credits.png
rename to packages/kilo-docs/public/img/teams/org_credits.png
diff --git a/packages/kilo-docs/static/img/teams/subscribe.png b/packages/kilo-docs/public/img/teams/subscribe.png
similarity index 100%
rename from packages/kilo-docs/static/img/teams/subscribe.png
rename to packages/kilo-docs/public/img/teams/subscribe.png
diff --git a/packages/kilo-docs/static/img/teams/usage-details.png b/packages/kilo-docs/public/img/teams/usage-details.png
similarity index 100%
rename from packages/kilo-docs/static/img/teams/usage-details.png
rename to packages/kilo-docs/public/img/teams/usage-details.png
diff --git a/packages/kilo-docs/static/img/typing-your-requests/typing-your-requests.png b/packages/kilo-docs/public/img/typing-your-requests/typing-your-requests.png
similarity index 100%
rename from packages/kilo-docs/static/img/typing-your-requests/typing-your-requests.png
rename to packages/kilo-docs/public/img/typing-your-requests/typing-your-requests.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/mcp-installed-config.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/mcp-installed-config.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/mcp-installed-config.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/mcp-installed-config.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-1.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-1.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-1.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-1.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-10.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-10.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-10.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-10.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-2.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-2.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-2.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-2.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-3.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-3.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-3.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-3.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-4.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-4.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-4.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-4.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-5.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-5.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-5.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-5.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-6.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-6.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-6.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-6.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-7.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-7.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-7.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-7.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-8.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-8.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-8.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-8.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-9.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-9.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-9.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code-9.png
diff --git a/packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code.png b/packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code.png
similarity index 100%
rename from packages/kilo-docs/static/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code.png
rename to packages/kilo-docs/public/img/using-mcp-in-kilo-code/using-mcp-in-kilo-code.png
diff --git a/packages/kilo-docs/static/img/your-first-task/your-first-task-6.png b/packages/kilo-docs/public/img/your-first-task/your-first-task-6.png
similarity index 100%
rename from packages/kilo-docs/static/img/your-first-task/your-first-task-6.png
rename to packages/kilo-docs/public/img/your-first-task/your-first-task-6.png
diff --git a/packages/kilo-docs/static/img/your-first-task/your-first-task-7.png b/packages/kilo-docs/public/img/your-first-task/your-first-task-7.png
similarity index 100%
rename from packages/kilo-docs/static/img/your-first-task/your-first-task-7.png
rename to packages/kilo-docs/public/img/your-first-task/your-first-task-7.png
diff --git a/packages/kilo-docs/static/img/your-first-task/your-first-task-8.png b/packages/kilo-docs/public/img/your-first-task/your-first-task-8.png
similarity index 100%
rename from packages/kilo-docs/static/img/your-first-task/your-first-task-8.png
rename to packages/kilo-docs/public/img/your-first-task/your-first-task-8.png
diff --git a/packages/kilo-docs/static/img/your-first-task/your-first-task.png b/packages/kilo-docs/public/img/your-first-task/your-first-task.png
similarity index 100%
rename from packages/kilo-docs/static/img/your-first-task/your-first-task.png
rename to packages/kilo-docs/public/img/your-first-task/your-first-task.png
diff --git a/packages/kilo-docs/public/setting-up/signupflow.gif b/packages/kilo-docs/public/setting-up/signupflow.gif
new file mode 100644
index 00000000000..90a8f070b4b
--- /dev/null
+++ b/packages/kilo-docs/public/setting-up/signupflow.gif
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:46d07832f84a9980e414ae0700574438607aad581c0de79e9ae342d690b04d4f
+size 3679623
diff --git a/packages/kilo-docs/sidebars.ts b/packages/kilo-docs/sidebars.ts
deleted file mode 100644
index d546ef7653e..00000000000
--- a/packages/kilo-docs/sidebars.ts
+++ /dev/null
@@ -1,270 +0,0 @@
-import type { SidebarsConfig } from "@docusaurus/plugin-content-docs"
-
-const sidebars: SidebarsConfig = {
- tutorialSidebar: [
- "index",
- {
- type: "category",
- label: "Getting Started",
- items: [
- "getting-started/installing",
- "getting-started/concepts",
- {
- type: "doc",
- id: "getting-started/setting-up",
- label: "Setup",
- },
- "getting-started/your-first-task",
- ],
- },
- {
- type: "category",
- label: "Using Kilo Code",
- items: [
- "basic-usage/the-chat-interface",
- "basic-usage/model-selection-guide",
- "basic-usage/using-modes",
- {
- type: "category",
- label: "Autocomplete",
- link: {
- type: "doc",
- id: "basic-usage/autocomplete/index",
- },
- items: ["basic-usage/autocomplete/mistral-setup"],
- },
- "basic-usage/context-mentions",
- {
- type: "category",
- label: "Basic Features",
- items: [
- "basic-usage/orchestrator-mode",
- "basic-usage/task-todo-list",
- "basic-usage/git-commit-generation",
- "features/browser-use",
- "features/code-actions",
- "features/system-notifications",
- "features/more-features",
- ],
- },
- {
- type: "category",
- label: "AI Model Providers",
- items: [
- "basic-usage/connecting-providers",
- "getting-started/connecting-api-provider",
- "features/api-configuration-profiles",
- "providers/kilocode",
- {
- type: "category",
- label: "Other Providers",
- items: [
- "providers/anthropic",
- "providers/bedrock",
- "providers/cerebras", // kilocode_change
- "providers/openai-chatgpt-plus-pro", // kilocode_change
- "providers/chutes-ai",
- "providers/claude-code",
- "providers/deepseek",
- "providers/fireworks",
- "providers/gemini",
- "providers/glama",
- "providers/groq",
- "providers/human-relay",
- "providers/inception", // kilocode_change
- "providers/lmstudio",
- "providers/minimax", // kilocode_change (M2 model update)
- "providers/mistral",
- "providers/moonshot", // kilocode_change
- "providers/ollama",
- "providers/openai",
- "providers/openai-compatible",
- "providers/openrouter",
- "providers/ovhcloud", // kilocode_change
- "providers/requesty",
- "providers/synthetic", // kilocode_change
- "providers/unbound",
- "providers/v0",
- "providers/vercel-ai-gateway",
- "providers/vertex",
- "providers/virtual-quota-fallback",
- "providers/vscode-lm",
- "providers/xai",
- ],
- },
- ],
- },
- "basic-usage/byok",
- "basic-usage/adding-credits",
- "basic-usage/settings-management",
- ],
- },
- {
- type: "category",
- label: "Core Concepts",
- items: [
- "features/auto-approving-actions",
- "features/suggested-responses",
- "basic-usage/how-tools-work",
- "features/enhance-prompt",
- "features/checkpoints",
- "tips-and-tricks",
- ],
- },
- {
- type: "category",
- label: "Kilo Paid Plans",
- items: [
- "plans/about",
- "plans/getting-started",
- "plans/dashboard",
- "plans/analytics",
- {
- type: "category",
- label: "AI Adoption Dashboard",
- items: [
- "plans/adoption-dashboard/overview",
- "plans/adoption-dashboard/understanding-your-score",
- "plans/adoption-dashboard/improving-your-score",
- "plans/adoption-dashboard/for-team-leads",
- ],
- },
- "plans/team-management",
- "plans/custom-modes",
- "plans/billing",
- {
- type: "category",
- label: "Enterprise-Only Features",
- items: ["plans/enterprise/SSO", "plans/enterprise/model-access", "plans/enterprise/audit-logs"],
- },
- "plans/migration",
- ],
- },
- {
- type: "category",
- label: "Agent Behavior",
- items: [
- "agent-behavior/prompt-engineering",
- "agent-behavior/agents-md",
- "agent-behavior/custom-modes",
- "agent-behavior/custom-rules",
- "agent-behavior/custom-instructions",
- "agent-behavior/workflows",
- "agent-behavior/skills",
- ],
- },
- {
- type: "category",
- label: "Advanced Usage",
- items: [
- "advanced-usage/migrating-from-cursor-windsurf",
- {
- type: "category",
- label: "Advanced Context Features",
- items: [
- "advanced-usage/memory-bank",
- "features/codebase-indexing",
- "advanced-usage/large-projects",
- ],
- },
- {
- type: "category",
- label: "Advanced AI Features",
- items: [
- "features/fast-edits",
- "features/model-temperature",
- "advanced-usage/rate-limits-costs",
- "advanced-usage/free-and-budget-models",
- "features/footgun-prompting",
- ],
- },
- "features/auto-launch-configuration",
- "advanced-usage/auto-cleanup",
- "advanced-usage/integrations",
- "advanced-usage/appbuilder",
- "advanced-usage/cloud-agent",
- "advanced-usage/code-reviews",
- "advanced-usage/deploy",
- "advanced-usage/managed-indexing",
- "advanced-usage/agent-manager",
- "advanced-usage/sessions",
- "features/experimental/experimental-features",
- ],
- },
- {
- type: "category",
- label: "Extending Kilo Code",
- items: [
- "advanced-usage/local-models",
- {
- type: "category",
- label: "Model Context Protocol (MCP)",
- items: [
- "features/mcp/overview",
- "features/mcp/using-mcp-in-kilo-code",
- "features/mcp/using-mcp-in-cli",
- "features/mcp/what-is-mcp",
- "features/mcp/server-transports",
- "features/mcp/mcp-vs-api",
- ],
- },
- "features/shell-integration",
- ],
- },
- {
- type: "category",
- label: "Contributing",
- items: [
- "contributing/index",
- "contributing/development-environment",
- {
- type: "category",
- label: "Architecture",
- items: [
- {
- type: "doc",
- id: "contributing/architecture/index",
- label: "Overview",
- },
- "contributing/architecture/annual-billing",
- "contributing/architecture/enterprise-mcp-controls",
- "contributing/architecture/onboarding-engagement-improvements",
- "contributing/architecture/organization-modes-library",
- "contributing/architecture/security-reviews",
- "contributing/architecture/track-repo-url",
- "contributing/architecture/vercel-ai-gateway",
- "contributing/architecture/voice-transcription",
- "contributing/architecture/model-o11y",
- ],
- },
- ],
- },
- {
- type: "category",
- label: "Tools Reference",
- items: [
- "features/tools/tool-use-overview",
- "features/tools/access-mcp-resource",
- "features/tools/apply-diff",
- "features/tools/ask-followup-question",
- "features/tools/attempt-completion",
- "features/tools/browser-action",
- "features/tools/delete-file",
- "features/tools/execute-command",
- "features/tools/list-code-definition-names",
- "features/tools/list-files",
- "features/tools/new-task",
- "features/tools/read-file",
- "features/tools/search-files",
- "features/tools/switch-mode",
- "features/tools/update-todo-list",
- "features/tools/use-mcp-tool",
- "features/tools/write-to-file",
- ],
- },
- "cli",
- "slack",
- ],
-}
-
-export default sidebars
diff --git a/packages/kilo-docs/src/components/Codicon.tsx b/packages/kilo-docs/src/components/Codicon.tsx
deleted file mode 100644
index 653ea2e4452..00000000000
--- a/packages/kilo-docs/src/components/Codicon.tsx
+++ /dev/null
@@ -1,15 +0,0 @@
-import React from 'react';
-import '@vscode/codicons/dist/codicon.css';
-
-interface CodiconProps {
- name: string;
-}
-
-export default function Codicon({ name }: CodiconProps): JSX.Element {
- return (
-
- );
-}
\ No newline at end of file
diff --git a/packages/kilo-docs/src/components/Image.js b/packages/kilo-docs/src/components/Image.js
deleted file mode 100644
index 41759303067..00000000000
--- a/packages/kilo-docs/src/components/Image.js
+++ /dev/null
@@ -1,28 +0,0 @@
-import React from 'react';
-
-/**
- * Renders an image with an optional caption.
- * @param {object} props - The component props.
- * @param {string} props.src - The image source URL.
- * @param {string} props.alt - The alt text for the image.
- * @param {string} [props.width] - The width of the image.
- * @param {string} [props.caption] - The optional caption for the image.
- * @returns {JSX.Element} The Image component.
- */
-const Image = ({ src, alt, width, caption }) => {
- return (
-
+
+
+ {/* Quick Links Panel - Stripe style */}
+ Kilo Code Documentation
++ Explore our guides and examples to build with Kilo Code, the most popular open source coding + agent. +
+
+
+ Get started with Kilo Code →
+
+
+ Explore all features
+
+
+
+
+
+
+ POPULAR GUIDES
+
+
+ Installation Guide
+
+
+ Chat Interface
+
+
+ Your First Task
+
+
+
+
+ PLATFORMS
+
+
+ VS Code Extension
+
+
+ JetBrains Extension
+
+
+ CLI
+
+
+
+ {categories.slice(0, 3).map((category) => (
+
+
+
+ ))}
+ {category.title}
+
+ {category.links.map((link) => (
+
+ {link.title}
+
+ ))}
+
+ Browse by topic
+
+ {categories.map((category) => (
+
+
+ {category.icon}
+ {category.title}
+{category.description}
+ + + + + ))} +
+
+ Try it out
+Get started quickly with common Kilo Code commands
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Terminal
+
+
+
+ {terminalContent[activeTab]}
+
+
+
+
+ 💬
+
+
+ Need help?
+
+ Join our Discord
+
+
+
+ 📝
+
+
+ Check out our
+
+ Changelog
+
+
+
+ 🐛
+
+
+ Found a bug?
+
+ Report an issue
+
+
+
- 
- {caption && (
- <>
-
- - {caption} - - - )} -
- );
-};
-
-export default Image;
\ No newline at end of file
diff --git a/packages/kilo-docs/src/components/ReportIssue/index.js b/packages/kilo-docs/src/components/ReportIssue/index.js
deleted file mode 100644
index 15c48d17672..00000000000
--- a/packages/kilo-docs/src/components/ReportIssue/index.js
+++ /dev/null
@@ -1,22 +0,0 @@
-import React from 'react';
-import {useLocation} from '@docusaurus/router';
-import {GITHUB_NEW_ISSUE_URL} from '@site/src/constants';
-import styles from './styles.module.css';
-
-export default function ReportIssue() {
- const {pathname} = useLocation();
-
- const issueUrl = `${GITHUB_NEW_ISSUE_URL}?title=Documentation%20Issue:%20${encodeURIComponent(pathname)}`;
-
- return (
- - - {caption} - - - )} -
-
-
- );
-}
\ No newline at end of file
diff --git a/packages/kilo-docs/src/components/ReportIssue/styles.module.css b/packages/kilo-docs/src/components/ReportIssue/styles.module.css
deleted file mode 100644
index 5656eb29a77..00000000000
--- a/packages/kilo-docs/src/components/ReportIssue/styles.module.css
+++ /dev/null
@@ -1,20 +0,0 @@
-.reportContainer {
- margin-top: 3rem;
- margin-bottom: 1rem;
-}
-
-.separator {
- margin-top: 2rem;
- margin-bottom: 1rem;
- border: 0;
- border-top: 1px solid var(--ifm-color-emphasis-300);
-}
-
-.reportLink {
- font-size: 0.875rem;
- color: var(--ifm-color-emphasis-700);
-}
-
-.reportLink a {
- font-weight: 500;
-}
\ No newline at end of file
diff --git a/packages/kilo-docs/src/components/YouTubeEmbed/index.tsx b/packages/kilo-docs/src/components/YouTubeEmbed/index.tsx
deleted file mode 100644
index 544bb17a209..00000000000
--- a/packages/kilo-docs/src/components/YouTubeEmbed/index.tsx
+++ /dev/null
@@ -1,242 +0,0 @@
-import React, { useState, useCallback, useEffect, useMemo } from 'react';
-import styles from './styles.module.css';
-
-/**
- * YouTube embed parameters interface
- * @see https://developers.google.com/youtube/player_parameters
- */
-interface YouTubeEmbedParams {
- /** Show related videos at the end (0 = no, 1 = yes) */
- rel?: 0 | 1;
- /** Use YouTube's modest branding (0 = no, 1 = yes) */
- modestbranding?: 0 | 1;
- /** Enable privacy-enhanced mode (0 = no, 1 = yes) */
- privacy?: 0 | 1;
- /** Auto-play the video (0 = no, 1 = yes) */
- autoplay?: 0 | 1;
- /** Show video controls (0 = no, 1 = yes) */
- controls?: 0 | 1;
- /** Show video info (0 = no, 1 = yes) */
- showinfo?: 0 | 1;
- /** Loop the video (0 = no, 1 = yes) */
- loop?: 0 | 1;
- /** Start time in seconds */
- start?: number;
- /** End time in seconds */
- end?: number;
-}
-
-interface YouTubeEmbedProps {
- /**
- * YouTube video URL or video ID
- */
- url: string;
- /**
- * Optional caption to display below the video
- */
- caption?: string;
- /**
- * Optional title for the iframe (for accessibility)
- */
- title?: string;
- /**
- * Optional YouTube embed parameters
- */
- embedParams?: YouTubeEmbedParams;
- /**
- * Optional callback for when the video fails to load
- */
- onError?: (error: Error) => void;
- /**
- * Optional callback for when the video successfully loads
- */
- onLoad?: () => void;
-}
-
-/**
- * Error that occurs when a YouTube video ID cannot be extracted
- */
-class YouTubeExtractError extends Error {
- constructor(url: string) {
- super(`Could not extract YouTube video ID from: ${url}`);
- this.name = 'YouTubeExtractError';
- }
-}
-
-/**
- * Extracts the YouTube video ID from a URL or returns the ID if already provided
- * @param {string} urlOrId - YouTube URL or video ID
- * @returns {string | null} YouTube video ID or null if extraction fails
- */
-const extractVideoId = (urlOrId: string): string | null => {
- // Trim whitespace
- const trimmedUrl = urlOrId.trim();
-
- // If empty, return null
- if (!trimmedUrl) {
- return null;
- }
-
- // If it's just the ID (no slashes or dots)
- if (!/[\/.]/.test(trimmedUrl) && /^[a-zA-Z0-9_-]{11}$/.test(trimmedUrl)) {
- return trimmedUrl;
- }
-
- // Extract from various YouTube URL formats
- const regexPatterns = [
- /(?:youtube\.com\/watch\?v=|youtu\.be\/|youtube\.com\/embed\/)([a-zA-Z0-9_-]{11})/,
- /youtube\.com\/watch\?.*v=([a-zA-Z0-9_-]{11})/,
- /youtube\.com\/shorts\/([a-zA-Z0-9_-]{11})/,
- ];
-
- for (const regex of regexPatterns) {
- const match = trimmedUrl.match(regex);
- if (match && match[1]) {
- return match[1];
- }
- }
-
- // If no pattern matches, return null
- return null;
-};
-
-/**
- * Builds the YouTube embed URL with parameters
- * @param {string} videoId - YouTube video ID
- * @param {YouTubeEmbedParams} params - Embed parameters
- * @returns {string} Complete embed URL
- */
-const buildEmbedUrl = (videoId: string, params: YouTubeEmbedParams = {}): string => {
- // Start with base URL
- const baseUrl = params.privacy
- ? `https://www.youtube-nocookie.com/embed/${videoId}`
- : `https://www.youtube.com/embed/${videoId}`;
-
- // Default parameters
- const defaultParams: YouTubeEmbedParams = {
- rel: 0,
- modestbranding: 1,
- controls: 1,
- };
-
- // Merge default and custom parameters
- const mergedParams = { ...defaultParams, ...params };
-
- // Convert parameters to URL query string
- const queryParams = Object.entries(mergedParams)
- .map(([key, value]) => `${key}=${value}`)
- .join('&');
-
- return `${baseUrl}?${queryParams}`;
-};
-
-/**
- * A responsive YouTube video embed component with enhanced features
- *
- * @example
- * // With video ID
- * -
- Is this documentation incorrect or incomplete?
-
- Report an issue on GitHub
-
-
-
-
- );
- }
-
- return (
-
-
- {caption && ⚠️
- Failed to load YouTube video
-{error.message}
-{caption}
}
-
-
- );
-}
\ No newline at end of file
diff --git a/packages/kilo-docs/src/components/YouTubeEmbed/styles.module.css b/packages/kilo-docs/src/components/YouTubeEmbed/styles.module.css
deleted file mode 100644
index fa68fec9d83..00000000000
--- a/packages/kilo-docs/src/components/YouTubeEmbed/styles.module.css
+++ /dev/null
@@ -1,60 +0,0 @@
-.youtubeWrapper {
- max-width: 85%;
- margin: 0 auto;
- width: 100%;
-}
-
-.videoContainer {
- position: relative;
- width: 100%;
- padding-bottom: 56.25%; /* 16:9 aspect ratio */
- margin-bottom: 1.5rem;
- overflow: hidden;
- border-radius: 8px;
- box-shadow: 0 4px 6px rgba(0, 0, 0, 0.1);
-}
-
-.videoIframe {
- position: absolute;
- top: 0;
- left: 0;
- width: 100%;
- height: 100%;
- border: 0;
- transition: opacity 0.3s ease;
-}
-
-.videoIframe.loading {
- opacity: 0.7;
-}
-
-.caption {
- margin-top: 0.5rem;
- text-align: center;
- font-size: 0.875rem;
- color: var(--ifm-color-emphasis-700);
- font-style: italic;
-}
-
-.errorContainer {
- display: flex;
- flex-direction: column;
- align-items: center;
- justify-content: center;
- background-color: var(--ifm-color-emphasis-100);
- border-radius: 8px;
- padding: 2rem;
- text-align: center;
-}
-
-.errorIcon {
- font-size: 2rem;
- color: var(--ifm-color-danger);
- margin-bottom: 1rem;
-}
-
-@media (max-width: 768px) {
- .youtubeWrapper {
- max-width: 95%;
- }
-}
\ No newline at end of file
diff --git a/packages/kilo-docs/src/constants.ts b/packages/kilo-docs/src/constants.ts
deleted file mode 100644
index 95d3a4f7956..00000000000
--- a/packages/kilo-docs/src/constants.ts
+++ /dev/null
@@ -1,29 +0,0 @@
-/**
- * Application-wide constants for use in TypeScript environments
- */
-
-// GitHub repository information
-export const GITHUB_REPO_URL = "https://github.com/Kilo-Org/docs"
-export const GITHUB_ISSUES_URL = `${GITHUB_REPO_URL}/issues`
-export const GITHUB_NEW_ISSUE_URL = `${GITHUB_ISSUES_URL}/new`
-
-// Community links
-export const DISCORD_URL = "https://kilocode.ai/discord"
-export const REDDIT_URL = "https://www.reddit.com/r/kilocode/"
-export const TWITTER_URL = "https://x.com/kilocode"
-export const YOUTUBE_URL = "https://www.youtube.com/@Kilo-Code"
-
-// GitHub links
-export const GITHUB_MAIN_REPO_URL = "https://github.com/Kilo-Org/kilocode"
-export const GITHUB_ISSUES_MAIN_URL = `${GITHUB_MAIN_REPO_URL}/issues`
-export const GITHUB_FEATURES_URL = `${GITHUB_MAIN_REPO_URL}/discussions/categories/ideas`
-
-// Download links
-export const VSCODE_MARKETPLACE_URL = "https://marketplace.visualstudio.com/items?itemName=kilocode.kilo-code"
-export const OPEN_VSX_URL = "https://open-vsx.org/extension/kilocode/kilo-code"
-
-// Company links
-export const CONTACT_EMAIL = "mailto:hi@kilocode.ai"
-export const CAREERS_URL = "https://kilocode.ai"
-export const WEBSITE_PRIVACY_URL = "https://kilocode.ai/privacy"
-export const EXTENSION_PRIVACY_URL = `${GITHUB_MAIN_REPO_URL}/blob/main/PRIVACY.md`
diff --git a/packages/kilo-docs/src/css/custom.css b/packages/kilo-docs/src/css/custom.css
deleted file mode 100644
index e21bf8dc1c6..00000000000
--- a/packages/kilo-docs/src/css/custom.css
+++ /dev/null
@@ -1,98 +0,0 @@
-/**
- * Any CSS included here will be global. The classic template
- * bundles Infima by default. Infima is a CSS framework designed to
- * work well for content-centric websites.
- */
-
-/* You can override the default Infima variables here. */
-:root {
- --ifm-color-primary: #2961df;
- --ifm-color-primary-dark: #1f55cf;
- --ifm-color-primary-darker: #1d50c3;
- --ifm-color-primary-darkest: #1842a1;
- --ifm-color-primary-light: #4072e2;
- --ifm-color-primary-lighter: #4b7ae4;
- --ifm-color-primary-lightest: #6e94e9;
- --ifm-code-font-size: 95%;
- --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.1);
-}
-
-/* For readability concerns, you should choose a lighter palette in dark mode. */
-[data-theme='dark'] {
- --ifm-color-primary: #25c2a0;
- --ifm-color-primary-dark: #21af90;
- --ifm-color-primary-darker: #1fa588;
- --ifm-color-primary-darkest: #1a8870;
- --ifm-color-primary-light: #29d5b0;
- --ifm-color-primary-lighter: #32d8b4;
- --ifm-color-primary-lightest: #4fddbf;
- --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.3);
-}
-
-/* Hide unwanted navigation items */
-.menu__list-item:has(> .menu__link[href="/docs"]),
-.menu__list-item:has(> .menu__link[href="/tutorial"]) {
- display: none;
-}
-
-/* Hide unwanted footer items */
-.footer__link-item[href="/docs"],
-.footer__link-item[href="/tutorial"] {
- display: none;
-}
-
-/* Video Grid Styles */
-.video-grid {
- display: grid;
- grid-template-columns: repeat(auto-fit, minmax(400px, 1fr));
- gap: 2rem;
- margin: 2rem 0;
- max-width: 1200px;
- margin-left: auto;
- margin-right: auto;
-}
-
-.video-container {
- position: relative;
- width: 100%;
- padding-bottom: 56.25%; /* 16:9 Aspect Ratio */
- border-radius: var(--ifm-card-border-radius);
- overflow: hidden;
-}
-
-.video-container iframe {
- position: absolute;
- top: 0;
- left: 0;
- width: 100%;
- height: 100%;
- border: 0;
-}
-
-.video-info {
- margin-top: 0.75rem;
-}
-
-.video-title {
- font-weight: 500;
- color: var(--ifm-heading-color);
- display: -webkit-box;
- -webkit-line-clamp: 2;
- -webkit-box-orient: vertical;
- overflow: hidden;
- line-height: 1.4;
- max-height: 2.8em; /* 2 lines * 1.4 line-height */
-}
-
-/* Basic Codicon styles */
-.codicon {
- vertical-align: middle;
- line-height: 1;
-}
-
-/* Ensure code blocks wrap instead of scrolling */
-pre {
- white-space: pre-wrap !important; /* Allows wrapping */
- word-wrap: break-word !important; /* Breaks long words */
- overflow-x: auto; /* Enables horizontal scrolling if necessary */
-}
\ No newline at end of file
diff --git a/packages/kilo-docs/src/theme/DocItem/index.js b/packages/kilo-docs/src/theme/DocItem/index.js
deleted file mode 100644
index 52d371ed6a3..00000000000
--- a/packages/kilo-docs/src/theme/DocItem/index.js
+++ /dev/null
@@ -1,12 +0,0 @@
-import React from 'react';
-import DocItem from '@theme-original/DocItem';
-import ReportIssue from '@site/src/components/ReportIssue';
-
-export default function DocItemWrapper(props) {
- return (
- <>
-
- {videoId && (
-
- )}
-
- {caption && (
-
- {caption}
-
- )}
-