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.0a4-py3-none-win_arm64.whl (3.2 MB view details)

Uploaded Python 3Windows ARM64

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

Uploaded Python 3Windows x86-64

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

Uploaded Python 3manylinux: glibc 2.28+ ARM64

yaadgaar-0.1.0a4-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.0a4-py3-none-macosx_11_0_arm64.whl (3.3 MB view details)

Uploaded Python 3macOS 11.0+ ARM64

yaadgaar-0.1.0a4-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.0a4-py3-none-win_arm64.whl.

File metadata

  • Download URL: yaadgaar-0.1.0a4-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.0a4-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 88081472ebfe2ed1d1f76a1404bb1d8d7498552c0753db17d65018439d1c534a
MD5 33d35f8dafe4052def9373a5ca6253ff
BLAKE2b-256 c52d2a4435ca82538a0cf1c39812d118ff7ebddb639e2abc788d1040d4dbce18

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a4-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.0a4-py3-none-win_amd64.whl.

File metadata

  • Download URL: yaadgaar-0.1.0a4-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.0a4-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 6da985959d8c885aca37c6a485fe08f07299a28c2c98a9d1e14aaae4ac7fcd02
MD5 b2b7a620be264e3f8f7a166574c2cea3
BLAKE2b-256 fd56a7afbd2dc0759a737221a06c4a735bd2b151c617b75df0a375ea6cbac52c

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a4-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.0a4-py3-none-manylinux_2_28_aarch64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a4-py3-none-manylinux_2_28_aarch64.whl
Algorithm Hash digest
SHA256 e3f6e89ec3bf6595e93850c51049659653d00957e6d8ebe0514b8757f5664982
MD5 2f2e5c13dce70253bf878b1d07c57754
BLAKE2b-256 7140bd5bbd0add8a082cd7bfe63a489368fe32f50d45eb15fc29fd41a5be58f3

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a4-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.0a4-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a4-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Algorithm Hash digest
SHA256 031883bdd13ae8833b27dc4fd5993689580c438d539c69da17aa3d279f708f28
MD5 a2d9516738f64a628af55fdabab4dc76
BLAKE2b-256 955a488d4b01a88e8e1dd6969eda7f5537d079930312ab7998b7834b82180a22

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a4-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.0a4-py3-none-macosx_11_0_arm64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a4-py3-none-macosx_11_0_arm64.whl
Algorithm Hash digest
SHA256 c4eb964900fcc65350269de68f551fdf5430ac428ee8c53f74193dfe85f03609
MD5 8e6b5b17f35883e9d8e1b20855ccbef1
BLAKE2b-256 5a4d4458a055cb4e8c33f67f78aa508aa65486ba06785a90c0de0b5d081ff72f

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a4-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.0a4-py3-none-macosx_10_12_x86_64.whl.

File metadata

File hashes

Hashes for yaadgaar-0.1.0a4-py3-none-macosx_10_12_x86_64.whl
Algorithm Hash digest
SHA256 f30759115b4a05fa65a98ecae1e9949def35c0dde8d7614030dc0a193b9116d7
MD5 585a38c886ce565eba2729ce283f4ca7
BLAKE2b-256 f685beaf97548d59c0b328b29d0bdf237152b56c237883b58b40c970a195e497

See more details on using hashes here.

Provenance

The following attestation bundles were made for yaadgaar-0.1.0a4-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