This release is a pre-release and may not be stable for production use.
teenyfactories
Agent runtime for TeenyFactories. Postgres-backed pub/sub, multi-provider LLM calls, vector search.
pip install --pre teenyfactories
import teenyfactories as tf
@tf.on_state('documents', 'loaded').do
def analyse(item):
tf.collection('documents').set(item['key'], state='analysed')
while True:
tf.run_pending()
tf.sleep(1)
Writing a row into a (collection, state) makes every subscriber to that pair pick it up: (collection, state) is a FIFO queue, and the handler consumes a row by transitioning its state (or deleting it). That's the framework.
Public API
| Group | Names |
|---|---|
| Pub/sub | on_state, run_pending (the only pub/sub primitive — no message bus) |
| Data | collection (.set, .add, .get, .get_all, .remove, .count, .exists, .first, .state, .where, .limit, .vector_search), embed |
| LLM | llm (fluent builder — .ask / .run_agent_loop), call_llm (LEGACY) |
| MCP | add_mcp_server, add_mcp_tool |
| Schedule | on_schedule.every(N).<unit>.do(handler) |
| Secrets / files | secrets, bucket_store (+ BucketStoreError family) |
| Logging | log_debug, log_info, log_warn, log_error, log_persona |
| Time / IDs | get_timestamp, get_timestamp_utc, generate_unique_id |
| Debug | breakpoint |
| Lifecycle / config | sleep, shutting_down, FACTORY_NAME, AGENT_NAME, AGENT_SLUG, AGENT_ID, __version__ |
Anything not in this list is not part of the supported surface — don't reach into submodules.
How it plugs in
A factory is a directory:
my_factory/
├── factory.yml
└── agents/
├── poller.py
└── enricher.py
Each agents/*.py runs in its own container based on ghcr.io/teenyfactories/agent:dev — which has this library pre-installed. Single-factory mode runs each file as a docker compose service; multi-factory mode runs them under the orchestrator. Either way, agent code is just import teenyfactories as tf + handlers + main loop.
Full setup, compose templates, environment variable reference: see the core repo.
Versioning
PEP 440 dev pre-releases: 0.1.0.devYYYYMMDD. pip install teenyfactories will NOT pick these up — you need --pre (latest dated build) or an explicit pin (teenyfactories==0.1.0.dev20260512).
License
MIT.
1 maintainer
Metadata
1 maintainer
Release files for teenyfactories 0.1.0.dev20260720
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 |
|---|---|---|---|---|
| teenyfactories-0.1.0.dev20260720.tar.gz | 95.9 kB | Without provenance | Details for teenyfactories-0.1.0.dev20260720.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| teenyfactories-0.1.0.dev20260720-py3-none-any.whl | Python 3 | none | any | Details for teenyfactories-0.1.0.dev20260720-py3-none-any.whl |
Total release size: 198.7 kB
Release files / teenyfactories-0.1.0.dev20260720.tar.gz
| Download URL | teenyfactories-0.1.0.dev20260720.tar.gz |
|---|---|
| Size | 95.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af9f3b89e2cbb45744c759bc6e4a754cc33fb04327038731b22332a0157abb58
|
|
BLAKE2b-256 checksum How to use checksums |
f16dde5f37b741650f8fa80791133e2a72f0c7bd85bdb9290d9b331e2a2bd208
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / teenyfactories-0.1.0.dev20260720-py3-none-any.whl
| Download URL | teenyfactories-0.1.0.dev20260720-py3-none-any.whl |
|---|---|
| Size | 102.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d76f16a6c87d154dfbac8c600583ca6a97ed804195dadc30dbf2eca377b9740
|
|
BLAKE2b-256 checksum How to use checksums |
420fd22eeb146127d99f1dc9697c6fb196f187bced57cfbe13ee397d7891d12f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for teenyfactories 0.1.0.dev20260720
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.
