Skip to main content

zizkadb-crewai

PyPI: zizkadb-crewai 0.1.4 · requires zizkadb-sdk>=0.4.1

Self-hosted, open-source observability and causal debugging for CrewAI.

A CrewAI run is normally a black box: when the output is wrong, it's hard to see which task or agent caused it. zizkadb-crewai logs every step of a crew run to ZizkaDB with a parent_id link, so a run becomes a causal tree — and one call, db.why(), walks that tree back to the root cause.

It doesn't only show what happened; it explains why it happened.

CrewAI run ──▶ ZizkaDBCrewLogger ──▶ ZizkaDB (causal store) ──▶ db.why() / dashboard

Install

Both packages are published on PyPI — no git URLs needed:

pip install zizkadb-sdk zizkadb-crewai crewai

Usage

ZizkaDBCrewLogger logs the crew lifecycle. Events auto-chain through the logger's last_event_id, so you can omit parent_id to link each event to the previous one.

Method Event type Purpose
await log_kickoff(goal, **extra) crew_kickoff Start of the run (root of the chain)
await log_task(description, *, parent_id=None, **extra) crew_task One node per task
await log_output(output, *, parent_id=None, **extra) crew_output Final result
from zizkadb import ZizkaDB
from zizkadb_crewai import ZizkaDBCrewLogger

# OSS-first: default to a local self-hosted instance; pass api_key only for remote/cloud.
async with ZizkaDB(host="http://localhost:8000") as db:
    logger = ZizkaDBCrewLogger(db=db, agent="research-crew")

    await logger.log_kickoff(goal="Research causal logging for AI agents")
    result = await crew.kickoff_async()
    for task_output in result.tasks_output:                    # one causal node per task
        await logger.log_task(
            description=task_output.description,
            output=str(task_output.raw)[:2000],
        )
    await logger.log_output(str(result))

    # The payoff — explain WHY the crew produced its output:
    (await db.why(logger.last_event_id)).print()

db.why() reconstructs the chain:

crew_kickoff → crew_task (Researcher) → crew_task (Writer) → crew_output

Runnable example

A complete two-agent crew (Researcher → Writer) with the why() proof lives at examples/crewai-agent/. It targets a self-hosted ZizkaDB (http://localhost:8000) — no cloud signup required.

Monorepo dev install

pip install -e sdk/python -e integrations/crewai

License

zizkadb-crewai and zizkadb-sdk are licensed under AGPL-3.0.

Metadata

Release files for zizkadb-crewai 0.1.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zizkadb-crewai 0.1.4
File Size Uploaded Provenance
zizkadb_crewai-0.1.4.tar.gz 3.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for zizkadb-crewai 0.1.4
File Interpreter ABI Platform
zizkadb_crewai-0.1.4-py3-none-any.whl Python 3 none any Details

Total release size: 7.9 kB

Release files / zizkadb_crewai-0.1.4.tar.gz

Download URL zizkadb_crewai-0.1.4.tar.gz
Size 3.8 kB
Tags Source
SHA-256 checksum
How to use checksums
5561fd469a66a57de7a1180cea8537d53e8e53556be79368195719fceded321b
BLAKE2b-256 checksum
How to use checksums
b61108aa7a38f45d1559a5fe3718c25b5b6c80bd0f1e2677237070d70e7da056
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.9

Release files / zizkadb_crewai-0.1.4-py3-none-any.whl

Download URL zizkadb_crewai-0.1.4-py3-none-any.whl
Size 4.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5616502b9f9eec963f81ad3004e71a3e6c83eb1723f8ba09594eab09685afacc
BLAKE2b-256 checksum
How to use checksums
97de1adb00b25a2cbe399d7411a5265b1ffbc1026efebc69af62e92119ce52fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.9

Security for zizkadb-crewai 0.1.4

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page