processfork-autogen
ProcessFork integration for AutoGen
0.4+. Wraps a RuntimeContext so a whole agent group's state can be
snapshotted and forked atomically.
Install
pip install "processfork-autogen[autogen]"
Use
from processfork_autogen import processfork_runtime
from autogen_agentchat.teams import RoundRobinGroupChat
team = RoundRobinGroupChat(
[alice, bob],
runtime=processfork_runtime("~/.processfork"),
)
await team.run(task="...")
# Snapshot the whole team:
cid = await team.runtime.snapshot("pre-vote")
forks = await team.runtime.fork(cid, n=4)
The runtime tracks each agent's message history under one trace blob plus per-agent partitions in the effects ledger. Snapshots are atomic across the team (no agent's state can advance mid-snapshot).
See agent_docs/integration-autogen.md for the spec.
1 maintainer
Metadata
1 maintainer
Release files for processfork-autogen 1.0.1
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 | |
|---|---|---|---|---|
| processfork_autogen-1.0.1.tar.gz | 4.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| processfork_autogen-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.3 kB
Release files / processfork_autogen-1.0.1.tar.gz
| Download URL | processfork_autogen-1.0.1.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24de226f5a397537c083f71192f750f30019a4ca259fcfb535079366837d8047
|
|
BLAKE2b-256 checksum How to use checksums |
5ce45710e09006ad96355507ac68961227fa445d418f4d4eb7fa2f272b21c169
|
| 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_autogen-1.0.1-py3-none-any.whl
| Download URL | processfork_autogen-1.0.1-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a262e07587f6d93511e48a5aa5a35cc9e3a21f9b357e88084adcf271fa7168df
|
|
BLAKE2b-256 checksum How to use checksums |
6835f024b7bbae7a6b338da63c9ff07ad54860c3b5ebb6470fc8e1eb6cd38997
|
| 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 logSecurity for processfork-autogen 1.0.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for processfork_autogen-1.0.1.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.
