Pre-release

This release is a pre-release and may not be stable for production use.

yadgar — the client

One binary. yaadgaar login obtains a credential, yaadgaar serve is the MCP server your agent spawns, and everything else manages the machine it runs on (D75, D76).

The command is yaadgaar, and the doubled vowels are not a typo. The Python client this replaces already owns yadgar on PATH, so the transitional client differs in both the PyPI project and the executable — the reasoning is written over BINARY_NAME in src/install/hooks.rs.

Decisions are recorded in yadgarhq/docs — D75 (the proxy that knows no tools), D76 (one binary, and a rules file that is referenced rather than spliced), D72 (the credential), D16 (why the gateway is the only thing that speaks MCP inward).

What it is

A proxy, and deliberately nothing more. tools/list is forwarded to the gateway and its answer returned verbatim; so is tools/call. There is no per-tool code in this repository at all — not a match arm, not a registry, not a feature flag.

That is the boundary rather than an economy. A list the client asserts is a list the client is trusted to filter honestly; forwarding makes the gateway's answer the only answer, and the gateway resolves identity before it replies. It is also what keeps releases uncoupled: this binary lives on people's laptops and the gateway does not, so a client that enumerated tools would make the tool set move at the speed of the slowest machine.

When the gateway is unreachable at spawn, the last tool list is served from cache and calls fail with a plain "gateway unreachable" — because an empty list is indistinguishable from yadgar not being installed, and the agent would silently lose memory and tasks with nothing to report.

Commands

Command What it does
yaadgaar login Asks for the gateway address and your credentials once and stores both together. It registers nothing — install owns every file the agent client reads.
yaadgaar serve The stdio MCP server the agent spawns. Not run by hand.
yaadgaar install Registers the hooks, the rules reference and the MCP entry, in the agent client's user-level config — once per machine, never per repository.
yaadgaar uninstall Removes what install added, and nothing else.
yaadgaar verify Reports drift in the installed environment. Scheduled, not remembered — the daemon cannot see ~/.claude/settings.json, so nothing server-side can ever notice.
yaadgaar hook <event> What settings.json invokes. A hook is a dispatch, not a program.

login then install is the whole setup, and verify is the one to schedule. project_id is derived from the working directory at call time (D53), so one registration serves every repository and a fresh checkout works immediately.

Installing

pip install --no-cache-dir yaadgaar
yaadgaar login
yaadgaar install

To upgrade, the same line with --upgrade:

pip install --no-cache-dir --upgrade yaadgaar

--no-cache-dir is not optional while the only releases are prereleases, and it is the whole of the problem. pip caches the simple-index page it fetched for a project. A machine that has resolved yaadgaar once keeps serving itself that page and cannot see anything published since — so an upgrade reports success against a version that is already stale, rather than failing.

Measured on a fresh Debian VM with 0.1.0a2 already on PyPI. The VM's own curl of the simple index showed all six a2 wheels at the same moment pip insisted only a1 existed:

Command What it did
pipx upgrade yaadgaar "already at latest version 0.1.0a1"
pipx install --force --pip-args=--pre yaadgaar installed a1 again
pipx install --force yaadgaar==0.1.0a2 "Could not find a version that satisfies the requirement"
pip install --no-cache-dir yaadgaar==0.1.0a2 worked, first try

Every row is the same cache. The third one is worth reading twice: an EXACT version that PyPI was serving at that moment came back as no such version, which is what a stale index page looks like from the inside.

No --pre and no version pin are needed, and this is measured rather than reasoned — a bare pip download --no-deps --no-cache-dir yaadgaar against a fresh index fetches 0.1.0a2, and pip install --no-cache-dir --upgrade --dry-run yaadgaar resolves to Would install yaadgaar-0.1.0a2. PEP 440 falls back to prereleases when a requirement matches nothing else, so pinning would only fix this README to a version that goes stale on the next release. --pre widens a requirement and does not refetch anything, which is why it changed nothing on the VM.

One command does NOT take that fallback: pip index versions yaadgaar reports "No matching distribution found" while pip index versions --pre yaadgaar lists both. It is a diagnostic, not an install, and it is the one place --pre earns its keep here.

Once a stable release exists, all of this goes away and pipx install yaadgaar / pipx upgrade yaadgaar are the lines. Until then pipx's own upgrade path is the one measured failing above; the pipx equivalent, pipx install --force --pip-args="--no-cache-dir" yaadgaar, is untested — the pip lines are the ones that were actually run.

Rust, shipped to PyPI as wheels via maturin. The language follows the rest of the system; the channel follows the people already using it, and a pip-installable command is not a thing a rewrite gets to take away. A plain GitHub-release binary was rejected for exactly that reason.

The wheel carries the compiled binary and no Python at all — bindings = "bin" in pyproject.toml — so import yaadgaar is not a thing and is not meant to be.

A wheel is per-platform, so there are six: Linux, macOS and Windows, each on x86_64 and aarch64. Every one is built on a runner of its own architecture rather than cross-compiled, and release.yaml refuses to publish unless all six are present — shipping the four that built would leave two platforms silently installing an older version.

Development

cargo build
cargo test
pre-commit run --all-files

There is no Containerfile and no chart here: this repository is not a service, and what it ships is a wheel. CI is the shared workflow in yadgarhq/actions, which detects that and skips the image, chart and proto stages (D62).

