Supporting OpenCode‑derived harnesses (e.g., KiloCode CLI) in the Multi‑Harness refactor #5546
moolawooda
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I’ve been following the
Multi‑Harness Agent OS Refactor in Progresswith great interest. The announcement mentions restructuring the codebase to support multiple agent harnesses, explicitly naming OpenCode, Codex, Pi, and others.I would like to ask whether the project also plans to support other harnesses that are built on top of OpenCode – i.e., downstream forks or derivatives that reuse OpenCode’s core but add their own modifications, custom agents, or platform‑specific features.
A concrete example is KiloCode CLI (https://github.com/Kilo-Org/kilocode), which maintains a close relationship with upstream OpenCode while introducing its own agentic workflows (Plan, Build, Debug, Orchestrator, etc.). Since KiloCode is fundamentally based on OpenCode, I imagine that the ongoing refactor – which already targets OpenCode – might make it relatively straightforward to support such derivatives by reusing a large portion of the harness integration.
I think many users would appreciate being able to run oh‑my‑openagent’s powerful orchestration (Sisyphus, Hephaestus, Prometheus, ultrawork mode, etc.) on top of these enhanced OpenCode variants. It could also broaden the project’s reach and encourage more experimentation in the agent space.
Looking forward to hearing the maintainers’ thoughts on this. Thanks for the great work!
All reactions