Skip to main content

Lightweight LLM call logger for OpenAI/Anthropic

Project description

Log and View Python Based LLM Conversations

LLM Logger is a lightweight, local-first tool for inspecting and understanding how your application interacts with large language models like OpenAI GPT-4 or Anthropic Claude.

It helps you:

  • Log and inspect each model call with request/response metadata
  • View differences between turns in a conversation
  • Visualize tool calls, tool responses, and system prompts
  • Compare prompt strategies and debug session behavior

Ideal for developers building agent workflows, chat interfaces, or prompt-based systems.


✨ Features

  • One-line setup – Start logging with a simple wrapper around your OpenAI client
  • 🧠 Automatic session tracking – No manual session IDs or state management required
  • 📀 Local-first logging – Stores structured logs as JSON on your machine
  • 🔍 Rich session insights – Context diffs, tool call/response blocks, and system prompt visibility
  • ⏱️ Latency + metadata capture – Track timing, models, and more with every call
  • 🧹 Framework-agnostic – Works with any Python codebase
  • 🛡️ Privacy-first – Fully offline, no account or server required
  • 🌐 Simple UI – Static frontend served locally; no build step needed for end users
  • 👐 Open source (MIT) – Lightweight, auditable, and easy to extend

📦 Installation

🔹 Installation Options

Option 1: From PyPI (Recommended for most users)

Install the prebuilt package if you just want to use the tool:

pip install llm-logger

Option 2: Local Copy (For direct integration or customization)

Clone the repository and install:

# Clone the repo
git clone https://github.com/akhalsa/llm_debugger.git

# rebuild ui (optional)
cd llm_debugger/llm_logger/front_end
npm install
npx tsc

# Install from the local copy
pip install ./llm_debugger

Note: All installation methods include pre-compiled frontend files. No Node.js or frontend build steps are required for basic usage. The static files (HTML, CSS, JS) are packaged with the library, so the debugger UI works out of the box.

Rebuilding using npm install and npx tsc are required to update the .js files in the static/ folder


🔸 Development Setup (Only for contributors)

If you want to modify the logger or UI code:

  1. Prerequisites:

    • Python ≥ 3.8
    • Node.js & npm (only needed for UI development)
  2. Setup:

    git clone https://github.com/akhalsa/llm_debugger.git
    cd llm_debugger
    
    # Optional: Create a virtual environment
    python3 -m venv venv
    source venv/bin/activate
    
    # Install in development mode
    pip install -e .
    
  3. Frontend Development (only if modifying the UI):

    cd llm_logger/front_end
    npm install
    npx tsc  # Compiles TypeScript to ../static
    

🚀 Usage

1. Wrap Your OpenAI Client

from dotenv import load_dotenv
import openai
import os
from llm_logger import wrap_openai

load_dotenv()
api_key = os.getenv("OPENAI_API_KEY")

openai_client = wrap_openai(
    openai.OpenAI(api_key=api_key),
    logging_account_id="my_project"
)

Then use openai_client as normal:

response = openai_client.chat.completions.create(
    model="gpt-4",
    messages=[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "What's the capital of France?"}
    ]
)

This writes logs to .llm_logger/logs/.


2. Launch the Log Viewer

Option A: Stand Alone Service Launched From Terminal

This option is ideal for viewing logs from an application running on your local device

# Default port (8000)
llm_logger

# Or specify a custom port
llm_logger -p 8000

Then open in your browser:

http://localhost:8000

Option B: As An Endpoint In Your Python Web Application

You can run the debugger UI alongside your application if you're using a python webapp

Same Process (using FastAPI):

from fastapi import FastAPI
import uvicorn
from llm_logger.server import create_app as create_log_viewer_app
log_viewer_app = create_log_viewer_app(base_url="/debugger")

# Your main application
app = FastAPI()

# Mount the debugger UI at /debugger
app.mount("/debugger", log_viewer_app)

# Run your application
if __name__ == "__main__":
    uvicorn.run(app, host="0.0.0.0", port=5000)

With Custom Base URL:

If you need to specify a custom base URL (for example, when the debugger is mounted at a specific path or accessed through a reverse proxy), you can use the create_app function:

from fastapi import FastAPI
from llm_logger.server import create_app

# Your main application
app = FastAPI()

# Create debugger app with custom base URL
debugger_app = create_app(base_url="/debugger")  # or any other path where it's mounted

# Mount the debugger UI
app.mount("/debugger", debugger_app)

This ensures that all internal links and API calls in the debugger UI will use the correct base URL.

Parallel Process (e.g., in Docker): In production or distributed development environments, it is recommended to run the llm_logger UI as a stand alone process.

# Start your main application
uvicorn your_app:app --host 0.0.0.0 --port 5000 &

# Start the debugger UI on a different port
llm_logger -p 8000 &

# Wait for both processes
wait

Option C: Docker Environment

If you're using Docker, you can include the debugger UI in your Dockerfile without requiring Node.js:

FROM python:3.9-slim

WORKDIR /app

# Install dependencies
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt

# Copy your application code
COPY . .

# Expose ports for both your app and the debugger
EXPOSE 5000 8000

# Start both services
CMD ["bash", "-c", "uvicorn your_app:app --host 0.0.0.0 --port 5000 & llm_logger -p 8000 & wait"]

🛠️ Roadmap Ideas

  • Replay conversation with inline visualization
  • Claude and other model support
  • UI analytics and filters
  • Exportable reports and session sharing
  • Plugin hooks and configuration options

📬 Feedback

Found a bug or have a feature request? Open an issue.


📜 License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

llm_logger-0.1.3.2.tar.gz (15.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

llm_logger-0.1.3.2-py3-none-any.whl (15.4 kB view details)

Uploaded Python 3

File details

Details for the file llm_logger-0.1.3.2.tar.gz.

File metadata

  • Download URL: llm_logger-0.1.3.2.tar.gz
  • Upload date:
  • Size: 15.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.12.5

File hashes

Hashes for llm_logger-0.1.3.2.tar.gz
Algorithm Hash digest
SHA256 4a327ca5a9d72de72cc5b6fd8a56769c66ec42e8f2d75ea8acc03d152027d21c
MD5 2d2bf3189ac4dd14ecbcab8e9c10c3e0
BLAKE2b-256 3377aff52f7d9695a8ab75825fd9367e29a2d486d512243a18bd48d5603086b8

See more details on using hashes here.

File details

Details for the file llm_logger-0.1.3.2-py3-none-any.whl.

File metadata

  • Download URL: llm_logger-0.1.3.2-py3-none-any.whl
  • Upload date:
  • Size: 15.4 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.12.5

File hashes

Hashes for llm_logger-0.1.3.2-py3-none-any.whl
Algorithm Hash digest
SHA256 07dc97806344b3a9b1bf17056179ce95bcb8e069df831b0ec5aa2af0470a6da0
MD5 110a3e9b90d0033688c714b17f04ed71
BLAKE2b-256 a9a663f178882f0f72a8647f8acaa19ced9d380aea74e202fc6971106a5aee77

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page