--- title: "Kimi subscription access in Visual Studio 2026 | iolys" description: "Use your eligible Kimi Code subscription in Visual Studio 2026. Track usage, choose reasoning effort, and use native web tools with iolys for C# and .NET." url: "https://getiolys.com/providers/kimi" language: "en" updated: "2026-09-19" --- # Use Kimi Code for C# and .NET in Visual Studio 2026. Bring the Kimi Code AI coding agent into Visual Studio 2026 through its CLI. iolys lets you keep your C# or .NET solution open, follow the agent’s work, and use the same session experience as every other configured provider. - Provider: Kimi - Connection type: Provider CLI - Access: BYOS: use the access attached to Kimi Code - Who pays for the AI usage: Reuses an eligible AI subscription you already pay for through the provider's supported connection. - Where the model runs: The model runs in the provider's own cloud service. - Best for: Repository exploration, multi-step implementation, debugging, and code changes across established .NET projects. - Official site: https://www.kimi.com/en/ Download and manage the Kimi CLI locally from Manage Providers, then sign in with your existing account. Use the Kimi Code access included in your eligible plan inside Visual Studio 2026. ## How to connect Kimi in Visual Studio 2026 1. Open Manage Providers in iolys and add or select Kimi. 2. Download the locally managed CLI from the provider panel, then sign in with your Kimi account. 3. Choose your Kimi model and a supported effort level, then start from your Visual Studio solution. ## What you get - **Kimi for Visual Studio 2026** — Use the Kimi Code route while staying in the Microsoft IDE used by your .NET solution. - **Account-based access** — Reuse eligible Kimi Code access instead of duplicating provider setup. - **Provider-independent UI** — Keep one interaction model even when you compare Kimi with another agent. ## Requirements iolys targets the Visual Studio 2026 IDE on 64-bit Windows. It requires access to a supported AI provider or a local Ollama instance. Git is required for isolated parallel workspaces. Visual Studio Code is a separate editor; iolys is an extension for the Visual Studio IDE. ## Price All currently available iolys features are free for personal and commercial use. AI provider subscriptions, API usage, and infrastructure costs remain separate. iolys does not include a bundled model allowance. ## Kimi questions ### How can I use Kimi in Visual Studio for C#? Install the iolys extension for Visual Studio 2026 and open your C# solution. Open Manage Providers in iolys and add or select Kimi. Download the locally managed CLI from the provider panel, then sign in with your Kimi account. Choose your Kimi model and a supported effort level, then start from your Visual Studio solution. You can then ask Kimi to help with your C# and .NET code from the iolys workspace. ### Is there a VSIX extension to use Kimi in Visual Studio? Yes. iolys is a VSIX extension for Visual Studio 2026, and Kimi is one of the provider connections it ships with. Install the iolys VSIX once from the Visual Studio Marketplace, then add Kimi from the Manage Providers panel; there is no separate VSIX per provider. ### Can I use my Kimi Code subscription in iolys? Yes. Sign in through Kimi Code with an account whose plan includes CLI access. iolys uses that eligible access inside Visual Studio 2026, and usage counts toward your Kimi account’s allowance. ### Does Kimi Code work with Visual Studio 2026? Yes, with the iolys extension. It connects Kimi Code to Visual Studio 2026 through the provider CLI, using the eligible access on your Kimi account. ### Can I check Kimi usage without leaving Visual Studio? Yes. Open Show usage from the chat toolbar. Kimi Usage shows your plan, monthly usage percentage, remaining allowance, and the usage windows and reset times reported by your account. The capture shows a five-hour window and a monthly window; limits depend on your Kimi account. ### Can I choose Kimi’s reasoning effort level? Yes, for models that publish graded effort levels. Open the model options beside the prompt. K3 in the capture offers low, high, and max. iolys reads the supported levels from Kimi’s model catalog and hides the effort selector for models without those options. ### Can Kimi search the web and read documentation? Yes. Kimi’s native WebSearch and FetchURL tools are enabled in the integration. They let Kimi search for relevant information and read public pages alongside the IDE context and tools provided by iolys. ### Can Kimi use Visual Studio build and test tools? Yes. Kimi connects to the tools supplied by iolys, including reading and editing code, running builds, and running tests. Open Tools and Skills beside the prompt to inspect the available IDE tools. ### How is the Kimi CLI installed and updated? Open Manage Providers and select Kimi. iolys downloads and manages its own local CLI installation from this panel. Keep it up to date to use the effort controls supported by your model and CLI version. ### Can I keep other providers configured? Yes. Kimi can sit alongside cloud APIs, local Ollama models, and other provider CLIs. ## Related pages - [Bring Your Own AI Subscription to Visual Studio 2026 | iolys](https://getiolys.com/) - [Bring Your Own Model (BYOM) in Visual Studio 2026 | iolys](https://getiolys.com/byom) - [AI coding agent capabilities for Visual Studio | iolys](https://getiolys.com/capabilities) - [Visual Studio integrations for C# and .NET | iolys](https://getiolys.com/integrations) - [GitHub Copilot alternative for Visual Studio and C# | iolys](https://getiolys.com/copilot-alternative-visual-studio) - [AI providers and BYOS for Visual Studio 2026 | iolys](https://getiolys.com/providers) - [What is iolys? AI coding agent harness for Visual Studio | iolys](https://getiolys.com/what-is-iolys) - [The story behind iolys | From iolite to AI in Visual Studio](https://getiolys.com/our-story) - [Install iolys from the Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=iolys.iolys-visual-studio) - [iolys blog](https://getiolys.com/blog)