MemFork
Git for agent state, in process: fork, merge, discard and rewind an agent's memory. Forking costs the same whatever memory holds, so an agent can branch before a risky step and throw the branch away if it goes wrong.
pip install memfork
One wheel, two things.
The engine, in your process
import memfork
db = memfork.Database()
db.put("plan:1", b"the original plan")
db.fork("attempt")
db.put("plan:1", b"a risky rewrite", branch="attempt")
db.get("plan:1").value # b'the original plan' — the fork is invisible here
db.merge("attempt") # or db.discard("attempt")
Branches are cheap because they share structure rather than copying. You can
also read memory as it was earlier: db.at("plan:1", seq).
The MCP server, for your agent clients
The same install puts the memfork command on your path:
memfork init # register the server with the MCP clients you have
memfork doctor # what is installed, and what is talking to it
Clients then get thirteen tools — store, recall, search, fork, merge, discard, time travel — over one store they share.
What is in memory and what is on disk
memfork.Database is in memory only. It does not write to disk, and it
does not see what an MCP client wrote: the durable, shared store belongs to the
MemFork daemon, which the memfork command starts when something needs it.
That split is deliberate — the engine is I/O-free by design — but it does mean a Python program that wants the shared memory talks to the server rather than importing it. Binding the durable store is later work.
More
Full documentation, the CLI reference and the design spec: https://github.com/memforkdb/memfork
Apache-2.0.
1 maintainer
Metadata
1 maintainer
Release files for memfork 0.1.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 | |
|---|---|---|---|
| memfork-0.1.1.tar.gz | 147.6 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| memfork-0.1.1-cp39-abi3-win_arm64.whl | CPython 3.9 | abi3 | Windows ARM64 | Details |
| memfork-0.1.1-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details |
| memfork-0.1.1-cp39-abi3-musllinux_1_2_x86_64.whl | CPython 3.9 | abi3 | Linux musl 1.2+ x86-64 | Details |
| memfork-0.1.1-cp39-abi3-musllinux_1_2_aarch64.whl | CPython 3.9 | abi3 | Linux musl 1.2+ ARM64 | Details |
| memfork-0.1.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| memfork-0.1.1-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| memfork-0.1.1-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
| memfork-0.1.1-cp39-abi3-macosx_10_12_x86_64.whl | CPython 3.9 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 31.0 MB
Release files / memfork-0.1.1.tar.gz
| Download URL | memfork-0.1.1.tar.gz |
|---|---|
| Size | 147.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2ab7a29a45663970ac0b5bab4debc04a045ace6e55b2ae3645071324859fa5b
|
|
BLAKE2b-256 checksum How to use checksums |
0eb0fec2faaa77a9e9d1df1a2ff9884a69ac1bc6fec2561a16113127374b90a9
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-win_arm64.whl
| Download URL | memfork-0.1.1-cp39-abi3-win_arm64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | CPython 3.9 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
3f11bb196216478106ebf42d92f142ad2baee027e7a5d0b52a17660e165d5bfa
|
|
BLAKE2b-256 checksum How to use checksums |
cbe380f58af28095ebb341a54dfefe0a2092543f3899243173aabc34eae4ba95
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-win_amd64.whl
| Download URL | memfork-0.1.1-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
a841bfd79b63b90970f4af33c65de958024fde9974f41d709899ab21aa839152
|
|
BLAKE2b-256 checksum How to use checksums |
f728cc3fb2105ae9e9a606d05ae7652e86ebf96191b8a7d7ab4f7c9e9155e9da
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-musllinux_1_2_x86_64.whl
| Download URL | memfork-0.1.1-cp39-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.9 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
04db4d1a12c58dab14379fed5c9376b9a3bb4b9de29bfe1f2d7c316d0180ac0d
|
|
BLAKE2b-256 checksum How to use checksums |
ff29df5cd6b1787522de899572dc987f26ef9d8a0b63ee10f10fc27a4c80ab08
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-musllinux_1_2_aarch64.whl
| Download URL | memfork-0.1.1-cp39-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 4.2 MB |
| Tags | CPython 3.9 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
129238394ae055de9cb1253cc415911c20282124078ecbd610d0243fa899bd4d
|
|
BLAKE2b-256 checksum How to use checksums |
d5b5154ce46a52ea4d73eff250bd8f602d914bfd52386a04e58555e97e1ee5f5
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | memfork-0.1.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 3.9 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
bb54701dc01cd938ed3c536a652d191ce0febcb85f710814990a5cfdd4af2fec
|
|
BLAKE2b-256 checksum How to use checksums |
a0cb65aa5a0745504768928daaa5932737113cc7ece587878e3652714cc5a300
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | memfork-0.1.1-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
ed956e3daeb7261e4f399791eb7a17c63bade487a5750fd8676d4b8813207613
|
|
BLAKE2b-256 checksum How to use checksums |
624e555a507f2accde4d2e45ce3794223f022dec8630a467159da3f4cfd1f0da
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | memfork-0.1.1-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
cbaaba174843b2270e05cde3047f080ea46aaf2f28d1439d3b11821c700611d3
|
|
BLAKE2b-256 checksum How to use checksums |
c32b2adac1ccc1cc12a88a28a4ab1e5c14d1816ec776d35e41070744ad8e8628
|
| 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 Sep 21, 2026.
Transparency logRelease files / memfork-0.1.1-cp39-abi3-macosx_10_12_x86_64.whl
| Download URL | memfork-0.1.1-cp39-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 3.7 MB |
| Tags | CPython 3.9 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
93fdcc656ba2e910d02c60d1913858174cd764e6aeafc905605b724253442ccf
|
|
BLAKE2b-256 checksum How to use checksums |
e5d373a533c5ea24b19f143ca1e8d6369b19008302e978bb0883ea167a37f251
|
| 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 Sep 21, 2026.
Transparency log
