Kilo Code shipped two integrations in April: a native KiloClaw chat panel inside the VS Code extension, and the Kilo CLI built into every KiloClaw cloud instance. The VS Code panel (available since v7.2.20) lets developers interact with their always-on autonomous KiloClaw agent alongside their interactive Kilo Code session, using the same WebSocket stream as the web UI. Meanwhile, KiloClaw instances now include the full Kilo CLI, enabling the autonomous agent to spin up coding sessions, review PRs, and coordinate multi-repo changes independently. The /kiloclaw CLI command also gained org-aware support for team contexts. Key limitation: both features require Kilo Gateway authentication.
Table of contents
What this looks like in practiceSetting up KiloClaw in VS CodeUsing Kilo CLI inside KiloClawWhy bothRough edgesWhat’s next1 Comment
Sort: