aiide is a framework to build LLM copilots.
It is born out of 3 years of experience building LLM applications starting from GPT-3 completion models to the latest frontier chat models.
What you get with aiide? | What's not part of aiide? |
---|---|
Full control over content sent to the LLM | Verbose abstractions for common prompting techniques |
Tools and structured outputs are first class citizens for actions and content generation | Chains as a core building block |
Simplified streaming by default to build real-time apps | Output parsing tools |
Messages history is a Pandas DataFrame | Complex nested JSON objects |
Let's start by installing the package.
pip install aiide
This also installs LiteLLM and Pandas by default. If you would like to use other LLM providers such as Anthropic or Google AI, please install the respective SDK as well.
The whole tutorial uses OpenAI models but it should work with all the popular LLM providers.
Now that aiide is installed, let's create a simple chatbot similar to ChatGPT free tier.
from aiide import Aiide
class Chatbot(Aiide):
def __init__(self):
self.setup(system_message="You are a helpful assistant.", model="gpt-4o-mini-2024-07-18")
agent = Chatbot()
while True:
user_input = input("\nSend a message: ")
if user_input == "exit":
break
for delta in agent.chat(user_message=user_input):
if delta["type"] == "text":
print(delta["delta"],end="")
Let's break down the code:
- We defined a class Chatbot that inherits from Aiide. Classes are a great way to encapsulate the chatbot logic and state. It also enables sharing state with tools and structured outputs as we will see later.
- We set up the chatbot with a system message and a model. The model can be anything supported by LiteLLM.
- We then create an instance of the Chatbot and start a loop to chat with the bot.
- The chat loop returns a generator of deltas. Each delta has a type and content. The type can be either text, tool_call or tool_response. If the delta type is text, it will have delta and content as it's keys. If the delta type is tool_call, it will have name and arguments as it's keys. If the delta type is tool_response, it will have name, arguments and response as it's keys.
setup
andchat
has a lot of optional parameters that you can find while hovering over the method in your IDE. Some notable parameters forsetup
aremodel
,temperature
,api_key
, and any supported LiteLLM completion parameters. Similarly,chat
has parameters such astools
,stop_words
,tool_choice
etc.
user_message
can take a couple of types of inputs. It can be a string as you've just seen, it can be an image object(PIL.Image
) it can be an array of strings and images.
Different ways to use user_message:
user_message = "What's the weather like in SF"
image = Image.open("image.jpg")
user_message = image
user_message = [image, "Annotate the attached image"]
A natural question for the above snippet is how do we track the chat history?
aiide has first-class support for memory. I found that handling OpenAI JSON based schema is cumbersome and error-prone. So, I had abstracted the chat history into a Pandas DataFrame.
messages
is a pandas DataFrame that stores all the messages, tool calls and responses of a chat session.
You can access the memory of the chatbot by calling agent.messages
in the above example.
The schema of the messages DataFrame is as follows:
role | content | arguments | response |
---|---|---|---|
system | You are a helpful assistant | None | None |
user | What's the weather like in SF | None | None |
tool | {'name':'get_weather','id':'abc'} | {'location':'SF'} | {'temperature':'72'} |
assistant | The weather is 72 degress right now. | None | None |
You can use the memory DataFrame to analyze and manipulate the chat history and the tool calls and responses.
Currently the LLM can respond with text in any format. Sometimes it thinks first, sometimes it will answer in code right away. What if we want to structure the output in a specific way?
Currently to my knowledge, OpenAI and Google AI supports structured outputs. aiide has a common interface for structured outputs.
Let's see how we can use structured outputs in aiide.
from aiide import Aiide
from aiide.schema import structured_outputs_gen, Str
class Chatbot(Aiide):
def __init__(self):
self.setup(system_message="You are a helpful assistant.", model="gpt-4o-mini-2024-07-18")
def structured_ouputs(self):
return structured_outputs_gen(
name="chain_of_thought",
properties=[
Str(name="thinking", description="Use this field to think out loud. Breakdown the user's query, plan your response, etc."),
Str(name="response"),
],
required=["thinking", "response"],
)
agent = Chatbot()
while True:
user_input = input("\nSend a message: ")
if user_input == "exit":
break
for delta in agent.chat(user_message=user_input,json_mode=True):
if delta["type"] == "text":
print(delta["delta"],end="")
Test out the infamous question How many R letters are there in the word "strawberry"?
Now, let's break down the changes code:
- We import
structured_outputs_gen
andStr
fromaiide.schema
. Both of these will aide(heh) in defining the structured outputs json schema.
I did not love pydantic for defining json schemas. I have observed that a lot of developers are omitting fields such as descriptions and enums while defining schemas with pydantic. It also does not have an easier way to dynamically change the schema. So, I have created a simple interface to define structured outputs that is as flexible as possible and also helps the developer understand what they can do for each type by the help of intellisense. Please checkout the aiide's JSON Schema for more information.
- We override a method
structured_outputs
inAiide
that returns the structured output generator. The beauty of this is that you can define multiple structured outputs return the appropriate one based on the context. - We pass
json_mode=True
to thechat
method. This will enable the structured outputs.
Tools are the heart of aiide. They are the actions that the LLM can take. They can be as simple as a function call or as complex as a hierarchical LLM agents.
You define tools as classes and pass instances to the Aiide instance. The lifecycle of handling the tool calls, it's execution and feeding the response back into the LLM is all handled by aiide. You however, can still control the execution of the tool based on the values of deltas.
Let's see how we can define a tool in aiide.
import random
import json
from aiide import Aiide, Tool
from aiide.schema import tool_def_gen, Str
class WeatherTool(Tool):
def __init__(self, parent):
self.error = False
def tool_def(self):
return tool_def_gen(
name="get_current_weather",
description="Get the current weather in a given location",
properties=[
Str(
name="location",
description="The city and state, e.g. San Francisco, CA",
),
Str(name="unit", enums=["celsius", "fahrenheit"]),
],
)
def main(self, location, unit="default"): # type: ignore
if self.error:
return json.dumps({"error": 404})
else:
return json.dumps({"location": location, "temperature": random.randint(0, 100), "unit": unit})
class Agent(Aiide):
def __init__(self):
# passing the chatbot instance to the tool for bi-directional communication
self.weatherTool = WeatherTool(self)
self.setup(
system_message="You are a helpful assistant.",
)
agent = Agent()
for delta in agent.chat(
user_message="What's the weather like in San Francisco, Tokyo, and Paris?",
tools=[agent.weatherTool],
):
# printing response based on the type of delta
if delta["type"] == "text":
print(delta["delta"], end="")
if delta["type"] == "tool_call":
print("Tool called:", delta["name"], "with arguments:", delta["arguments"])
if delta["type"] == "tool_response":
print("Tool response for tool:", delta["name"], " with arguments:", delta["arguments"], "is:", delta["response"])
# changing the execution of the tool based on the context of the conversation
if delta["type"] == "tool_call" and "tokyo" in delta["arguments"].lower():
agent.weatherTool.error = True
else:
agent.weatherTool.error = False
Let's break down the code:
- We import
Tool
fromaiide
andtool_def_gen
andStr
fromaiide.schema
.Tool
is the base class for all tools in aiide.tool_def_gen
is a tool definition generator that helps in defining the tool schema.Str
is a string type that can have description, enums. - We define a class
WeatherTool
that inherits fromTool
. We define the__init__
method to initialize the tool. We define thetool_def
method to define the tool schema. We finally define themain
method to define the tool logic. - For activating the tool, we can pass the tool instance to the
chat
method through thetools
array parameter. - As mentioned previously, the delta has three types:
text
,tool_call
, andtool_response
. When type of delta is tool, the delta will have name and arguments keys for the tool called. After the tool is executed, the delta will have a type of tool_response and the response key will have the response of the tool. - If you observe the code, we are setting a boolean flag
error
in the tool instance based on the location. This way, you can control the execution of a tool based on the context of the conversation and the tool's state. A good example would be taking user's consent before executing code. - This way, you can activate or deactivate tools based on the context of the conversation.
The delta schema is as follows:
Type | Keys |
---|---|
text | - delta: The text content of the delta |
- content: The full content of the delta, including the text and any additional data | |
tool_call | - name: The name of the tool being called |
- arguments: The arguments passed to the tool | |
tool_response | - name: The name of the tool that generated the response |
- arguments: The arguments passed to the tool | |
- response: The response generated by the tool |
As mentioned earlier, aiide has a simple interface to define JSON schemas. This is useful for defining structured outputs and tools that might change based on the context of the conversation.
Please read the tutorial on aiide's JSON Schema.