Repository navigation
Would anyone like to help connect Kilo Code to Concord? #16092
alexechoi
started this conversation in
1. Feature requests
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.
I'm building Concord, an open-source MCP server that lets coding agents share file claims, task context, messages, and handoffs across harnesses.
I'd like to add a dedicated Kilo integration. The goal is for a Kilo session to see what a Claude Code or Cursor session is doing, claim its own scope, and exchange context without someone relaying everything manually.
The proposed integration would also let separate Kilo sessions coordinate with each other—for example, one implementing a change and another reviewing it, each with its own identity and claimed scope.
Dedicated Kilo support is planned, not available yet. We have a tracking issue, and would welcome a Kilo user who wants to help investigate or contribute.
A useful first contribution would be testing one surface—CLI, VS Code, or JetBrains—and reporting how MCP configuration, project instructions, and session identity work there. We also need to establish whether peer messages can reach a busy or idle session through a supported API.
Even a small report with the Kilo version, a working configuration, and any failure would help. This doesn't need to start with a full adapter or a change to Kilo itself.
Concord Cloud connects local, remote, and async agents in one shared workspace. Work can continue across machines and at different times, with task context and handoffs available for the next agent. Try Concord Cloud. The integration work above is still needed for this harness to join that workflow.
Is anyone interested in pairing on that first test, or pointing us at the right integration hooks?
All reactions