feat: add Kilo Code configurator for AutoConfig support

[Nonanti]

Summary

• Adds KiloCodeConfigurator to enable automatic MCP configuration for Kilo Code VS Code extension users
• Implements platform-specific config paths for Windows, macOS, and Linux
• Uses IsVsCodeLayout = true as Kilo Code stores settings in VS Code's globalStorage

Config Paths

• Windows: %APPDATA%/Code/User/globalStorage/kilocode.kilo-code/settings/mcp_settings.json
• macOS: ~/Library/Application Support/Code/User/globalStorage/kilocode.kilo-code/settings/mcp_settings.json
• Linux: ~/.config/Code/User/globalStorage/kilocode.kilo-code/settings/mcp_settings.json

Test Plan

• Open MCP for Unity window in Unity Editor
• Verify "Kilo Code" appears in the client list
• Test "Check Status" button with Kilo Code installed
• Test "Configure" button to auto-configure MCP settings

Closes #250

Summary by CodeRabbit

• New Features
  • Kilo Code editor integration for the Unity Editor with automatic platform detection and support for Windows, macOS, and Linux.
  • In-editor, step‑by‑step installation and configuration guidance to help set up the Kilo Code extension and MCP settings in VS Code.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Adds a new editor configurator class, KiloCodeConfigurator, that extends JsonFileMcpConfigurator, initializes an McpClient with platform-specific VS Code paths and IsVsCodeLayout = true, and supplies a list of installation/configuration steps.

Changes

Cohort / File(s)	Change Summary
Kilo Code Configurator MCPForUnity/Editor/Clients/Configurators/KiloCodeConfigurator.cs	New class KiloCodeConfigurator added. Inherits JsonFileMcpConfigurator, constructs an McpClient with Windows/macOS/Linux VS Code paths and IsVsCodeLayout = true, and overrides GetInstallationSteps() to return step-by-step setup instructions for the Kilo Code extension and MCP settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Single-file addition following an existing configurator pattern.
• Review focus: correctness of platform paths, serialization/constructor usage, and clarity of installation steps.

Possibly related PRs

• Add CodeBuddy CLI configurator #403 — Adds a similar JsonFileMcpConfigurator-derived configurator with platform-specific paths and GetInstallationSteps override.

Poem

🐰 I hopped to the code with a curious cheer,
Kilo paths set for each OS near,
A configurator stitched, neat and bright,
Guiding installs by vscode light,
Hooray — setup's ready, let's code tonight! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: adding a Kilo Code configurator for AutoConfig support, which is the primary objective of this pull request.
Linked Issues check	✅ Passed	The pull request implements all coding requirements from issue #250: adds KiloCodeConfigurator class, integrates it with AutoConfig, implements platform-specific config paths, and sets proper VS Code layout handling.
Out of Scope Changes check	✅ Passed	All changes are directly related to issue #250 objectives. Only the KiloCodeConfigurator class is added, which is the core requirement for supporting Kilo Code in AutoConfig.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf2078b and 6168df4.

📒 Files selected for processing (1)

• MCPForUnity/Editor/Clients/Configurators/KiloCodeConfigurator.cs (1 hunks)

🔇 Additional comments (3)

MCPForUnity/Editor/Clients/Configurators/KiloCodeConfigurator.cs (3)

1-7: LGTM!

The imports and namespace declaration are appropriate for the functionality implemented.

---

8-18: Implementation looks correct; paths follow VS Code's standard extension storage pattern.

The configuration properly uses platform-specific special folders (ApplicationData for Windows, UserProfile with standard subdirectories for macOS/Linux) to locate the Kilo Code VS Code extension's globalStorage settings. The IsVsCodeLayout = true flag is appropriately set since Kilo Code is a VS Code extension. The class structure and constructor pattern are consistent with the codebase conventions.

---

20-27: Installation steps are accurate for Kilo Code's MCP configuration workflow.

The terminology "mcpServers object" and "Edit Global MCP Settings" correctly reflect Kilo Code's configuration structure and UI. The steps provide appropriate guidance for users to configure MCP servers via the extension's settings interface.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

MCPForUnity/Editor/Clients/Configurators/KiloCodeConfigurator.cs (3)

10-17: Platform-specific config paths look consistent with stated targets; consider non-default VS Code installs

The Windows/macOS/Linux paths align with the documented Kilo Code locations and the PR objectives. If you expect users on VS Code Insiders, OSS builds (e.g., Code - OSS / VSCodium), or portable installs, you may eventually want to extend this to alternate Code roots or surface a way to override the path in the UI.

---

16-16: Double-check that IsVsCodeLayout = true matches Kilo’s JSON structure, not just storage location

IsVsCodeLayout is documented on McpClient as “config file follows VS Code layout (env object at root)”, which is about the JSON shape. Kilo’s mcp_settings.json under globalStorage may have its own schema; if it doesn’t mirror the standard VS Code layout with an env object at the root, this flag could cause JsonFileMcpConfigurator to read/write the file incorrectly. Please confirm the actual Kilo file structure and flip this to false (or adjust the configurator) if the layout differs.

---

20-27: Installation steps are clear; consider tightening language around the mcpServers object

The steps are concise and actionable. To reduce ambiguity, you might explicitly state that users should create the mcpServers object if it doesn’t already exist and that they’re editing the same mcp_settings.json file pointed to by the auto-config path, to avoid confusion with other MCP-related settings in VS Code/Kilo.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b09e48a and cf2078b.

📒 Files selected for processing (1)

• MCPForUnity/Editor/Clients/Configurators/KiloCodeConfigurator.cs (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (1)

MCPForUnity/Editor/Clients/Configurators/KiloCodeConfigurator.cs (1)

MCPForUnity/Editor/Models/McpClient.cs (1)

• McpClient (5-55)