Clarification on the Relationship, Background, and Future Plans of Two CLI Projects

[shreychen]

Question

Hi Kilo-Org team! 👋

First off, thank you for building such powerful agentic engineering tools—Kilo Code has been incredibly helpful for streamlining development workflows.

While exploring your GitHub repositories, I noticed two projects that both appear to implement CLI functionality for Kilo Code:

1. kilocode/cli (under the kilocode repo, within the cli directory)
2. kilo-cli (a standalone kilo-cli repo)

Both projects seem active with recent commits , which has left me curious about their exact relationship and roadmap. I’d greatly appreciate it if you could clarify the following:

Questions:

1. Relationship: Are these two projects separate implementations, forks, or is one a successor/predecessor of the other? Do they serve different use cases or target different environments?
2. Background: What led to the creation of two distinct CLI projects? Were there specific technical or product decisions that motivated this structure?
3. Future Plans: Will both projects continue to be maintained, or is there a plan to consolidate them into a single CLI tool? If consolidation is planned, which repository will be the primary one moving forward?
4. Usage Guidance: For new users looking to adopt Kilo Code CLI, which project should we prioritize? Are there any functional differences we should be aware of when choosing between them?

Thank you for taking the time to address these questions—it will help the community make informed decisions about integrating Kilo Code into our workflows.

Looking forward to your response!

Best regards.

[stmichaelis]

Same question here, absolutely confused. Stumbled upon this after the CLI notified about a version upgrade with a huge jump from 0.26.1 to 1.0.13 (at the time). Seems like this is the successor?

After upgrading, kilo CLI stopped working with a black screen on Windows WSL2. As a fork of OpenCode, this could be the same problem they are fighting with over there. But I am wondering if this version even uses the same configuration as the original CLI?

[pschiel]

After upgrading, kilo CLI stopped working with a black screen on Windows WSL2

try this to eliminate possible problems:

• Deactivate timesyncd. Otherwise HyperV will do hard time resets, which leads to freezes and corrupt timestamps.

sudo systemctl stop systemd-timesyncd
sudo systemctl disable systemd-timesyncd

• Disable appendWindowsPath in /etc/wsl.conf

[interop]
appendWindowsPath = false

• Cleanup

npm cache clean --force
rm -rf $HOME/.bun/install/cache
rm -rf $HOME/.local/state/kilo
rm -rf $HOME/.local/share/kilo/bin
rm -rf $HOME/.cache/kilo
rm -rf $HOME/.config/kilo/node_modules

• Remove all plugins (plugins auto-update during start)

[stmichaelis]

Thanks for the quick reply. Works now. I did not check what exactly helped, as I intend to revert the changes some versions from now on to get back to a standard configuration and see if an update fixes this as well. Also applied the workaround disabling IPv6 in ~/.wslconfig as

[wsl2]
kernelCommandLine=ipv6.disable=1

as circulated in the OpenCode issues.
So seems this fork of OpenCode adapted to Kilo will replace the original independent CLI.