We would like to support Developer Lightspeed with DevSpaces as part of MTA-8.  Prior to committing to this the engineering team needs to explore what the work would entail to determine if this is feasible in the timeline.

rbanda@redhat.com contributed a guide of how he setup Kai 0.1.0 to run on DevSpaces:

• https://rrbanda.github.io/kai-demo/
  • https://github.com/rrbanda/kai-demo

Since rbanda@redhat.com's work, we have re-architected Kai to:

• Remove the use of the Python kai_rpc_server binary
• Rewrote the majority of the LLM/Agentic workflows in TypeScript
• Reworked the analysis in kai_analyzer_rpc so that it reuses the language server implementation from the IDE.

Next steps:

• Investigate if the latest Kai development builds are able to run in Dev Spaces
  • There is some concern that the communication of kai_analyzer_rpc with language servers inside of the IDE could be different in Dev Spaces than in local usage, this is more from a lack of our knowledge than from an identified blocker.  
• Plan what work is required to generate a downstream image of Developer Lightspeed for DevSpaces
  • As part of building the vsix we need to:
    • Assemble the typescript code and all deps into the vsix
    • Grab the downstream kai_analyzer_rpc binary and place in the vsix
  • Note:  We have not built the .vsix in downstream processes to date, we are unsure if there will be challenges in downstream systems for this.
    • It would help if we can identify other vsix extensions that are being built in downstream by Red Hat so we can learn from them as an example
• Test the downstream image is working properly in DevSpaces

Assuming that we can prove the above technical steps are working, then the remaining work to support this is related to:

• Release engineering
• QE automation of DevSpaces with Developer Lightspeed
• Docs to cover this use case

We are tracking this in upstream as:

https://github.com/konveyor/kai/issues/825