Last verified: July 19, 2026
The most clearly documented way to use MiniMax AI in VS Code is the third-party Kilo Code extension with the MiniMax-M3 model and a MiniMax Token Plan Subscription Key. MiniMax publishes the provider settings, but MiniMax does not own Kilo Code. The official MiniMax coding product is MiniMax Code, which is a separate desktop, web, and coding-agent experience—not a Visual Studio Code extension.
This distinction matters for support and privacy. MiniMax supplies the model, API-compatible service, account, and credential. Kilo Code supplies the VS Code agent interface, file access, terminal actions, modes, and extension update channel. Microsoft supplies VS Code and the Marketplace. A MiniMax documentation page describing an integration does not turn the external tool into an official MiniMax product.
A MiniMax AI VS Code workflow therefore combines services from separate parties. Evaluate the MiniMax account terms, the extension’s permissions and data handling, and the editor’s workspace trust settings as distinct layers.
Independent-site notice: MiniMax-AI.chat is not owned by, operated by, or affiliated with MiniMax, Microsoft, or Kilo Code. This guide was checked against MiniMax, Kilo Code, GitHub, and Visual Studio Marketplace documentation. Extension interfaces and account entitlements can change, so confirm the labels displayed in the software before entering a credential.
MiniMax AI in VS Code at a glance
| Question | Verified answer |
|---|---|
| Does MiniMax publish an official VS Code extension? | No MiniMax-owned VS Code extension was identified in the official product directory or setup documentation. |
| Which VS Code extension has MiniMax-documented steps? | Kilo Code. |
| Who owns Kilo Code? | Kilo Code is an external open-source project; it is not a MiniMax product. |
| Which model does MiniMax’s Kilo setup specify? | MiniMax-M3. |
| Which credential does that setup specify? | A Token Plan Subscription Key with plan or Credits access. |
| What is the Global entrypoint? | api.minimax.io in Kilo’s MiniMax provider field. |
| Can a pay-as-you-go API Key replace the Subscription Key? | Do not assume so. MiniMax says the two key types are not interchangeable; follow the credential requested by the integration. |
| Can the extension edit files or run commands? | Kilo advertises multi-file editing and terminal actions. Permission and review settings therefore matter. |
Official MiniMax components vs external tools
| Component | Owner or maintainer | Status in this workflow |
|---|---|---|
| MiniMax M3 | MiniMax | Official MiniMax model used for coding and agent tasks |
| MiniMax Open Platform and Token Plan | MiniMax | Official account, service, quota, and credential route |
| MiniMax Code | MiniMax | Official MiniMax coding product; an alternative to working inside VS Code |
| Kilo Code | Kilo Code project | Third-party VS Code extension with MiniMax-documented provider steps |
| Visual Studio Code and Marketplace | Microsoft | Editor and extension-distribution channel |
| Continue, Cline, Roo Code, and similar extensions | Their respective maintainers | External tools; compatibility depends on their custom-provider implementation and version |
| Cursor, TRAE, Claude Code, OpenCode, Codex, and other coding tools | Their respective maintainers | External editors or agents documented separately by MiniMax; not all are VS Code extensions |
For broader coding use cases and tool options, use the MiniMax AI programming guide. This page stays focused on Visual Studio Code, Kilo Code, credential handling, and repository safety.
Before installing: choose the account and credential
MiniMax issues two credential types that can look similar in an integration form:
| Credential | Billing resource | Use in this guide |
|---|---|---|
| Pay-as-you-go API Key | Open Platform balance charged per API use | Use only when the tool and MiniMax documentation explicitly support the pay-as-you-go route. |
| Token Plan Subscription Key | Assigned Token Plan quota and/or purchased Credits | The credential specified in MiniMax’s Kilo Code instructions. |
The Subscription Key is often shown with an sk-cp-… prefix. A key can appear in the console before the user has an assigned plan seat or Credits, so visibility alone does not prove that it can make requests. Open Billing → Token Plan, confirm the resource assigned to your Team user, and copy the Subscription Key from the matching account.
For the exact difference between credentials, Global and Mainland China domains, and authentication formats, read the MiniMax API key and base URL guide. Token Plan is designed for individual, interactive development and has quota windows and traffic limits. MiniMax recommends pay-as-you-go for production services; an IDE workflow is not the same as a production backend.
How to set up MiniMax M3 in VS Code with Kilo Code
Step 1: verify and install the extension
- Open the VS Code Extensions panel with
Ctrl+Shift+Xon Windows/Linux orCmd+Shift+Xon macOS. - Search for Kilo Code.
- Open the Marketplace listing and verify the extension identifier
kilocode.Kilo-Codeand links to the Kilo Code project before installing. This reduces the risk of choosing a similarly named extension. - Install the extension, then review its requested capabilities and release information.
- Open a non-sensitive test repository under version control for the first configuration.
The canonical listing is the Kilo Code extension on Visual Studio Marketplace, and its source is published in the Kilo Code GitHub repository. Use one of those routes instead of a third-party download site or an unsolicited VSIX file.
Step 2: remove conflicting environment overrides
MiniMax’s Kilo Code instructions say to clear ANTHROPIC_AUTH_TOKEN and ANTHROPIC_BASE_URL before configuring the provider because those environment variables can override the in-extension settings. First inspect them in the terminal:
# macOS / Linux / WSL
printenv ANTHROPIC_AUTH_TOKEN
printenv ANTHROPIC_BASE_URL
# PowerShell
$env:ANTHROPIC_AUTH_TOKEN
$env:ANTHROPIC_BASE_URLIf either variable belongs to another tool or provider, do not destroy it blindly. Close the affected tool, remove the override only from the VS Code session used for this setup, or launch VS Code from a clean shell. Document the original value securely if you need to restore it later. Never paste the value into an article, issue, screenshot, or support chat.
# Clear only in this macOS / Linux / WSL shell session
unset ANTHROPIC_AUTH_TOKEN
unset ANTHROPIC_BASE_URL
# Clear only in this PowerShell process
Remove-Item Env:ANTHROPIC_AUTH_TOKEN -ErrorAction SilentlyContinue
Remove-Item Env:ANTHROPIC_BASE_URL -ErrorAction SilentlyContinueStep 3: enter the MiniMax provider settings
- Open the Kilo Code panel.
- Open Kilo Code Settings.
- Set API Provider to
MiniMax. - For a Global MiniMax account, set MiniMax Entrypoint to
api.minimax.io. Do not addhttps://,/v1, or/anthropicwhen the field matches MiniMax’s documented Kilo form. - Paste the Token Plan Subscription Key into MiniMax API Key.
- Select
MiniMax-M3. - Click Save, then Done.
Regional warning: the steps above are MiniMax’s Global instructions. A Mainland China key belongs to the
minimaxi.comservice route. Do not send a Global key to a China host or the reverse. Follow the regional MiniMax documentation exposed by the account rather than guessing how a particular extension maps its entrypoint field.
Step 4: run a low-risk verification task
Do not begin by asking an agent to rewrite a production repository. Open a small test project and use a read-only request:
Read the repository without changing files. Identify the language, package manager, test command, build command, and three files most relevant to authentication. Cite each conclusion with a file path. Do not run commands until I approve them.
Confirm that the response comes from MiniMax-M3, that no 401 or quota error appears, and that the proposed file paths exist. Then allow one harmless command, such as the repository’s version or test-discovery command. Review every permission prompt rather than approving a batch automatically.
Why the base URL looks different in Kilo Code
MiniMax’s general API documentation exposes full protocol bases:
| Integration | Global value | Who appends the route |
|---|---|---|
| OpenAI-compatible SDK | https://api.minimax.io/v1 | The SDK appends operations such as /chat/completions. |
| Anthropic-compatible SDK | https://api.minimax.io/anthropic | The SDK appends /v1/messages. |
| Kilo Code built-in MiniMax provider | api.minimax.io | The extension constructs the protocol route from its provider implementation. |
Do not reuse one value in every field. A form labeled Entrypoint may expect a host, while a form labeled OpenAI Base URL expects the full /v1 base. Copy the value for the exact tool and provider mode, or the request may contain a duplicated path such as /v1/v1.
Other VS Code tools that may connect to MiniMax
MiniMax states that tools accepting a custom OpenAI-compatible or Anthropic-compatible endpoint can use its M-series models. Its generic coding-tool reference explicitly groups Continue and OpenAI-format IDE plugins under the OpenAI-compatible route. That is a protocol capability, not a guarantee that every version of every extension supports every MiniMax feature.
| Tool | VS Code relationship | MiniMax status | Recommended action |
|---|---|---|---|
| Kilo Code | VS Code extension | Dedicated MiniMax setup documented by MiniMax | Use the built-in MiniMax provider and the exact host-only entrypoint above. |
| Continue | VS Code/JetBrains extension | Named in MiniMax’s generic OpenAI-format guidance | Use a custom OpenAI-compatible provider only after checking Continue’s matching schema. |
| Cline | VS Code extension | External tool; dedicated M3 steps were not present on the MiniMax page used for this verification | Confirm that the installed version accepts a custom OpenAI or Anthropic base and does not rewrite the model ID. |
| Roo Code | VS Code extension | External tool; no dedicated M3 walkthrough was relied on here | Treat configuration as third-party and verify the provider’s request format before adding a key. |
| Cursor | Separate VS Code-derived editor | MiniMax publishes dedicated instructions | Use the separate Cursor guide; it is not an extension inside standard VS Code. |
| Claude Code, OpenCode, Codex, and similar agents | Usually CLI/TUI tools that can run in VS Code’s terminal | Several have MiniMax documentation | Do not describe terminal integration as a native VS Code extension. |
When using a generic OpenAI-compatible extension with a Global account, the starting values are normally https://api.minimax.io/v1, your eligible MiniMax credential, and model ID MiniMax-M3. When using an Anthropic-compatible extension, the starting base is https://api.minimax.io/anthropic. The extension must support the protocol fields and tool-call behavior your workflow needs.
Token Plan, Credits, and rate limits in VS Code
Kilo Code does not create a separate MiniMax quota. Requests consume the resources attached to the Subscription Key. MiniMax’s Token Plan uses subscription windows, Credits, and plan-specific traffic rules; the extension can also generate many requests during repository exploration, tool loops, retries, or parallel agents.
- One chat can produce multiple calls: tool use, follow-up reasoning, and verification may each consume a request.
- Large context costs more capacity: avoid attaching an entire monorepo when a small set of files answers the question.
- Parallel agents multiply traffic: begin with one task and low concurrency.
- A 429 is not an invitation to retry immediately: pause, use exponential backoff with jitter, and reduce parallel work.
- Plan quota and API traffic limits are different: remaining subscription allowance does not guarantee unlimited RPM, TPM, or concurrency.
Use the MiniMax API rate-limit guide for dated RPM, TPM, and concurrency tables and the MiniMax pricing guide for the billing map. Do not put changing plan prices in a permanent VS Code setup checklist.
Store the MiniMax key safely
MiniMax says API credentials must not be exposed in browser or client-side code. An IDE credential is still a sensitive bearer secret. Anyone who obtains it may consume the attached resources until it is disabled or replaced.
- Enter the key only in the extension’s provider credential field or an explicitly documented secret mechanism.
- Never save it in
.vscode/settings.json, a workspace file, source code, a committed.env, shell history, task definition, or debug launch configuration. - Do not enable Settings Sync for a plaintext setting containing a key.
- Use separate credentials or Team users for separate trust boundaries where the MiniMax console and your operating model allow it.
- Keep pay-as-you-go and Subscription Keys labeled so one is not pasted into the wrong billing route.
- Do not paste the key into the AI chat itself. The model does not need to read the credential used by the extension transport.
- If a key appears in Git, a screenshot, a log, or a shared workspace, replace it immediately and disable the exposed key through the console when that control is available.
Kilo’s repository includes a privacy statement saying entered API keys are stored locally for Kilo CLI, but that file is specifically titled Kilo CLI Privacy Policy. It should not be treated as a complete technical specification of every VS Code extension release. Review the extension’s displayed privacy information and source before using a high-value credential.
Repository, terminal, and MCP safety
A coding extension can expose much more than a prompt. Depending on permissions, it may read repository files, edit multiple paths, run terminal commands, open a browser, or connect to MCP servers. The selected model provider may receive prompts and relevant code context. “Runs inside VS Code” does not mean “stays on the computer.”
Use a controlled development workflow
- Start clean: commit or stash your own work before allowing edits.
- Open the narrowest folder: do not expose a parent directory containing unrelated repositories, credentials, or personal files.
- Keep VS Code Workspace Trust enabled: treat an unknown repository as untrusted until you inspect tasks, extensions, hooks, and scripts.
- Plan before editing: ask the agent to list intended files, commands, and tests.
- Approve commands individually: inspect package scripts and shell commands before execution.
- Review the diff: look for secret exposure, dependency changes, permission expansion, disabled validation, and edits outside scope.
- Run project checks yourself: execute tests, lint, type checks, builds, and security scans from a known environment.
- Keep production separate: do not expose production credentials or give the extension direct deployment authority for routine coding.
Treat MCP servers as separate trust boundaries
MCP can add search, issue trackers, databases, files, browsers, and other tools. Each server has its own code, credentials, data access, network behavior, and update path. Installing an MCP server from an extension market does not make it a MiniMax service. Review its source, pin or record the version, scope its credentials, and remove unused servers.
For a pre-use checklist, see what not to paste into MiniMax AI and the broader MiniMax security guidance.
Troubleshooting MiniMax in Kilo Code
| Symptom | Likely checks | Action |
|---|---|---|
| 401 or invalid key | Global/China mismatch, wrong credential type, inactive Subscription Key, stale environment override | Match the key to its platform, confirm plan/Credits assignment, and clear conflicting Anthropic variables. |
| 404 or route error | Full URL pasted into a host-only entrypoint, duplicated /v1, protocol mismatch | For Kilo’s built-in MiniMax provider, restore the documented api.minimax.io entrypoint. |
| Model not found | Model ID altered, account entitlement, unsupported provider mode | Use exact case MiniMax-M3 and confirm the model through the matching MiniMax account. |
| 429 or task repeatedly pauses | RPM/TPM/concurrency ceiling, Token Plan window, parallel agents, aggressive retry | Stop repeated calls, reduce concurrency and context, then retry with delay. |
| Settings appear correct but another provider responds | Environment variables overriding the extension, wrong profile, stale VS Code process | Inspect the process environment, reopen VS Code from a clean shell, and reselect the MiniMax provider. |
| Unexpected file or terminal action | Broad agent mode or permission approval | Deny the action, inspect the plan and diff, narrow the workspace, and revert through version control if necessary. |
| Unexpected usage | Leaked key, hidden retry loop, parallel tasks, another tool sharing the key | Stop the extension, inspect usage, replace the credential if exposure is possible, and separate integrations. |
Use the MiniMax API error-code guide for response codes. Preserve the response body after redacting credentials, because an HTTP status alone may not identify the MiniMax business error.
When to use MiniMax Code instead
Choose MiniMax Code when you want the official MiniMax coding harness and do not specifically need a VS Code extension. MiniMax describes Code as supporting coding workflows, Agent Teams, Skills, memories, schedules, and chat. Token Plan access can work directly in MiniMax Code without manually placing a key into an external extension.
Choose Kilo Code when staying inside VS Code and using its external agent modes is more important, and your security review permits a third-party extension. Choose a generic compatible extension only when you have verified its provider format, credential storage, tool permissions, privacy terms, and model behavior.
Frequently asked questions
Does MiniMax have an official VS Code extension?
No MiniMax-owned VS Code extension was identified in the official product directory or setup documentation used for this guide. MiniMax documents how to configure MiniMax M3 in Kilo Code, which is an external open-source extension.
Is Kilo Code made by MiniMax?
No. Kilo Code is maintained by the Kilo Code project. MiniMax supplies the model service and publishes integration settings, but documentation of an external tool is not ownership or affiliation.
Which MiniMax model should I select in Kilo Code?
MiniMax’s verified Kilo Code instructions specify MiniMax-M3. Use the exact model ID and confirm availability in the MiniMax account linked to the credential.
Which MiniMax key does Kilo Code use?
The MiniMax instructions specify a Token Plan Subscription Key. This key uses assigned plan quota and/or Credits and is not interchangeable with a pay-as-you-go API Key.
What is the MiniMax entrypoint in Kilo Code?
For the Global setup, MiniMax documents api.minimax.io in Kilo’s MiniMax Entrypoint field. That is a host-only value. Do not paste the OpenAI /v1 base into that specific field.
Can I use a Mainland China key with the Global entrypoint?
No. MiniMax keys must match their service region. Use the console, key, and host associated with the same Global or Mainland China service, and follow the region-specific integration instructions.
Can Kilo Code read my repository?
Kilo Code advertises codebase operations, multi-file editing, terminal commands, and other agent capabilities. Open only the required workspace, inspect permissions, review proposed actions, and assume relevant code context can be sent to the selected model provider.
Should I put the MiniMax key in .vscode/settings.json?
No. A workspace settings file can be committed, copied, or shared. Enter the credential only in an explicitly documented provider-secret field or secret mechanism, and verify that it is not included in Settings Sync or repository files.
Why does Kilo Code return 429 when quota remains?
Remaining Token Plan allowance and traffic limits are separate. Repository exploration, parallel agents, tool loops, or retries can exceed RPM, TPM, or concurrency even when subscription quota remains. Reduce parallel work and context, then retry with backoff.
Can I use Continue, Cline, or Roo Code with MiniMax?
A version that accepts a custom OpenAI-compatible or Anthropic-compatible provider may be able to connect, but this guide does not label every extension as officially supported. Verify the installed version’s schema, base URL handling, tool-call support, credential storage, and permissions before entering a key.
Official and primary sources
- MiniMax Other Tools guide — Kilo Code configuration and generic compatible-protocol reference.
- MiniMax Token Plan Quick Start — Subscription Key rules, M3 test, and coding-tool directory.
- MiniMax API prerequisites — pay-as-you-go API Key versus Subscription Key.
- MiniMax Token Plan FAQ — eligibility, plan usage, and suitability.
- Kilo Code source repository — project ownership, features, installation, and release source.
- Kilo Code Visual Studio Marketplace listing — canonical extension listing and identifier.
- Kilo repository privacy statement — locally stored credentials claim scoped by its Kilo CLI title.
- Kilo repository security model — permissions, sandbox warning, and external-provider trust boundary for its CLI.
Next step: obtain the correct Subscription Key, install the verified Kilo Code extension, configure the host-only Global entrypoint, and run a read-only task in a disposable repository. Add write and terminal permissions only after the model, region, quota, and review workflow are confirmed.