To build a wheel locally:

maturin build --release   # → target/wheels/, for THIS machine only

The other five targets are built by .github/workflows/release.yaml, which is this repository's one piece of local CI. The reason it is not in yadgarhq/actions with everything else is written at the top of that file.

Project links

Data verified by PyPI on Sep 1, 2026
Data provided by the project maintainers, verified at the time the release was uploaded to PyPI.

Key dates

PyPI data
Data sourced directly from PyPI's database.
  • Released:
Newer release available (0.1.0a7)

1 maintainer

PyPI data
Data sourced directly from PyPI's database.
Avatar for maxagahi from gravatar.com maxagahi

GitHub Statistics

Data verified by PyPI on Sep 1, 2026
The GitHub source repository was provided by the project maintainers and verified by PyPI at the time of upload. Stars, forks, and open issues/PRs are derived from that repository and have not been independently verified.

License expression

Apache-2.0
View SPDX License List

Requires

Python >=3.9

Tags

mcp agent memory yadgar

Classifiers

Report project as malware

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

yaadgaar-0.1.0a5-py3-none-win_arm64.whl (3.2 MB view details)

Uploaded Python 3Windows ARM64

yaadgaar-0.1.0a5-py3-none-win_amd64.whl (3.2 MB view details)

Uploaded Python 3Windows x86-64

yaadgaar-0.1.0a5-py3-none-manylinux_2_28_aarch64.whl (3.3 MB view details)

Uploaded Python 3manylinux: glibc 2.28+ ARM64

yaadgaar-0.1.0a5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.6 MB view details)

Uploaded Python 3manylinux: glibc 2.17+ x86-64

yaadgaar-0.1.0a5-py3-none-macosx_11_0_arm64.whl (3.3 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

yaadgaar-0.1.0a5-py3-none-macosx_10_12_x86_64.whl (3.5 MB view details)

Uploaded Python 3macOS 10.12+ x86-64

File details

Details for the file yaadgaar-0.1.0a5-py3-none-win_arm64.whl.

File metadata

  • Download URL: yaadgaar-0.1.0a5-py3-none-win_arm64.whl
  • Upload date:
  • Size: 3.2 MB
  • Tags: Python 3, Windows ARM64
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for yaadgaar-0.1.0a5-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 9b7facfef914c188354dcfa38941941dce960c01651d95e8b960f7b1703d9d85
MD5 d25d43903105f117c065dde336ce87ed
BLAKE2b-256 017a1d1d3b2bb4d066c2af34ddb6b13c33480e860932fb5f4e2638db49ce9b28

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a5-py3-none-win_arm64.whl:

Publisher: release.yaml on yadgarhq/yadgar

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file yaadgaar-0.1.0a5-py3-none-win_amd64.whl.

File metadata

  • Download URL: yaadgaar-0.1.0a5-py3-none-win_amd64.whl
  • Upload date:
  • Size: 3.2 MB
  • Tags: Python 3, Windows x86-64
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for yaadgaar-0.1.0a5-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 d95fd81e86a1ec73d77d27b811d06e7416c27b93e03ac0c560796f87b6300d38
MD5 2d8fa501de0a730df4dedd92818144e7
BLAKE2b-256 e8875feb9806cae40e48882d20ed0d2bb53c60b2f754a29854d16916fbcd8bae

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a5-py3-none-win_amd64.whl:

Publisher: release.yaml on yadgarhq/yadgar

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file yaadgaar-0.1.0a5-py3-none-manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a5-py3-none-manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 0a12cf163c5e56613d7167b624b63feba78a9b4b15b8550800e4eb5d3e912c05
MD5 5829234dc5f7f10eae70876eac175322
BLAKE2b-256 1016e75c9d0f6cf1bf63926bc144f07d5b9f022cde7d55f3f0c587f0ae3110b9

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a5-py3-none-manylinux_2_28_aarch64.whl:

Publisher: release.yaml on yadgarhq/yadgar

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file yaadgaar-0.1.0a5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 52383e8a28a5f8a4522c20aa19b4f47a231fc320ab093aa79510b110c2a55c18
MD5 200157ad272956b39954fffbdfd6716c
BLAKE2b-256 73c78625678435f90b6390e9be90d8cef347584be03c4d40bc439fe06abd0f33

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl:

Publisher: release.yaml on yadgarhq/yadgar

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file yaadgaar-0.1.0a5-py3-none-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a5-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 5f8775ca40b5dc0181f1546d5406fd066149cf5bdbd03a786ab217655e2780c6
MD5 9c70e34a9749d16f756c91c10591a7d8
BLAKE2b-256 0b852fa5dc8ace73761f23c635362acbb213dc202712c9834d6776f412194ae9

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a5-py3-none-macosx_11_0_arm64.whl:

Publisher: release.yaml on yadgarhq/yadgar

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file yaadgaar-0.1.0a5-py3-none-macosx_10_12_x86_64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a5-py3-none-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 11bf8fcc83e9c35ddcae7cb37b4ae42abde9bf03d301e081eb170f08270940c1
MD5 596f91b5ebb365fecb2ca9115565cc05
BLAKE2b-256 8725b8e1dd703438766052a5bf28a20f8072d751b1c7a56c31ec44b0a8d49940

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a5-py3-none-macosx_10_12_x86_64.whl:

Publisher: release.yaml on yadgarhq/yadgar

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.
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