mezhar
Genie agents as code, for Databricks. Each agent (a Genie space over metric views) is a folder of files in a git repository: the view, the instructions, the test questions with known correct answers, and who may use it. Every pull request deploys the agent to dev and grades it against those questions; every environment is graded again each night; the questions real users ask are collected for an analyst to decide. Changes reach prod through an approved merge.
A project pins one line, mezhar==<version>. Its pipeline runs mezhar deploy -t <target>: check the files, deploy the bundle,
set up the engine's tables and the Genie spaces, import the test sets, grade. A weekly pipeline opens the upgrade PR, already graded
on dev, with the release notes as its description.
uv pip install mezhar
mezhar help
A project starts from the mezhar Databricks bundle template. Its manual ships inside the project as a skill
(.agents/skills/mezhar/SKILL.md, with mezhar-review for analysts) and is rewritten by mezhar upgrade for every engine version.
Licence: PolyForm Internal Use 1.0.0 — use it for your own company's internal business, no distribution. Source is not public.
1 maintainer
Metadata
1 maintainer
Release files for mezhar 0.11.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mezhar-0.11.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / mezhar-0.11.2-py3-none-any.whl
| Download URL | mezhar-0.11.2-py3-none-any.whl |
|---|---|
| Size | 195.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
722c26dddc3a9c6ecf6ab645acc28d7ddfa1d7ae490d8a2e29839e046a74cc50
|
|
BLAKE2b-256 checksum How to use checksums |
a60f7fd1f1c4b27ec833bee70c01cb07b5a6e1fcd97d43475764d5899fb48cdb
|
| 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 Oct 5, 2026.
Transparency log
