KiloCode Intellij fails to initialize after installation

[rpx99]

Plugin Type

JetBrains Plugin

App Version

4.99.1

Description

Tried the plugin first time, but failed.

[UDS] Failed to start server

java.lang.IllegalArgumentException at java.base/java.net.UnixDomainSocketAddress.of(UnixDomainSocketAddress.java:168) at ai.kilocode.jetbrains.core.ExtensionUnixDomainSocketServer.startUds(ExtensionUnixDomainSocketServer.kt:52) at ai.kilocode.jetbrains.core.ExtensionUnixDomainSocketServer.start(ExtensionUnixDomainSocketServer.kt:45) at ai.kilocode.jetbrains.core.ExtensionUnixDomainSocketServer.start(ExtensionUnixDomainSocketServer.kt:20) at ai.kilocode.jetbrains.plugin.WecoderPluginService$initialize$1.invokeSuspend(WecoderPlugin.kt:316) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100) at kotlinx.coroutines.internal.SoftLimitedDispatcher$Worker.run(SoftLimitedDispatcher.kt:130) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:613) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:1183) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:778) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:765)

java.lang.Throwable: Failed to start socket server for project: test at com.intellij.openapi.diagnostic.Logger.error(Logger.java:375) at ai.kilocode.jetbrains.plugin.WecoderPluginService$initialize$1.invokeSuspend(WecoderPlugin.kt:318) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100) at kotlinx.coroutines.internal.SoftLimitedDispatcher$Worker.run(SoftLimitedDispatcher.kt:130) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:613) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:1183) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:778) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:

Reproduction steps

Just install kilo code plugin and click on the plugin symbol.

Provider

No response

Model

No response

System Information

openjdk 21.0.8 2025-07-15 OpenJDK Runtime Environment (build 21.0.8+9-1) OpenJDK 64-Bit Server VM (build 21.0.8+9-1, mixed mode, sharing)

OpenBSD 7.8 GENERIC.MP#53 amd64

IntelliJ IDEA 2025.2.3 (Community Edition)
Build #IC-252.26830.84, built on October 2, 2025
Source revision: ba2aff1f71476
Runtime version: 21.0.8+9-1 amd64
VM: OpenJDK 64-Bit Server VM by N/A
Toolkit: sun.awt.X11.XToolkit
OpenBSD 7.8
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 3566M
Cores: 8
Registry:
ide.experimental.ui=true
idea.islands.feedback2.enabled=false
llm.show.ai.promotion.window.on.start=false
Non-Bundled Plugins:
com.arcticicestudio.nord.jetbrains (0.13.0)
com.jetbrains.gerryPurpleTheme (2025.1.0805)
ai.kilocode.jetbrains (4.99.1)
com.intellij.ml.llm (252.26830.84)
monokai-pro (2.1.1)
Lombook Plugin (252.26199.74)
Kotlin: 252.26830.84-IJ
Current Desktop: KDE

[rpx99]

👎

System Information
==================
CPU Architecture: amd64
Operating System: OpenBSD 7.8
IDE Version: IntelliJ IDEA 2025.2.3 (build IC-252.26830.84)
Plugin Version: 4.99.1
JCEF Support: No

WARNING: JCEF Not Supported
Your IDE runtime does not support JCEF. Please use a JCEF-enabled runtime.
See Known Issues for more information

[guang-gui]

me too

[pboos]

There are some instructions for JCEF problems here:
https://kilo.ai/docs/jetbrains-troubleshooting#intellij-idea

Do any of those solve your problems? Also check the ones under Android Studio that show how to switch your Java Runtime to one with JCEF in case your have a wrong one selected.

[github-actions]

Closing this one out since it's been inactive for a while — not because it's a bad issue, just that older items tend to lose context over time and we'd rather start fresh if this is still a problem.

Please feel free to reopen (or open a new issue) if you're still running into this. We're happy to take another look! 🙏