AgentMesh
Local-first multi-agent coordination and provenance for coding workflows.
AgentMesh adds deterministic coordination (claims, waits, steals), commit-linked lineage (AgentMesh-Episode trailers + weave events), and portable handoff bundles (.meshpack) on top of normal git workflows.
Install
pipx install agentmesh-core # recommended (isolated)
# or
pip install agentmesh-core
# optional: commit witness signing (Ed25519)
pipx install "agentmesh-core[witness]"
Quick Start
cd your-repo
agentmesh init --install-hooks # set up mesh + Claude Code hooks
agentmesh doctor # verify everything is wired correctly
agentmesh task start --title "Fix login timeout" \
--claim src/auth.py --claim tests/test_auth.py
# edit + stage as normal
git add src/auth.py tests/test_auth.py
agentmesh task finish --message "Fix login timeout handling" \
--run-tests "pytest -q tests/test_auth.py"
# ^ commits with AgentMesh-Episode trailer, emits capsule, releases claims
How It Works
When multiple AI agents (or humans) work in the same repo, AgentMesh prevents chaos:
- Claims: agents lock files/ports/resources before editing. Conflicts are blocked, not merged.
- Episodes: every work session gets a unique ID (
ep_...) that binds claims, capsules, and commits. - Capsules: structured context bundles (SBAR format) for zero-ramp-up handoffs between agents.
- Weaver: hash-chained provenance linking capsules to git commits. Every change is traceable.
- Commit trailers:
agentmesh commitinjectsAgentMesh-Episode:by default, and can attach signed witness trailers (AgentMesh-KeyID,AgentMesh-Witness,AgentMesh-Sig+ portable witness payload chunks) when witness support + keys are present.
Optional Witness Signing
If installed with agentmesh-core[witness], you can sign commit witnesses locally:
agentmesh key generate
agentmesh commit -m "Fix timeout handling"
agentmesh witness verify HEAD
Witness verification is portable: the signed witness payload is embedded in commit trailers, so CI and other machines can verify without local sidecar state.
CI Integration
Add agentmesh-action to check lineage coverage on PRs:
# .github/workflows/lineage.yml
name: Lineage Check
on: [pull_request]
permissions:
contents: read
pull-requests: write
jobs:
lineage:
runs-on: ubuntu-latest
steps:
- uses: Haserjian/agentmesh-action@v1
The action posts a sticky PR comment showing commit coverage. Set require-trailers: "true" to enforce episode lineage, and verify-witness: "true" + require-witness: "true" to enforce cryptographic witness verification.
Documentation Policy
- Public/private split guidance:
docs/public-private-boundary.md - Decision matrix + release gate:
docs/public-private-decision-matrix.md - Alpha gate operator runbook:
docs/alpha-gate-runbook.md - License transition policy:
docs/license-policy.md
Generated canary artifacts (CI logs, raw gate reports) should be treated as private by default. Publish sanitized summaries/templates for OSS.
Use the classifier before publishing:
agentmesh classify --staged --fail-on-private --fail-on-review
Release preflight (deterministic gate for agents/automation):
agentmesh release-check --staged --require-witness --json
Sanitize private alpha gate artifacts before publishing:
agentmesh sanitize-alpha-gate-report \
--in .agentmesh/runs/alpha-gate-report.json \
--out docs/alpha-gate-report.public.json
CI rollout recommendation:
- Start with non-blocking
release-checkpreview artifacts. - Keep private-artifact blocking enabled.
- Switch
release-checkto blocking after policy tuning.
License
AgentMesh is licensed under Apache-2.0 for current and future development.
Published releases up to and including v0.7.0 remain under MIT as originally released.
Metadata
Release files for agentmesh-core 0.9.0
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 |
|---|---|---|---|---|
| agentmesh_core-0.9.0.tar.gz | 180.4 kB | With provenance | Details for agentmesh_core-0.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentmesh_core-0.9.0-py3-none-any.whl | Python 3 | none | any | Details for agentmesh_core-0.9.0-py3-none-any.whl |
Total release size: 271.6 kB
Release files / agentmesh_core-0.9.0.tar.gz
| Download URL | agentmesh_core-0.9.0.tar.gz |
|---|---|
| Size | 180.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9305900bfb3113cd47b8a1661a6e8efad050bdbe04dc8f3600e721a462a72e1d
|
|
BLAKE2b-256 checksum How to use checksums |
0cdcd9984009c9e5d6120635906e990d4aa542c807728fac6703b66a6e8778ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 25, 2026.
Transparency logRelease files / agentmesh_core-0.9.0-py3-none-any.whl
| Download URL | agentmesh_core-0.9.0-py3-none-any.whl |
|---|---|
| Size | 91.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
519a2fa94787158632d20fbeff15150f992c689dddd442cee6876dcd652ad5ed
|
|
BLAKE2b-256 checksum How to use checksums |
22ddf25757a17409f6fb5edb574c8ba770167f1d944d1cf4612834c0f8ee7fac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 25, 2026.
Transparency logSecurity for agentmesh-core 0.9.0
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 agentmesh_core-0.9.0.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 Feb 25, 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.