xtr-ai-orm-conversation-store
Agent conversations kept in two tables on an xtr-orm connection, for xtr-ai.
Install
uv add "xtr-ai[orm]"
The orm extra installs this package.
Use
OrmConversationStore is a pydantic-ai ConversationStore. Give it the connection's primary
engine:
from pydantic_ai.conversation import Conversation
from xtr_ai_orm_conversation_store import OrmConversationStore
store = OrmConversationStore(engine)
conversation = await store.load(conversation_id) or Conversation(conversation_id=conversation_id)
result = await agent.run(prompt, conversation=conversation)
await store.save(result)
In an application, configure it in xtr-ai instead, as
conversation_stores={"default": OrmConversationStoreConfig(connection="default")}, and inject
ConversationStore. See xtr-ai's Use in an application.
Tables
| Table | Holds |
|---|---|
ai_conversation |
One row per conversation: where its history ends, usage, pending tool calls, scope, branches, fork origin, revision |
ai_conversation_entry |
One row per message, pointing at the one before it; shared by a conversation and its forks |
table_prefix changes ai_. ConversationMappingDriver adds the tables to a connection's
definitions, so orm:migrations:diff writes them. xtr-ai registers it when the store is
configured.
Behaviour
- Own transactions. Every call runs in a short transaction of its own and commits before it
returns. A store never joins the caller's unit of work.
- A long model call holds no database connection.
- Rolling back the caller's work never undoes a saved turn.
- A conversation cannot be saved atomically with the application's own rows.
- Conflicts. A record and the messages it adds are written in one transaction. A save over a
newer revision raises
ConversationConflictand leaves neither behind. - History. A conversation's history is read in one recursive query.
- Deleting. Deleting a conversation deletes the messages only it reaches. Messages a fork,
or its origin, still reaches stay until the last of them is deleted.
- A fork saved while its origin is being deleted can lose the messages it shares with it, except on SQLite, where writes take turns. Don't fork a conversation you are deleting.
- Databases. It runs on PostgreSQL, MySQL 8 and SQLite, through their async drivers.
Development
uv sync
uv run ruff check && uv run ruff format --check && uv run basedpyright && uv run ty check && uv run pytest
License
MIT
Metadata
Release files for xtr-ai-orm-conversation-store 6.7.0
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 |
|---|---|---|---|---|
| xtr_ai_orm_conversation_store-6.7.0.tar.gz | 9.5 kB | With provenance | Details for xtr_ai_orm_conversation_store-6.7.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xtr_ai_orm_conversation_store-6.7.0-py3-none-any.whl | Python 3 | none | any | Details for xtr_ai_orm_conversation_store-6.7.0-py3-none-any.whl |
Total release size: 20.5 kB
Release files / xtr_ai_orm_conversation_store-6.7.0.tar.gz
| Download URL | xtr_ai_orm_conversation_store-6.7.0.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c47d1c3c67e78e470d3f87abca32f9f11d6de7ba5a0c7458e94d87993c6cd50a
|
|
BLAKE2b-256 checksum How to use checksums |
509fe80efa43f5e80ca1cb2e8979a5b6284f2990ac5d5a81cdfade632ecd7a01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Nov 13, 2026.
Transparency logRelease files / xtr_ai_orm_conversation_store-6.7.0-py3-none-any.whl
| Download URL | xtr_ai_orm_conversation_store-6.7.0-py3-none-any.whl |
|---|---|
| Size | 11.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7285cee9c5ee02b4c89419d4073214b8f876b8ad23eb5831c6014f4712db9c31
|
|
BLAKE2b-256 checksum How to use checksums |
e62488d6c46a51848613c477c3e0ad84dd336b1b6a47885eb4e19d52d5e4d1a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.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.
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 Nov 13, 2026.
Transparency logSecurity for xtr-ai-orm-conversation-store 6.7.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for xtr_ai_orm_conversation_store-6.7.0.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 Nov 13, 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.