WG - Chappie #45377
phillip-kruger
started this conversation in
Design Discussions
WG - Chappie
#45377
Replies: 1 comment
-
Can you provide a few examples / tasks that could be considered once the mechanism is in place? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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.
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.
Organizing the Work
Existing issues
see https://github.com/quarkiverse/quarkus-chappie/issues
Beta Was this translation helpful? Give feedback.
All reactions