jpit (v4.4.7)
The developer and AI agent companion CLI for jsonpit — daemon-free distributed storage over Cloud Drives.
100% lockstep parity with C# JsonPit in RAIkeep.
jpit provides high-performance semantic living state search ("Pit-Grep"), time-travel inspection, and cloud-safe distributed ingestion across replicated JsonPits on OneDrive, Dropbox, and Google Drive.
Installation & Upgrade
Recommended: Global CLI via pipx (Isolated)
Install jpit in an isolated environment without dependency conflicts across your system:
# Install jpit globally
pipx install jpit
# Upgrade to latest lockstep release (v4.4.7)
pipx upgrade jpit
In a Project / Virtual Environment via pip
# Install
pip install jpit
# Upgrade
pip install --upgrade jpit
Upgrading with Multi-Python / pyenv Environments
If you have multiple Python versions (e.g. 3.12, 3.13, 3.14):
-
Anchor
pipto your active interpreter:python -m pip install --upgrade jpit
(Prevents installing into the wrong Python version if bare
pippoints to an older runtime). -
If using
pyenv, regenerate shims:pyenv rehashEnsures
which jpitpoints to~/.pyenv/shims/jpit, dynamically delegating to your active shell Python. -
Verify:
which jpit jpit --version
(Installing jpit automatically installs the jsonpit core storage engine and provisions both jpit and jsonpit command-line executables).
CLI Usage
# Fast semantic search across one or all pits ("Pit-Grep"):
jpit grep "Adele" Person
jpit grep "Burkhardt" --root AIA
# Pipe search results directly into jq:
jpit grep "Jazz" Person --json | jq '.[].Genre'
# Inspect entity living state or full immutable history:
jpit get Person Rainer
jpit history Person Rainer
# Pipe JSON5 / JSON mutations directly into a pit:
cat update.json5 | jpit put Person
echo '{Id: "AlanKay", Dynabook: true}' | jpit put Person
# Ingest single entity, keyed map, or array from file (CR043):
jpit seed Activity -s PerformLive.json5
# Set individual properties or tombstone an entity:
jpit set Person AlanKay '{"Status": "Visionary"}'
jpit del Person ObsoleteEntity
# Automated maintenance and dead flag pruning (100% C# pits maintain parity):
jpit maintain Activity -c OneDrive -r AIA
jpit maintain Activity -c OneDrive -r AIA --apply --prune-process-flags --older-than 01:00:00 --json
jpit maintain --wwwa -c OneDrive -r AIA --apply --prune-process-flags --older-than 7.00:00:00
# Read-only audit of durable recovery events (100% C# pits audit parity):
jpit audit Activity -c OneDrive -r AIA
jpit audit Activity -c OneDrive -r AIA --machine local --level Warning
jpit audit --wwwa -c OneDrive -r AIA --json
Core Engine & Documentation
For complete Python library documentation, distributed lease protocols, and multi-agent coordination architecture, visit:
👉 jsonpit on GitHub · API Reference (API.md) · jsonpit on PyPI
Metadata
Release files for jpit 4.4.7
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 |
|---|---|---|---|---|
| jpit-4.4.7.tar.gz | 2.8 kB | Without provenance | Details for jpit-4.4.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jpit-4.4.7-py3-none-any.whl | Python 3 | none | any | Details for jpit-4.4.7-py3-none-any.whl |
Total release size: 5.9 kB
Release files / jpit-4.4.7.tar.gz
| Download URL | jpit-4.4.7.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9fd4f86abee3a5e6fdfacf52c3113358d8a5ef45a63814f0ec0055686317f01
|
|
BLAKE2b-256 checksum How to use checksums |
2790b6844bb5fbf4dbcc39a1210685d77390563dfafe4bcef7542d4d5df150cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / jpit-4.4.7-py3-none-any.whl
| Download URL | jpit-4.4.7-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc6371e330a5e048ff17613a79bea7f5df7aeb6e5e849463d7ef26c58ae16b29
|
|
BLAKE2b-256 checksum How to use checksums |
f9c7e40870fe6a54eebb5eac7311358419ddfa2c4f4859851591c6dc01e53227
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for jpit 4.4.7
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.