Skip to content
forked from heiko-braun/cai

The Camel Quickstart Assistant helps you build Camel applications using a LLM backed agent that draws on documentation for Camel Quarkus and Camel Springboot.

License

Notifications You must be signed in to change notification settings

megacamelus/cai

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Camel Quickstart Assistant

Setup (Mac OS)

It's best served through a dedicated conda environment:

conda create --name camel python=3.11
conda activate camel
pip install -r requirements.txt

Prerequisites

What do I need besides this repo?

In short, you need twqo or three things to work woth the codebase:

  • an OpenAI API key (requires gpt-3 or gpt-4 models with support for function calling)
  • a postgres database (i.e. the free tier at https://aiven.io/postgresql)
  • a qdrant vector DB (i.e. the free tier at https://qdrant.tech)
  • a slack workspace and app for the slack bot

API Keys

All the tools and the assistant leverage 3rd party services for which you need API keys.

Make sure these are present in your environment:

export OPENAI_API_KEY="..."
export QDRANT_KEY="..."
export QDRANT_URL="..."
export PG_URL="..."

For the slack bot, you also need these:

export SLACK_BOT_TOKEN="..."
export SLACK_APP_TOKEN="..."

(See slack_tokens.md as well.)

Data Preparation

Step 1: Prepare the local data

The current impl serves the main knowledge through local files that have been scraped from the camel documentation.

As a first step you need to prepare the local data using the crawl and upsert tools available.

Once the process completes, you should have a text-only representation of the documentation under ./data/text/*.*.

Typically this is a one-time step

Step 2: Upsert the data

The data prepared, needs to be indexed and will be kept in a vector DB to enable semantic search for the agent.

In a second step you need to upsert data using the upsert tools available:

python upsert_pdf.py 

usage: upsert_pdf.py [-h] -c COLLECTION [-s START] [-b BATCHSIZE] [-p PROCESSES] [-m MODE] [-f FILE]

Once the process completes, you should have a meta data and vector embeddings in QDrant (http://qdrant.tech/).

Typically this is a one-time step

Using the assistant

Web based:

streamlit run agent-ui.py

CLI based:

python agent-cli.py [-f QUESTION.txt]

[...]

Results

user: How do I perform content filtering in Camel? Show me an example.

assistant: To perform content filtering in Apache Camel, you can use various mechanisms in the routing logic to transform content from the inbound message. Here are some examples:

  1. Using a Processor with the filtering programmed in Java:
from("direct:start")
    .process(new Processor() {
        public void process(Exchange exchange) {
            String body = exchange.getMessage().getBody(String.class);
            // do something with the body
            // and replace it back
            exchange.getMessage().setBody(body);
        }
    })
    .to("mock:result");
  1. Using a Bean EIP to use any Java method on any bean as a content filter:
from("activemq:My.Queue")
    .bean("myBeanName", "doFilter")
    .to("activemq:Another.Queue");
  1. Using an Expression to filter content from messages. For example, using XPath to filter an XML message to select all the <foo><bar> elements:
from("activemq:Input")
    .setBody().xpath("//foo:bar")
    .to("activemq:Output");

These examples demonstrate how to perform content filtering in Apache Camel using different mechanisms in the routing logic, such as Processor, Bean EIP, and Expression.

About

The Camel Quickstart Assistant helps you build Camel applications using a LLM backed agent that draws on documentation for Camel Quarkus and Camel Springboot.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Jupyter Notebook 73.8%
  • Python 26.1%
  • Dockerfile 0.1%