LeafMesh — Multi-Agent AI Orchestration Platform
YAML-native multi-agent AI platform with self-healing and evolutionary capabilities
LeafMesh transforms multi-agent AI development through declarative YAML configuration that becomes executable intelligence. Built on the MANAGED_MESH architecture with production-ready coordination and persistence.
Core Features
- YAML-Native Intelligence - Zero-code agent creation with AST-parsed configuration
- Built-in Coordination - Manager and Summarizer agents provide automatic oversight
- MANAGED_MESH Architecture - Direct agent communication with conditional routing
- Redis-Powered Persistence - Automatic session management and conversation history
- Enterprise Tool Ecosystem - 15+ built-in tools with OpenAI-compatible function calling
- Advanced Parallel Processing - Multi-session threading with intelligent coordination
Production Features
- Self-Healing Networks - 6 autonomous healing actions with failure detection
- Evolutionary Optimization - Genetic algorithms with real fitness testing
- Adaptive Model Intelligence - ML-powered model selection with performance prediction
Quick Start
1. Installation
pip install leafmesh
2. Environment Setup
# Required: OpenAI API key
export OPENAI_API_KEY="your-openai-key"
# Optional: Additional providers
export ANTHROPIC_API_KEY="your-anthropic-key"
export GOOGLE_API_KEY="your-google-key"
3. Redis Setup
Local Redis:
# macOS
brew install redis && brew services start redis
# Ubuntu/Debian
sudo apt install redis-server && sudo systemctl start redis
# Docker
docker run -d -p 6379:6379 redis:alpine
4. Basic Usage
from leafmesh import LeafMesh
# Initialize from YAML configuration
sdk = LeafMesh.from_yaml("config.yaml")
# Start the mesh
await sdk.start()
# Process requests
response = await sdk.process_request(
session_id="user_session",
input_data={"message": "Hello, how can you help me?"}
)
print(response)
Example YAML Configuration:
name: "my_mesh"
architecture: "managed_mesh"
# Built-in coordination
manager:
enabled: true
model: "gpt-4o"
summarizer:
enabled: true
model: "gpt-4o-mini"
# User-defined agents
agents:
conversation_agent:
name: "conversation_agent"
model: "gpt-4o-mini"
prompt: "You are a helpful AI assistant."
yields:
response: "string"
confidence: "number"
tools: ["calculator", "current_time"]
Architecture Overview
LeafMesh implements a MANAGED_MESH architecture with:
- LLM Agents - YAML-defined with optional Python enhancement
- Manager Agent - Built-in coordination and rule enforcement
- Summarizer Agent - Omnipresent monitoring and analysis
- Redis Persistence - Automatic session and conversation storage
- Event System - All communication flows through events
- Tool System - OpenAI-compatible function calling
For detailed architecture information, see docs/ARCHITECTURE.md
Agent Enhancement
Add Python logic to YAML-defined agents:
@sdk.intelligence("conversation_agent")
async def enhance_conversation(llm_response, input_data, context):
"""Add business logic to agent responses"""
# Access conversation history
history = context.get("conversation_history", [])
# Enhance the LLM response
enhanced_response = add_context(llm_response, history)
# Trigger other agents conditionally
if needs_specialist(enhanced_response):
await sdk.trigger_agents(data={"analysis": enhanced_response})
return {
"response": enhanced_response,
"confidence": calculate_confidence(enhanced_response)
}
Revolutionary Features
Self-Healing Networks
# Enable automatic failure recovery
await sdk.enable_self_healing()
# Monitor agent health
health = await sdk.get_agent_health_status()
stats = await sdk.get_healing_statistics()
Evolutionary Optimization
# Optimize mesh configuration automatically
test_scenarios = [
{"input": "Test case 1", "agents": ["conversation_agent"]},
{"input": "Test case 2", "agents": ["technical_agent"]}
]
best_genome = await sdk.evolve_swarm_architecture(test_scenarios)
await sdk.apply_evolved_configuration()
Adaptive Model Selection
# Automatic model selection based on request characteristics
response = await sdk.adaptive_execute(
prompt="Analyze this complex scenario",
preferred_models=["gpt-4o", "claude-3.5-sonnet"]
)
Documentation
- Architecture Guide - Technical implementation details
- Debugging Guide - Troubleshooting and monitoring
- Getting Started - Run
create-leafmesh my-projectto scaffold a complete example project
Use Cases
LeafMesh excels at:
- Customer Service Systems - Multi-tier workflows with self-healing
- Data Analysis Pipelines - Collaborative analytical workflows
- Content Creation - Coordinated writing and editing
- Decision Support - Complex decision-making with oversight
- Workflow Automation - Business process automation
Framework Comparison
| Feature | LeafMesh | LangGraph | CrewAI | AutoGen |
|---|---|---|---|---|
| YAML Configuration | Primary | Code-based | Code-based | Code-based |
| Built-in Coordination | Manager/Summarizer | Manual | Manual | Manual |
| Auto-Persistence | Redis | Manual | Manual | Manual |
| Self-Healing | Production | None | None | None |
| Evolutionary Optimization | Genetic Algorithm | None | None | None |
Licensing
LeafMesh is commercial software owned by LeafCraft.
- Evaluation: 30-day free evaluation for research/development
- Commercial: Requires valid commercial license for revenue-generating use
- Enterprise: Custom enterprise licensing available
Licensing: info@leafcraftstudios.com
Getting Started
- Install LeafMesh and set up Redis
- Create your first YAML configuration with basic agents
- Add Python enhancements for custom logic
- Enable revolutionary features for production
LeafMesh: Production-ready multi-agent AI with YAML-driven simplicity
Copyright 2025 LeafCraft. All rights reserved.
1 maintainer
Metadata
1 maintainer
Release files for leafmesh 2.4.418
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| leafmesh-2.4.418-cp314-none-any.whl | CPython 3.14 | none | any | Details |
| leafmesh-2.4.418-cp313-none-any.whl | CPython 3.13 | none | any | Details |
| leafmesh-2.4.418-cp312-none-any.whl | CPython 3.12 | none | any | Details |
| leafmesh-2.4.418-cp311-none-any.whl | CPython 3.11 | none | any | Details |
| leafmesh-2.4.418-cp310-none-any.whl | CPython 3.10 | none | any | Details |
Total release size: 25.8 MB
Release files / leafmesh-2.4.418-cp314-none-any.whl
| Download URL | leafmesh-2.4.418-cp314-none-any.whl |
|---|---|
| Size | 5.9 MB |
| Tags | CPython 3.14 |
|
SHA-256 checksum How to use checksums |
9c1b8a48ec7a726342e381bfc1a95b1ae7cf5554a6049aae971d0c4f8a845460
|
|
BLAKE2b-256 checksum How to use checksums |
b1e2d77955906dc4e34c5898e939cbb39ec45aed3128bf8a5cd4b5611fbaae9f
|
| 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 24, 2026.
Transparency logRelease files / leafmesh-2.4.418-cp313-none-any.whl
| Download URL | leafmesh-2.4.418-cp313-none-any.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.13 |
|
SHA-256 checksum How to use checksums |
38b87b102f29e8bcd3645bd3a754693c4dd6d78808aa17093ffb905d36f718f8
|
|
BLAKE2b-256 checksum How to use checksums |
191a275e0369005cff8bf80311071fec9fdac0c4bf3382ebfd7e212f7d91426d
|
| 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 24, 2026.
Transparency logRelease files / leafmesh-2.4.418-cp312-none-any.whl
| Download URL | leafmesh-2.4.418-cp312-none-any.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.12 |
|
SHA-256 checksum How to use checksums |
7f16f17f863a8648a9fa5d69d9c17bcc7a6236d88e88dd87674f5051ac3b539c
|
|
BLAKE2b-256 checksum How to use checksums |
522499a6436ec39c452152ae3bb70b95de0d48ad44f0f38939366c91e3c3a3c6
|
| 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 24, 2026.
Transparency logRelease files / leafmesh-2.4.418-cp311-none-any.whl
| Download URL | leafmesh-2.4.418-cp311-none-any.whl |
|---|---|
| Size | 5.7 MB |
| Tags | CPython 3.11 |
|
SHA-256 checksum How to use checksums |
89eb76a2346a4bd5cd634c57885cf8dca4834a52dce58c3498cb5f56c9c1a553
|
|
BLAKE2b-256 checksum How to use checksums |
a48d54fcc6376fc338aa96b64734f500463ac28bd9482f9bdb27a6323c5b26fd
|
| 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 24, 2026.
Transparency logRelease files / leafmesh-2.4.418-cp310-none-any.whl
| Download URL | leafmesh-2.4.418-cp310-none-any.whl |
|---|---|
| Size | 3.2 MB |
| Tags | CPython 3.10 |
|
SHA-256 checksum How to use checksums |
902b17e93aabcd12ee422b6bce26c4426ef65d00cb3633c636f4140bfffe9be6
|
|
BLAKE2b-256 checksum How to use checksums |
2e8502eaa37baee206a458d96ef1bb9c20b6ca794e72b48f336a8f64a2ca3e55
|
| 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 24, 2026.
Transparency logSecurity for leafmesh 2.4.418
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
All 5 files in this release have been uploaded with provenance metadata.
Attestation for leafmesh-2.4.418-cp314-none-any.whl
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 24, 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.
