Feature request: Kilo Code agent integration

Open
#1,554 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
ai, cli, devtools

Research direction

Start by reading opencode.go and pi.go to understand the existing agent integrations, then inspect how hooks and transcripts are handled. Add the KiloAgent presence detection for .kilo/ or .kilocodemodes, hook handling for .kilo/hooks.json or the bus bridge, and transcript processing for Kilo JSONL history and modified artifacts. Done means the integration is versioned and captures Kilo sessions consistently with the existing integrations.

Written by the indexing model from the issue text.

Description

enhancement
Problem or use case
Summary

Proposing native Kilo Code coding agent integration (.kilo/agents/), similar to the existing Claude Code, Cursor, and OpenCode integrations.

Why Kilo Code?
  • Kilo Code is a rapidly growing open-source agentic IDE framework with access to 500+ models.
  • It uses a structured local agent architecture (.kilo/agents/*.md) and workspace rules (.kilo/rules/).
  • Power users running complex multi-step workflows in Kilo Code produce rich FSM state transitions and JSONL audit trails that need Git-native versioning.
Proposed Implementation

Similar to opencode.go and pi.go:

  1. kilocode.go — KiloAgent struct implementing presence detection (.kilo/ or .kilocodemodes).
  2. hooks.go — Hook handler to generate/clean .kilo/hooks.json or bus bridge.
  3. transcript.go — Linearize Kilo JSONL task history and extract modified artifact metadata.
My Background

I independently designed and shipped an open-source Executive Orchestrator mode and JSONL memory ledger specifically for Kilo Code (https://github.com/temary1122-a11y/kilocode-executive-orchestrator). I understand Kilo's internal state machine and event formatting deeply.

I would love to submit a PR implementing the Kilo Code agent bridge for Entire CLI!

Desired behavior
Proposed solution

No response

Alternatives or workarounds

No response

Dominant language
Go
Stars
5.1k
Forks
475
Avg merge
1d 11h
Merged PRs (30d)
178

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from entireio/cli

All issues in entireio/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.