packages/kilo-docs/pages/getting-started/faq/known-issues.md
This section contains known issues and limitations of Kilo Code.
In some cases, this behavior can be caused by a conflict with other VS Code extensions that interact with files or workspace scanning.
A reported example was the Todo Tree extension, which interfered with workflow execution. Disabling the extension resolved the issue immediately.
If you encounter similar behavior:
We are working on documenting known extension conflicts to improve troubleshooting guidance.
You may see an error like this:
Command failed with exit code 1: powershell (Get-CimInstance -ClassName Win32_OperatingSystem).caption
'powershell' is not recognized as an internal or external command,
operable program or batch file.
This error occurs when Windows cannot find the PowerShell executable. Most commonly, this happens because the PATH environment variable does not include the directory where PowerShell is installed.
Add PowerShell to your PATH:
Windows + X (or right-click the Start button) and select System%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\
Yes. A restart is required for Windows to apply the updated PATH variable.
This error can also appear if a Windows-specific PowerShell command is executed in:
In these cases, PowerShell may not be available, and the command must be replaced with an OS-appropriate alternative.
Verify that PowerShell is installed and accessible by running:
JCEF is not supported in this environment or failed to initializeInternal JCEF not supported, trying external JCEFKilo Code depends on JCEF (JetBrains Chromium Embedded Framework) to display its interface. If the bundled Java runtime doesn't include JCEF, or JCEF is disabled, the panel cannot render.
ide.browser.jcef.enabled=true
Failed to fetch extension base URLPKIX path building failedunable to find valid certification path to requested targetThe IDE cannot validate the TLS certificate used by the Kilo Code endpoint or a network proxy. Common causes include untrusted root certificates, corporate proxies intercepting HTTPS traffic, or missing intermediate certificates.
JetBrains IDEs rely on the system certificate store, so resolving trust at the OS level usually fixes the issue.
{% callout type="note" %}
JetBrains 2024.3 note: Some builds may fail to recognize OS certificates. Workarounds include downgrading to a previous version, upgrading to 2024.3.1 or later, or adding the JVM option -Djavax.net.ssl.trustStoreType=Windows-ROOT.
{% /callout %}
Kilo Code cannot access paths without an active workspaceKilo Code requires an explicit workspace configuration to access project files in JetBrains IDEs. This is especially common in Android Studio, which may not automatically set up the workspace that Kilo Code expects.