Pixie
Generate Evals from debugging LLM Applications
Evals takes a lot of effort to setup, and the results are not always helpful. What if we can generate evals automatically based on how you debug your LLM applications?
Demo
Get Started
1. Setup
In your project folder, install pixie-sdk package:
pip install pixie-sdk
Start the local debug server by running:
pixie
2. Connect Your Application
Add @pixie.session decorator to any code you'd like to debug, use pixie.print(...) to log data to the debugger UI.
# my_chatbot.py
import asyncio
from pydantic_ai import Agent
import pixie.sdk as pixie
# You can implement your application using any major AI development framework
agent = Agent(
name="Simple chatbot",
instructions="You are a helpful assistant.",
model="gpt-4o-mini",
)
@pixie.session
async def my_chatbot():
"""Chatbot application example."""
await pixie.print("How can I help you today?")
messages = []
while True:
user_msg = await asyncio.to_thread(input)
await pixie.print(user_msg, from_user=True)
response = await agent.run(user_msg, message_history=messages)
messages = response.all_messages()
await pixie.print(response.output)
3. Debug with web UI
Visit the web UI gopixie.ai to start debugging.
Run your application as normal while pixie debug server is running, and your session would show up in the debugger UI.
Important Links
- Documentation - Complete documentation with tutorials and API reference
- Examples - Real-world examples and sample applications
- Demo - Live Demo with the examples server setup
- Discord - Join our community for support and discussions
Acknowledgments
This project is built on top of many awesome open-source projects:
- Langfuse for instrumentation
- Pydantic for structured data validation
- FastAPI for web API
- Strawberry for graphql
- Uvicorn for web server
- Janus for sync-async queue
- docstring-parser for docstring parsing
Metadata
Release files for pixie-sdk 0.2.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pixie_sdk-0.2.16.tar.gz | 269.1 kB | Without provenance | Details for pixie_sdk-0.2.16.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pixie_sdk-0.2.16-py3-none-any.whl | Python 3 | none | any | Details for pixie_sdk-0.2.16-py3-none-any.whl |
Total release size: 743.4 kB
Release files / pixie_sdk-0.2.16.tar.gz
| Download URL | pixie_sdk-0.2.16.tar.gz |
|---|---|
| Size | 269.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bd0e3739f40271e165c684bc154ebdf94fbe162b88e8b30280f11a4dbe809e4
|
|
BLAKE2b-256 checksum How to use checksums |
ffc796e11b29b05c674dcb0a2247f7c24f2bcc2bec897cad07dad68fedcacc56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.2 CPython/3.12.12 Linux/6.11.0-1018-azure
|
Release files / pixie_sdk-0.2.16-py3-none-any.whl
| Download URL | pixie_sdk-0.2.16-py3-none-any.whl |
|---|---|
| Size | 474.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11bd6afb487911eb8d1425482bdff36dd4cb2889687eac3c8a45dee46815d350
|
|
BLAKE2b-256 checksum How to use checksums |
c784752c7765cfa04a6a5734f058d569fd70e8f4905af250199c4ba581603985
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.3.2 CPython/3.12.12 Linux/6.11.0-1018-azure
|
Security for pixie-sdk 0.2.16
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.