[Feature]: Kilo Code Support

[archodev]

Prerequisites

• I will write this issue in English (see our Language Policy)
• I have searched existing issues and discussions to avoid duplicates
• This feature request is specific to oh-my-opencode (not OpenCode core)
• I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer

Problem Description

Interestingly enough, the Kilo Code CLI appears to support OpenCode plugins as it is a fork of OpenCode. I think it would be great if we could use Oh My OpenCode in the Kilo Code CLI because they offer free models like GLM-5 that are not available in OpenCode.

Proposed Solution

I propose that a flag is added to the installer that allows you to install the plugin for Kilo Code CLI. This would add the plugin to the configuration in ~/.config/kilo/config.json and make it so when the plugin is run from Kilo Code, it properly reads from ~/.config/kilo/oh-my-opencode.json. I think the easiest way to detect if we are running in Kilo Code would be to see if the kilo/ model provider is available.

Alternatives Considered

I tried copying my ~/.config/opencode folder into ~/.config/kilocode and it didn't work, it turns out that contrary to what their documentation claims the correct config file location is ~/.config/kilo/config.json. Copying here does work, however it tries to load the oh-my-opencode config from ~/.config/opencode/oh-my-opencode.json which contains opencode models not available in kilo code.

Doctor Output (Optional)

Additional Context

No response

Feature Type

Configuration Option

Contribution

• I'm willing to submit a PR for this feature
• I can help with testing
• I can help with documentation

[code-yeongyu]

[sisyphus-bot] Thank you for using English in this issue. This project requires all GitHub communications (issues, PRs, and comments) to be in English only. Please see our language policy in AGENTS.md. If you need to communicate in another language, please use translation tools first.

[code-yeongyu]

Hi @archodev,

Thanks for the detailed feature request and for doing the research on Kilo Code's config paths.

Since Kilo Code maintains OpenCode plugin compatibility, this is a reasonable extension. Your proposed approach sounds good:

1. Installer flag (e.g.,

--target=kilocode

) to write to

~/.config/kilo/

instead of

~/.config/opencode/

2. Runtime detection of Kilo Code via

kilo/

model provider prefix
3. Config path resolution that checks the runtime environment

You're welcome to submit a PR for this. Key files to modify:

src/cli/installer.ts

• Add target selection

src/plugin-handlers/config-handler.ts

• Add Kilo Code config path detection

src/shared/paths.ts

(or create) - Abstract config directory resolution

Please reference this issue in your PR. Looking forward to your contribution!

[wommy]

kilo code is behind opencode by many commits, ive been using it for a few days now

i think it makes alot more sense to just bring your kilo api key into opencode, tho im still using both

[notlousybook]

kilo code is behind opencode by many commits, ive been using it for a few days now

i think it makes alot more sense to just bring your kilo api key into opencode, tho im still using both

@wommy you can't bring it into opencode

[code-yeongyu]

[sisyphus-bot] ## Feature Assessment: Kilo Code Support

Status: ✅ REASONABLE EXTENSION - Awaiting Implementation

Already Exists? NO

Kilo Code support does not currently exist in the codebase. Configuration path resolution only handles:

• (CLI binary)
• / (Desktop app)
• environment variable override

Feasibility: MODERATE

The existing config path infrastructure in provides a solid foundation. Implementation would require:

1. Binary Detection Extension - Recognize Kilo Code runtime (detect model provider prefix)
2. Config Path Addition - Add as an alternative config directory
3. Installer Flag - Add option to
4. Config Handler Update - Modify for runtime path resolution

Key Files to Modify:

File	Purpose
	Config directory resolution logic
	Installation orchestration
	Plugin registration
	Runtime config loading

User Research Verified:

• ✅ Correct config path: (not )
• ✅ Kilo Code is OpenCode plugin-compatible
• ✅ Copying config works but reads wrong model providers

Recommended Approach:
The maintainer's suggested approach is sound:

1. Installer flag () for initial setup
2. Runtime detection via provider prefix
3. Dynamic config path resolution based on detected environment

@archodev has indicated willingness to submit a PR. This feature aligns with the project's multi-model orchestration philosophy.

[code-yeongyu]

[sisyphus-bot]

Read-only triage on dev.

Current state

• Kilo Code is not in the install surface, provider-availability mapping, or model-capabilities cache.
• Adding Kilo Code support would require:
  1. Provider detection and auth flow.
  2. Model-capabilities entries for Kilo Code models.
  3. Fallback chain updates.

Action

• Labels: enhancement, triage:feature-request (already set). No label change.
• Keep open. No assignee. Please link the Kilo Code API docs and preferred model IDs so we can evaluate the integration scope.

[zeljkoavramovic]

+1 for this request, since Kilo has a nice VS Code plugin as well. Kilo is not usable for me without implementing requested feature.