WG - Chappie

[phillip-kruger]

The main objective of this working group is to allow AI features in Quarkus Dev Mode (Dev UI and CLI)

The Problem

The way developers are writing code is changing with the rise of AI tools like chatGPT etc. Developers ask an AI agent to help with tasks.

The proposed Solution

Provide a way to allow AI integration into Quarkus Dev Mode (Dev UI and CLI) . The should allow extensions to contribute to the AI hooks.

Quarkus core should allow hooks (BuildItems) that extensions can use to define AI functions.

The chappie extensions will use this and set it up in Dev UI. The Chappie extension will also be responsible for a indexed vector DB that contains the Quarkus documentation. Extensions should be able to use this with groupId and artifactId.

The Chappie extension will manage the backend configuration and connection (to the LLM), and the elements in Dev UI.

Extensions will provide relevant AI functions.

Adding a chatbot can also be added.

Proposed Architecture

Because we want to be able to use langchain4j without clashing with a user's use of langchain4j, the chappie server will be created as a Quarkus app (that can use the langchain4J extension) and expose functions as REST (and/or some other protocol). The chappie extension will start this server as a dev-service, running the chappie langchain4j functions isolated from the user's app.

To decouple the AI assistant from Chappie but still be able to allow Quarkus extensions to take part in the Assistant functions, some interfaces will be added to Quarkus core. They will be used by the extensions to take part, and implemented by the chappie extension (or another extension).

Definition of Done

Once the core is in place and the Chappie extension is working, and all extensions features implemented and the Vector DB is available. Documentation on how to add an AI functions for future ideas. Demo to team.

Scope of Work

In scope: The core work in Quarkus, the Chappie extension and some extensions usage. The populated vector DB.

Some example:

• Help with an exception when it occurs
• Generate Test classes from source
• Add JavaDoc to source
• Explain the source code
• Generate test data (import.sql)
• Help writing HQL
• Generate JS from OpenAPI spec
• and more !

Organizing the Work

Communication and Transparency: Coordination will be done in the relevant project's GitHub issue. Most work will be done in the Quarkiverse Extension (/~https://github.com/quarkiverse/quarkus-chappie) and the Chappie Bot (/~https://github.com/chappie-bot) and some in Quarkus code and the relevant extension.

Point of Contact: Phillip Kruger

Expected Timeline: ? 

Existing issues

see /~https://github.com/quarkiverse/quarkus-chappie/issues

[cescoffier]

Can you provide a few examples / tasks that could be considered once the mechanism is in place?
Also, can you highlith the architecture (the idea is not to have a dependency on an LLM from Quarkus "core", but like a dev service kind of thing.)

[phillip-kruger]

@cescoffier please check again

[cescoffier]

I think it's good to go!