Skip to main content

jpit (v4.5.1)

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

Install jpit in an isolated environment without dependency conflicts across your system:

# Install jpit globally
pipx install jpit

# Upgrade to latest lockstep release (v4.5.1)
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):

  1. Anchor pip to your active interpreter:

    python -m pip install --upgrade jpit
    

    (Prevents installing into the wrong Python version if bare pip points to an older runtime).

  2. If using pyenv, regenerate shims:

    pyenv rehash
    

    Ensures which jpit points to ~/.pyenv/shims/jpit, dynamically delegating to your active shell Python.

  3. 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.5.1

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

Source distribution (sdist)

Source distribution for jpit 4.5.1
File Size Uploaded Provenance Actions
jpit-4.5.1.tar.gz 2.8 kB Without provenance Details for jpit-4.5.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for jpit 4.5.1
File Interpreter ABI Platform Actions
jpit-4.5.1-py3-none-any.whl Python 3 none any Details for jpit-4.5.1-py3-none-any.whl

Total release size: 5.9 kB

Release files / jpit-4.5.1.tar.gz

Download URL jpit-4.5.1.tar.gz
Size 2.8 kB
Tags Source
SHA-256 checksum
How to use checksums
58c2779384b43019d96339ab6346343ae105fd9deffafd2370b03f9466788ad5
BLAKE2b-256 checksum
How to use checksums
4c695cf780a54a66977d946a4e289e2de7403b415aaad4fc949eaffe3ba566ec
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.5.1-py3-none-any.whl

Download URL jpit-4.5.1-py3-none-any.whl
Size 3.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
30598d2049d0ff586d407199c626dc65b36a4351ca0130b6e03b2f509859ca62
BLAKE2b-256 checksum
How to use checksums
234807e5ac1ade0c6144146d39ef7302353099a79985581b77825478def355bc
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.5.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.

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