3tears-conversations
Canonical owner of the per-agent conversations table plus its entity and three-tier collection.
Purpose
Tracks one row per user-facing conversation an agent is engaged in: ownership scope (agent_id, customer_id, user_id), external reference (channel_type, conversation_ref), lifecycle (status, summary), timestamps (date_created, date_updated, date_last_message).
This table is owned here because multiple packages key off conversation_id (memory, agent-tools context items, workspace bindings) and no single consumer is the natural owner of the shape. Owning the table here lets each downstream package depend on conversations without pulling in memory's extraction pipeline.
Public API
Exports (see src/threetears/conversations/__init__.py):
Conversation--BaseEntitysubclass for a single row.ConversationsCollection-- three-tier (L1SQLite /L2NATS KV /L3postgres) collection with the usualget/save/subscriptsemantics.register(runner)-- agent-scope migration entry point. Contributes theconversationstable creation to a canonicalthreetears.core.data.migrations.MigrationRunner. Nodepends_onedges; this is the root of the agent-schema dependency graph, so memory / workspace / tools migrations that referenceconversations.idsort after it.
Minimal usage
from threetears.conversations import Conversation, ConversationsCollection, register
from threetears.core.data.migrations import MigrationRunner
# 1. register the package's migrations on the runner; run_migrations pins one
# pooled connection and holds the database-wide DDL lock for the whole run
runner = MigrationRunner()
register(runner)
await store.run_migrations(runner)
# 2. use the collection like any other 3tears collection
collection = ConversationsCollection(registry=registry)
conv = await collection.get(conversation_id)
conv.summary = "follow-up on last week's analysis"
await conv.save()
Reference
- Downstream consumers:
threetears.agent.memory,threetears.agent.tools(context items),threetears.agent.workspace(bindings)
1 maintainer
Metadata
1 maintainer
Release files for 3tears-conversations 0.59.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 | |
|---|---|---|---|
| 3tears_conversations-0.59.0.tar.gz | 88.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3tears_conversations-0.59.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 151.3 kB
Release files / 3tears_conversations-0.59.0.tar.gz
| Download URL | 3tears_conversations-0.59.0.tar.gz |
|---|---|
| Size | 88.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c643a01923c75a3cea94aea579028be58fdb2af19a04edc1f966a4008661fa40
|
|
BLAKE2b-256 checksum How to use checksums |
aef78e3d0ff555a6cb2ea14ce777e88b4f87b39e142ba0609822d891e473a247
|
| 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 3, 2026.
Transparency logRelease files / 3tears_conversations-0.59.0-py3-none-any.whl
| Download URL | 3tears_conversations-0.59.0-py3-none-any.whl |
|---|---|
| Size | 63.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
919f24f14ae0a985d4f966390e2deedaf5449938a76d363b18549ed3bca55f70
|
|
BLAKE2b-256 checksum How to use checksums |
c722433d162ef9233328e3d69df4c364884c6adc62ddc1c37574ed883d1dc081
|
| 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 3, 2026.
Transparency log
