Run a second, isolated Kilo Code without touching your main setup

Separate VS Code installs don’t isolate providers, not even Insiders with its own --user-data-dir . Override only the config directory and your second instance still shares your main auth.json , so real isolation has to move both. Run the Kilo extension in stable VS Code and in VS Code Insiders, even with separate --user-data-dir and --extensions-dir , and they still share provider config and API keys. Note the last entry: managed config outranks project config. What project config can’t doCredentials you set up through /connect still go to the global auth.json .