This release is a pre-release and may not be stable for production use.
withlore
Connect your voice or text agent to Lore. Lore records its traces, tool calls, conversations and call audio, then simulates users against it and grades every conversation.
Documentation: docs.lore-labs.ai
Create a key in Lore under Settings → Projects & keys, then:
export LORE_API_KEY="lore_sk_..."
Voice agents (LiveKit)
pip install "withlore[livekit]"
In your job entrypoint, before session.start():
from withlore.livekit import observe
await observe(ctx, session)
await session.start(agent=agent, room=ctx.room)
Lore records both sides of the call audio, the transcript with per-turn latency, tool calls and LiveKit's spans. When Lore simulates callers against your agent, the same call records into the simulation instead of production. See the LiveKit guide.
Text and AI agents
Install withlore with the extra for your framework, then call withlore.init() at
startup, before you create your model client.
pip install "withlore[openai]"
import withlore
withlore.init()
with withlore.conversation() as convo:
reply = client.chat.completions.create(model="gpt-5-mini", messages=messages)
convo.record(messages + [reply.choices[0].message])
withlore.init() records traces. convo.record() records the conversation from the
messages your framework already keeps: OpenAI and Anthropic message lists, OpenAI Agents
SDK results, LangChain and LangGraph messages, and Claude Agent SDK messages.
| Framework | Install |
|---|---|
| OpenAI | withlore[openai] |
| Anthropic | withlore[anthropic] |
| OpenAI Agents SDK | withlore[openai-agents] |
| Claude Agent SDK | withlore[claude-agent-sdk] |
| LangChain / LangGraph | withlore[langchain] |
See Record conversations for chats that span several requests.
Simulate and evaluate
withlore.Client and the withlore CLI run scenarios, simulations and grading from
code or CI. Start with withlore auth login, then withlore catalog --json. See
Evaluate your agent.
Privacy
By default Lore receives operational metadata only: models, token counts, timing and status. Prompts, transcripts, tool payloads and audio are recorded only when your code asks for them and your project admits them. See Privacy.
Links
Licensed under Apache-2.0.
Metadata
Release files for withlore 0.2.0a23
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 | |
|---|---|---|---|---|
| withlore-0.2.0a23.tar.gz | 531.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| withlore-0.2.0a23-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 631.8 kB
Release files / withlore-0.2.0a23.tar.gz
| Download URL | withlore-0.2.0a23.tar.gz |
|---|---|
| Size | 531.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae1f753406e5af4a1283998320f2b6f3e337cbfb975550958fe2bc751ff01ca5
|
|
BLAKE2b-256 checksum How to use checksums |
df09e99ab8d8415dba61c41a4b12365bf99d64c24190c9d65688c72050b8505b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / withlore-0.2.0a23-py3-none-any.whl
| Download URL | withlore-0.2.0a23-py3-none-any.whl |
|---|---|
| Size | 100.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09e04d54af60cf41f7bacd23f279e1fb8fbd51f8b10206092ed827c80c676fed
|
|
BLAKE2b-256 checksum How to use checksums |
022859fa06177cd67cfd0dcbebe2da1552cdc76e22df835623a1f33d01cda6ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for withlore 0.2.0a23
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for withlore-0.2.0a23.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA 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.