Skip to content

LlamaBot: A Pythonic bot interface to LLMs

LlamaBot implements a Pythonic interface to LLMs, making it much easier to experiment with LLMs in a Jupyter notebook and build Python apps that utilize LLMs. All models supported by LiteLLM are supported by LlamaBot.

Install LlamaBot

To install LlamaBot:

pip install llamabot==0.12.10

This will give you the minimum set of dependencies for running LlamaBot.

To install all of the optional dependencies, run:

pip install "llamabot[all]"

Get access to LLMs

Option 1: Using local models with Ollama

LlamaBot supports using local models through Ollama. To do so, head over to the Ollama website and install Ollama. Then follow the instructions below.

Option 2: Use an API provider

OpenAI

If you have an OpenAI API key, then configure LlamaBot to use the API key by running:

export OPENAI_API_KEY="sk-your1api2key3goes4here"

Mistral

If you have a Mistral API key, then configure LlamaBot to use the API key by running:

export MISTRAL_API_KEY="your-api-key-goes-here"

Other API providers

Other API providers will usually specify an environment variable to set. If you have an API key, then set the environment variable accordingly.

Option 3: Using local models with LMStudio

LlamaBot supports using local models through LMStudio via LiteLLM. To use LMStudio with LlamaBot:

  1. Install and set up LMStudio
  2. Load your desired model in LMStudio
  3. Start the local server in LMStudio (usually runs on http://localhost:1234)
  4. Set the environment variable for LMStudio's API base:
export LM_STUDIO_API_BASE="http://localhost:1234"
  1. Use the model with LlamaBot using the lm_studio/ prefix:
from llamabot import SimpleBot

system_prompt = "You are a helpful assistant."
bot = SimpleBot(
    system_prompt,
    model_name="lm_studio/your-model-name"  # Use lm_studio/ prefix
)

Replace your-model-name with the actual name of the model you've loaded in LMStudio. LlamaBot can use any model provider that LiteLLM supports, and LMStudio is one of the many supported providers.

How to use

SimpleBot

The simplest use case of LlamaBot is to create a SimpleBot that keeps no record of chat history. This is effectively the same as a stateless function that you program with natural language instructions rather than code. This is useful for prompt experimentation, or for creating simple bots that are preconditioned on an instruction to handle texts and are then called upon repeatedly with different texts.

Using SimpleBot with an API provider

For example, to create a Bot that explains a given chunk of text like Richard Feynman would:

from llamabot import SimpleBot

system_prompt = "You are Richard Feynman. You will be given a difficult concept, and your task is to explain it back."
feynman = SimpleBot(
  system_prompt,
  model_name="gpt-3.5-turbo"
)

For using GPT, you need to have the OPENAI_API_KEY environment variable configured. If you want to use SimpleBot with a local Ollama model, check out this example

Now, feynman is callable on any arbitrary chunk of text and will return a rephrasing of that text in Richard Feynman's style (or more accurately, according to the style prescribed by the system_prompt). For example:

prompt = """
Enzyme function annotation is a fundamental challenge, and numerous computational tools have been developed.
However, most of these tools cannot accurately predict functional annotations,
such as enzyme commission (EC) number,
for less-studied proteins or those with previously uncharacterized functions or multiple activities.
We present a machine learning algorithm named CLEAN (contrastive learning–enabled enzyme annotation)
to assign EC numbers to enzymes with better accuracy, reliability,
and sensitivity compared with the state-of-the-art tool BLASTp.
The contrastive learning framework empowers CLEAN to confidently (i) annotate understudied enzymes,
(ii) correct mislabeled enzymes, and (iii) identify promiscuous enzymes with two or more EC numbers—functions
that we demonstrate by systematic in silico and in vitro experiments.
We anticipate that this tool will be widely used for predicting the functions of uncharacterized enzymes,
thereby advancing many fields, such as genomics, synthetic biology, and biocatalysis.
"""
feynman(prompt)

This will return something that looks like:

Alright, let's break this down.

Enzymes are like little biological machines that help speed up chemical reactions in our
bodies. Each enzyme has a specific job, or function, and we use something called an
Enzyme Commission (EC) number to categorize these functions.

Now, the problem is that we don't always know what function an enzyme has, especially if
it's a less-studied or new enzyme. This is where computational tools come in. They try
to predict the function of these enzymes, but they often struggle to do so accurately.

So, the folks here have developed a new tool called CLEAN, which stands for contrastive
learning–enabled enzyme annotation. This tool uses a machine learning algorithm, which
is a type of artificial intelligence that learns from data to make predictions or
decisions.

CLEAN uses a method called contrastive learning. Imagine you have a bunch of pictures of
cats and dogs, and you want to teach a machine to tell the difference. You'd show it
pairs of pictures, some of the same animal (two cats or two dogs) and some of different
animals (a cat and a dog). The machine would learn to tell the difference by contrasting
the features of the two pictures. That's the basic idea behind contrastive learning.

CLEAN uses this method to predict the EC numbers of enzymes more accurately than
previous tools. It can confidently annotate understudied enzymes, correct mislabeled
enzymes, and even identify enzymes that have more than one function.

The creators of CLEAN have tested it with both computer simulations and lab experiments,
and they believe it will be a valuable tool for predicting the functions of unknown
enzymes. This could have big implications for fields like genomics, synthetic biology,
and biocatalysis, which all rely on understanding how enzymes work.

Using SimpleBot with a Local Ollama Model

If you want to use an Ollama model hosted locally, then you would use the following syntax:

from llamabot import SimpleBot

system_prompt = "You are Richard Feynman. You will be given a difficult concept, and your task is to explain it back."
bot = SimpleBot(
    system_prompt,
    model_name="ollama_chat/llama2:13b"
)

Simply specify the model_name keyword argument following the <provider>/<model name> format. For example:

All you need to do is make sure Ollama is running locally; see the Ollama documentation for more details. (The same can be done for the QueryBot class below!)

The model_name argument is optional. If you don't provide it, Llamabot will try to use the default model. You can configure that in the DEFAULT_LANGUAGE_MODEL environment variable.

SimpleBot with memory for chat functionality

If you want chat functionality with memory (similar to what ChatBot provided), you can use SimpleBot with a LanceDBDocStore as memory. This allows the bot to remember previous conversations:

from llamabot import SimpleBot, LanceDBDocStore

# Create a bot with memory
system_prompt = "You are Richard Feynman. You will be given a difficult concept, and your task is to explain it back."
chat_memory = LanceDBDocStore(table_name="feynman_chat")
feynman = SimpleBot(
    system_prompt,
    chat_memory=chat_memory,
    model_name="gpt-3.5-turbo"
)

# Have a conversation
response1 = feynman("Can you explain quantum mechanics?")
print(response1)

# The bot remembers the previous conversation
response2 = feynman("Can you give me a simpler explanation?")
print(response2)

The LanceDBDocStore will persist your conversation history using vector embeddings, allowing the bot to semantically search through previous exchanges and maintain context across multiple interactions.

QueryBot

The final bot provided is a QueryBot. This bot lets you query a collection of documents. QueryBot now works with a docstore that you create first, making it more modular.

Here's how to use QueryBot with a docstore:

from llamabot import QueryBot
from llamabot.docstore import LanceDBDocStore
from pathlib import Path

# First, create a docstore and add your documents
docstore = LanceDBDocStore(table_name="eric_ma_blog")
docstore.add_documents([
    Path("/path/to/blog/post1.txt"),
    Path("/path/to/blog/post2.txt"),
    # ... more documents
])

# Then, create a QueryBot with the docstore
bot = QueryBot(
  system_prompt="You are an expert on Eric Ma's blog.",
  docstore=docstore,
  # Optional:
  # model_name="gpt-3.5-turbo"
  # or
  # model_name="ollama_chat/mistral"
)

result = bot("Do you have any advice for me on career development?")

You can also use an existing docstore:

from llamabot import QueryBot
from llamabot.docstore import LanceDBDocStore

# Load an existing docstore
docstore = LanceDBDocStore(table_name="eric_ma_blog")

# Create QueryBot with the existing docstore
bot = QueryBot(
  system_prompt="You are an expert on Eric Ma's blog",
  docstore=docstore,
  # Optional:
  # model_name="gpt-3.5-turbo"
  # or
  # model_name="ollama_chat/mistral"
)

result = bot("Do you have any advice for me on career development?")

For more explanation about the model_name, see the examples with SimpleBot.

ImageBot

With the release of the OpenAI API updates, as long as you have an OpenAI API key, you can generate images with LlamaBot:

from llamabot import ImageBot

bot = ImageBot()
# Within a Jupyter notebook:
url = bot("A painting of a dog.")

# Or within a Python script
filepath = bot("A painting of a dog.")

# Now, you can do whatever you need with the url or file path.

If you're in a Jupyter Notebook, you'll see the image show up magically as part of the output cell as well.

Experimentation

Automagically record your prompt experimentation locally on your system by using llamabot's Experiment context manager:

from llamabot import Experiment, prompt, metric

@prompt
def sysprompt():
    """You are a funny llama."""

@prompt
def joke_about(topic):
    """Tell me a joke about {{ topic }}."""

@metric
def response_length(response) -> int:
    return len(response.content)

with Experiment(name="llama_jokes") as exp:
    # You would have written this outside of the context manager anyways!
    bot = SimpleBot(sysprompt(), model_name="gpt-4o")
    response = bot(joke_about("cars"))
    _ = response_length(response)

And now they will be viewable in the locally-stored message logs:

CLI Demos

Llamabot comes with CLI demos of what can be built with it and a bit of supporting code.

Here is one where I expose a chatbot directly at the command line using llamabot chat:

Watch the terminal session on Asciinema

And here is another one where llamabot is used as part of the backend of a CLI app to chat with one's Zotero library using llamabot zotero chat:

Watch the terminal session on Asciinema

And finally, here is one where I use llamabot's SimpleBot to create a bot that automatically writes commit messages for me.

Watch the terminal session on Asciinema

Caching

LlamaBot uses a caching mechanism to improve performance and reduce unnecessary API calls. By default, all cache entries expire after 1 day (86400 seconds). This behavior is implemented using the diskcache library.

Cache Configuration

The cache is automatically configured when you use any of the bot classes (SimpleBot or QueryBot). You don't need to set up the cache manually.

Cache Location

The default cache directory is located at:

~/.llamabot/cache

Cache Timeout

The cache timeout can be configured using the LLAMABOT_CACHE_TIMEOUT environment variable. By default, the cache timeout is set to 1 day (86400 seconds). To customize the cache timeout, set the LLAMABOT_CACHE_TIMEOUT environment variable to the desired value in seconds. For example:

export LLAMABOT_CACHE_TIMEOUT=3600

This will set the cache timeout to 1 hour (3600 seconds).

Contributing

New features

New features are welcome! These are early and exciting days for users of large language models. Our development goals are to keep the project as simple as possible. Features requests that come with a pull request will be prioritized; the simpler the implementation of a feature (in terms of maintenance burden), the more likely it will be approved.

Bug reports

Please submit a bug report using the issue tracker.

Questions/Discussions

Please use the issue tracker on GitHub.

Contributors

Rena Lu
Rena Lu
💻		 andrew giessel
andrew giessel
🤔 🎨 💻		 Aidan Brewis
Aidan Brewis
💻		 Eric Ma
Eric Ma
🤔 🎨 💻		 Mark Harrison
Mark Harrison
🤔		 reka
reka
📖 💻		 anujsinha3
anujsinha3
�� 📖
Elliot Salisbury
Elliot Salisbury
📖		 Ethan Fricker, PhD
Ethan Fricker, PhD
📖		 Ikko Eltociear Ashimine
Ikko Eltociear Ashimine
📖		 Amir Molavi
Amir Molavi
🚇 📖