1 of 2 files were uploaded without provenance metadata. View details.
processfork-crewai
ProcessFork memory adapter for CrewAI ≥0.130.
Replaces CrewAI's stock CrewMemory with a ProcessFork-backed
implementation; every crew step becomes a .pfimg you can time-travel
through.
Install
pip install "processfork-crewai[crewai]"
Use
from crewai import Crew
from processfork_crewai import ProcessForkMemory
crew = Crew(
agents=[researcher, writer, editor],
memory=ProcessForkMemory(store="~/.processfork", crew_id="ml-blogpost"),
tasks=[...],
)
result = crew.kickoff()
# Time-travel:
crew.memory.checkout("sha256:...pre-edit")
Captures:
- All three agents' message histories into the trace blob.
- Tool-call ledgers (web-search, file-write, etc.).
- The
output_files/directory each task writes to (world.fs).
See agent_docs/integration-crewai.md for the spec.
Metadata
Release files for processfork-crewai 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Incomplete provenance
1 of 2 files were uploaded without provenance metadata.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| processfork_crewai-1.0.0.tar.gz | 3.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| processfork_crewai-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.8 kB
Release files / processfork_crewai-1.0.0.tar.gz
Incomplete provenance
This file belongs to a release with incomplete provenance: while this file has provenance metadata, other files in this release do not.
We recommend further investigation before installing this file. View details.
| Download URL | processfork_crewai-1.0.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc9dcebe8d90cf488bd3cbb8c1f278909c7daa188826c657daba08341a5cbfc1
|
|
BLAKE2b-256 checksum How to use checksums |
52274d5c75e3e70dae1868b0caff09c8d6ef6f1f6dd2afb262ac2ba405f645b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 6, 2026.
Transparency logRelease files / processfork_crewai-1.0.0-py3-none-any.whl
Incomplete provenance
This file belongs to a release with incomplete provenance: while other files in this release have provenance metadata, this file does not.
We recommend further investigation before installing this file. View details.
| Download URL | processfork_crewai-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71561a8a154ae680e7409561aa7f290da577a41c8036673667cf636d6e2e58cb
|
|
BLAKE2b-256 checksum How to use checksums |
647f1f81e993af1e5e1148245a30c782b15aea2be12c2acc44953a955a535ace
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for processfork-crewai 1.0.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.
Incomplete provenance
1 of 2 files were uploaded without provenance metadata.
Attestation for processfork_crewai-1.0.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 May 6, 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.