15 KiB
Contribution Guidelines
The Enterprise-Grade Production-Ready Multi-Agent Orchestration Framework
Table of Contents
- Project Overview
- Getting Started
- How to Contribute
- Coding Standards
- Areas Needing Contributions
- Development Resources
- Community and Support
- License
Project Overview
Swarms is an enterprise-grade, production-ready multi-agent orchestration framework focused on making it simple to orchestrate agents to automate real-world activities. The goal is to automate the world economy with these swarms of agents.
Key Features
Category | Features | Benefits |
---|---|---|
🏢 Enterprise Architecture | • Production-Ready Infrastructure • High Reliability Systems • Modular Design • Comprehensive Logging |
• Reduced downtime • Easier maintenance • Better debugging • Enhanced monitoring |
🤖 Agent Orchestration | • Hierarchical Swarms • Parallel Processing • Sequential Workflows • Graph-based Workflows • Dynamic Agent Rearrangement |
• Complex task handling • Improved performance • Flexible workflows • Optimized execution |
🔄 Integration Capabilities | • Multi-Model Support • Custom Agent Creation • Extensive Tool Library • Multiple Memory Systems |
• Provider flexibility • Custom solutions • Extended functionality • Enhanced memory management |
We Need Your Help To:
- Write Tests: Ensure the reliability and correctness of the codebase
- Improve Documentation: Maintain clear and comprehensive documentation
- Add New Orchestration Methods: Add multi-agent orchestration methods
- Remove Defunct Code: Clean up and remove bad code
- Enhance Agent Capabilities: Improve existing agents and add new ones
- Optimize Performance: Improve speed and efficiency of swarm operations
Your contributions will help us push the boundaries of AI and make this library a valuable resource for the community.
Getting Started
Installation
Using pip
pip3 install -U swarms
Using uv (Recommended)
uv is a fast Python package installer and resolver, written in Rust.
# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
# Install swarms using uv
uv pip install swarms
Using poetry
# Install poetry if you haven't already
curl -sSL https://install.python-poetry.org | python3 -
# Add swarms to your project
poetry add swarms
From source
# Clone the repository
git clone https://github.com/kyegomez/swarms.git
cd swarms
# Install with pip
pip install -e .
Environment Configuration
Create a .env
file in your project root with the following variables:
OPENAI_API_KEY=""
WORKSPACE_DIR="agent_workspace"
ANTHROPIC_API_KEY=""
GROQ_API_KEY=""
Project Structure
swarms/
: Contains all the source code for the libraryagents/
: Agent implementations and base classesstructs/
: Swarm orchestration structures (SequentialWorkflow, AgentRearrange, etc.)tools/
: Tool implementations and base classesprompts/
: System prompts and prompt templatesutils/
: Utility functions and helpers
examples/
: Includes example scripts and notebooks demonstrating how to use the librarytests/
: Unit tests for the librarydocs/
: Documentation files and guides
How to Contribute
Reporting Issues
If you find any bugs, inconsistencies, or have suggestions for enhancements, please open an issue on GitHub:
- Search Existing Issues: Before opening a new issue, check if it has already been reported.
- Open a New Issue: If it hasn't been reported, create a new issue and provide detailed information.
- Title: A concise summary of the issue.
- Description: Detailed description, steps to reproduce, expected behavior, and any relevant logs or screenshots.
- Label Appropriately: Use labels to categorize the issue (e.g., bug, enhancement, documentation).
Issue Templates: Use our issue templates for bug reports and feature requests:
Submitting Pull Requests
We welcome pull requests (PRs) for bug fixes, improvements, and new features. Please follow these guidelines:
-
Fork the Repository: Create a personal fork of the repository on GitHub.
-
Clone Your Fork: Clone your forked repository to your local machine.
git clone https://github.com/kyegomez/swarms.git cd swarms
-
Create a New Branch: Use a descriptive branch name.
git checkout -b feature/your-feature-name
-
Make Your Changes: Implement your code, ensuring it adheres to the coding standards.
-
Add Tests: Write tests to cover your changes.
-
Commit Your Changes: Write clear and concise commit messages.
git commit -am "Add feature X"
-
Push to Your Fork:
git push origin feature/your-feature-name
-
Create a Pull Request:
- Go to the original repository on GitHub.
- Click on "New Pull Request".
- Select your branch and create the PR.
- Provide a clear description of your changes and reference any related issues.
-
Respond to Feedback: Be prepared to make changes based on code reviews.
Note: It's recommended to create small and focused PRs for easier review and faster integration.
Good First Issues
The easiest way to contribute is to pick any issue with the good first issue
tag 💪. These are specifically designed for new contributors:
- Good First Issues
- Contributing Board - Participate in Roadmap discussions!
Coding Standards
To maintain code quality and consistency, please adhere to the following standards.
Type Annotations
-
Mandatory: All functions and methods must have type annotations.
-
Example:
def add_numbers(a: int, b: int) -> int: return a + b
-
Benefits:
- Improves code readability.
- Helps with static type checking tools.
Docstrings and Documentation
-
Docstrings: Every public class, function, and method must have a docstring following the Google Python Style Guide or NumPy Docstring Standard.
-
Content:
- Description: Briefly describe what the function or class does.
- Args: List and describe each parameter.
- Returns: Describe the return value(s).
- Raises: List any exceptions that are raised.
-
Example:
def calculate_mean(values: List[float]) -> float: """ Calculates the mean of a list of numbers. Args: values (List[float]): A list of numerical values. Returns: float: The mean of the input values. Raises: ValueError: If the input list is empty. """ if not values: raise ValueError("The input list is empty.") return sum(values) / len(values)
-
Documentation: Update or create documentation pages if your changes affect the public API.
Testing
-
Required: All new features and bug fixes must include appropriate unit tests.
-
Framework: Use
unittest
,pytest
, or a similar testing framework. -
Test Location: Place tests in the
tests/
directory, mirroring the structure ofswarms/
. -
Test Coverage: Aim for high test coverage to ensure code reliability.
-
Running Tests: Provide instructions for running tests.
pytest tests/
Code Style
- PEP 8 Compliance: Follow PEP 8 style guidelines.
- Linting Tools: Use
flake8
,black
, orpylint
to check code style. - Consistency: Maintain consistency with the existing codebase.
Areas Needing Contributions
We have several areas where contributions are particularly welcome.
Writing Tests
- Goal: Increase test coverage to ensure the library's robustness.
- Tasks:
- Write unit tests for existing code in
swarms/
. - Identify edge cases and potential failure points.
- Ensure tests are repeatable and independent.
- Add integration tests for swarm orchestration methods.
- Write unit tests for existing code in
Improving Documentation
- Goal: Maintain clear and comprehensive documentation for users and developers.
- Tasks:
- Update docstrings to reflect any changes.
- Add examples and tutorials in the
examples/
directory. - Improve or expand the content in the
docs/
directory. - Create video tutorials and walkthroughs.
Adding New Swarm Architectures
- Goal: Provide new multi-agent orchestration methods.
- Current Architectures:
Enhancing Agent Capabilities
- Goal: Improve existing agents and add new specialized agents.
- Areas of Focus:
- Financial analysis agents
- Medical diagnosis agents
- Code generation and review agents
- Research and analysis agents
- Creative content generation agents
Removing Defunct Code
- Goal: Clean up and remove bad code to improve maintainability.
- Tasks:
- Identify unused or deprecated code.
- Remove duplicate implementations.
- Simplify complex functions.
- Update outdated dependencies.
Development Resources
Documentation
- Official Documentation: docs.swarms.world
- Installation Guide: Installation
- Quickstart Guide: Get Started
- Agent Architecture: Agent Internal Mechanisms
- Agent API: Agent API
Examples and Tutorials
- Basic Examples: examples/
- Agent Examples: examples/single_agent/
- Multi-Agent Examples: examples/multi_agent/
- Tool Examples: examples/tools/
API Reference
- Core Classes: swarms/structs/
- Agent Implementations: swarms/agents/
- Tool Implementations: swarms/tools/
- Utility Functions: swarms/utils/
Community and Support
Connect With Us
Platform | Link | Description |
---|---|---|
📚 Documentation | docs.swarms.world | Official documentation and guides |
📝 Blog | Medium | Latest updates and technical articles |
💬 Discord | Join Discord | Live chat and community support |
@kyegomez | Latest news and announcements | |
The Swarm Corporation | Professional network and updates | |
📺 YouTube | Swarms Channel | Tutorials and demos |
🎫 Events | Sign up here | Join our community events |
Onboarding Session
Get onboarded with the creator and lead maintainer of Swarms, Kye Gomez, who will show you how to get started with the installation, usage examples, and starting to build your custom use case! CLICK HERE
Community Guidelines
- Communication: Engage with the community by participating in discussions on issues and pull requests.
- Respect: Maintain a respectful and inclusive environment.
- Feedback: Be open to receiving and providing constructive feedback.
- Collaboration: Work together to improve the project for everyone.
License
By contributing to swarms, you agree that your contributions will be licensed under the Apache License.
Citation
If you use swarms in your research, please cite the project by referencing the metadata in CITATION.cff.
Thank you for contributing to swarms! Your efforts help make this project better for everyone.
If you have any questions or need assistance, please feel free to:
- Open an issue on GitHub
- Join our Discord community
- Reach out to the maintainers
- Schedule an onboarding session
Happy contributing! 🚀