packages/kilo-docs/pages/code-with-ai/platforms/vscode/index.md
Kilo Code is available as two VS Code extensions: the VSCode (Legacy) extension and the current VSCode version built on Kilo's shared agent runtime.
{% tabs %} {% tab label="VSCode" %}
Ctrl+Shift+X / Cmd+Shift+X)The extension includes its own embedded runtime. No separate Kilo CLI installation is required.
Key features include:
kilo.jsonc instead of VS Code settings.kilo/agents/*.md) replacing the modes system.md filestask toolSettings apply across extension surfaces, including the sidebar and Agent Manager. The standalone CLI uses the same ~/.config/kilo/kilo.jsonc (global) and ./kilo.jsonc (project) files when used directly.
Kilo Code for VS Code starts its embedded runtime from the extension and applies the relevant VS Code network settings to that runtime. On managed networks, configure proxy and certificate trust in VS Code settings rather than in a separate CLI install.
Use these settings when your organization requires a proxy or inspects HTTPS traffic:
http.proxy to your organization proxy URL.http.noProxy for hosts that should bypass the proxy.http.proxySupport enabled unless you intentionally want VS Code and Kilo Code to ignore proxy settings.kilo-code.new.extraCaCerts to the absolute path of a PEM file that contains the additional certificate authority certificates.http.proxyStrictSSL enabled whenever possible. Disable it only as a temporary troubleshooting step or when your administrator explicitly requires it, because it disables TLS certificate verification for this path.Example user or workspace settings:
{
"http.proxy": "http://proxy.example.com:8080",
"http.noProxy": ["localhost", "127.0.0.1", ".example.internal"],
"kilo-code.new.extraCaCerts": "/absolute/path/to/corporate-ca.pem"
}
{% /tab %} {% tab label="VSCode (Legacy)" %}
{% partial file="install-vscode.md" /%}
.kilocodemodes YAML files@{% /tab %} {% /tabs %}