Buddie — AI Agent Reliability Toolkit
Verify the claim. Know the context.
Buddie checks agent reports against primary evidence with deterministic Core verification, actionable feedback, and permission-controlled local environment diagnostics.
Install: pip install buddie==2.0.4.
Repository | Privacy | Release notes
Buddie 2.0.4
2026-10-29
Buddie — AI Agent Reliability Toolkit: canonical Discovery, README-style branding, Linux worker guard hardening and Stop-hook corrections without duplicate answers.
Changes
- The compact Claude plugin includes the canonical Buddie Discovery skill and reporting reference, read from the release commit and relocated without changing their bytes.
- Discovery distinguishes real Core verification, independent evidence triage with authorized tools, and unverified claims when relevant tools are unavailable.
- Public manifests and generated package descriptions adopt the AI Agent Reliability Toolkit positioning and the existing Verify the claim. Know the context. tagline.
- The plugin and Desktop bundle use the previously created white-dog icon with cyan accents matching the README artwork.
- Packaging rejects missing Discovery dependencies and competing destination paths, including case variants on Windows.
- On Linux, regex workers refuse to proceed if registering the parent-death signal fails or if the expected parent has already ended. The liveness test handles a process disappearing during the /proc read and retains diagnostics and cleanup.
- At Stop, failed verification now asks for corrected lines instead of repeating the full answer that is already displayed. PreToolUse delivery checks retain their existing behavior.
- Ready pull requests automatically run full validation. CI runs the main suite in parallel and the timing-sensitive worker tests separately, with pip caching.
Upgrade
Install buddie==2.0.4 or use the matching approved plugin or Desktop bundle. This release replaces the unpublished 2.0.3 candidate and includes merged PR77. Standalone Discovery retains version 0.1.0. Published 2.0.2 artifacts and the immutable 2.0.3 candidate remain unchanged.
Permissions
No new Core runtime permissions are required. Discovery uses only tools and evidence already authorized in the host session; optional Core diagnostics retain existing permission grants. No automatic installation or credential access is added.
Security
Linux regex workers now fail closed when their parent-death guard cannot be established. The candidate binds archives, public metadata and canonical Discovery sources to the source revision and SHA-256 digests. Issue73 was closed at the owner’s request after PR77; the historical intermittent failure’s precise root cause remains unproven. Report vulnerabilities through SECURITY.md.
Limitations
Discovery is an instruction skill, not an executable verifier. Automatic hooks and local MCP vary by client; actual Cowork, Claude Chat and mobile behavior is not certified by package validation. Projects/Context, hosted remote MCP and image-understanding tools are not introduced. Agensi submission is pending review, not approved.
Metadata
Release files for buddie 2.0.4
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 |
|---|---|---|---|---|
| buddie-2.0.4.tar.gz | 280.1 kB | With provenance | Details for buddie-2.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| buddie-2.0.4-py3-none-any.whl | Python 3 | none | any | Details for buddie-2.0.4-py3-none-any.whl |
Total release size: 584.8 kB
Release files / buddie-2.0.4.tar.gz
| Download URL | buddie-2.0.4.tar.gz |
|---|---|
| Size | 280.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4cc0a844105ab282dc732fef5efd6148f227ef9261ba6d60f00c073ad2dbad15
|
|
BLAKE2b-256 checksum How to use checksums |
b42a9d518d0d56d183122cecf3a6f1d084f4725d8ec32be0a0a313cc3ff1b807
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 29, 2026.
Transparency logRelease files / buddie-2.0.4-py3-none-any.whl
| Download URL | buddie-2.0.4-py3-none-any.whl |
|---|---|
| Size | 304.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9350f5cffb1c7d49b6a6a45537e33200783f85c1187900f34d163fa3da99315
|
|
BLAKE2b-256 checksum How to use checksums |
19756ee2cbb55428177a5535770e940d12d1f07969449281a06526d0f42fc6f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 29, 2026.
Transparency logSecurity for buddie 2.0.4
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for buddie-2.0.4.tar.gz
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 29, 2026.
Transparency logA 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.