Kilo cli support

[benzntech]

What feature would you like to see?

Kilo code cli is now fork of opencode https://github.com/Kilo-Org/kilo

Additional information

No response

[github-actions]

HAPI currently supports OpenCode only. The CLI exposes hapi opencode and the implementation spawns the opencode binary; I didn’t find any Kilo-specific integration in this repo.

Relevant code:

• cli/src/commands/opencode.ts:8 - registers the hapi opencode command.
• cli/src/opencode/opencodeLocal.ts:20 - spawns the opencode binary.
• cli/README.md:31 - documents OpenCode mode.
• cli/README.md:105 - requires opencode on PATH.

Need more info:

• Is Kilo a drop-in replacement for OpenCode (same opencode command + flags like --session)?
• What binary name/path should HAPI launch for Kilo?
• Any config or hook differences versus OpenCode we should account for?

---

HAPI Bot

[benzntech]

Based on the current state of the OpenCode and Kilo ecosystems, here is the technical breakdown you need for the HAPI integration.

Core Relationship: Kilo vs. OpenCode

Kilo (formerly Kilocode) is a fork of OpenCode. While it aims for deep integration with the Kilo platform, it maintains a "superset" philosophy, meaning it preserves most of OpenCode's underlying CLI architecture but introduces its own identity and expanded feature set.

---

1. Is Kilo a drop-in replacement?

Mostly, but not entirely.

• Command Parity: Kilo supports many of the same high-level behaviors as OpenCode, including the TUI-based interaction.

• Flags: It supports the --session flag for resuming conversations, similar to OpenCode.

• Compatibility: Kilo explicitly states in its documentation that it is built on OpenCode and supports the same core configuration options to ease the transition for developers.

2. Binary and Execution Path

To support Kilo in HAPI, you will need to account for a different binary name and default location.

• Binary Name: kilo

• Package Name: @kilocode/cli (installed via npm install -g @kilocode/cli)

• Implementation Change: You should update cli/src/opencode/opencodeLocal.ts to allow a configurable binary path or check for both opencode and kilo.

3. Config and Hook Differences

This is where the two diverge significantly for integration purposes:

Feature | OpenCode Integration | Kilo Integration -- | -- | -- Config File | ~/.config/opencode/opencode.json | ~/.config/kilocode/kilocode.json Local Config | ./opencode.json | ./kilocode.json Plugin System | TypeScript-based event subscribers | Custom Lifecycle Hooks (recent feature) Session Events | session.created, session.status | session_start, session_idle, session_end

Key Hook Difference:

Kilo has recently introduced a more "git-hook" style configuration for sessions. Unlike OpenCode’s internal TypeScript plugins, Kilo allows you to define shell commands as hooks directly in the JSON config:

JSON

{
  "hooks": {
    "session_start": "your-command-here",
    "session_idle": "your-command-here"
  }
}

---

Recommended Next Steps for the Repo

1. Abstract the Runner: Modify opencodeLocal.ts to use a generic AgentRunner that accepts a binaryName (defaulting to opencode but allowing kilo).

2. Config Discovery: Update the config loader to check for kilocode.json if opencode.json is missing.

3. Environment Variables: Note that Kilo uses the prefix KILO_ (e.g., KILO_API_KEY) vs OpenCode's provider-specific prefixes.

Would you like me to draft a proposal for the TypeScript interface changes needed in cli/src/opencode/opencodeLocal.ts to handle these dual binaries?