Thanks for your interest in contributing! This guide covers the basics for all repos in the plexus-oss organization.
- Search existing issues first to avoid duplicates
- Use the Bug Report issue template
- Include reproduction steps, expected vs actual behavior, and your environment
- Use the Feature Request issue template
- Describe the problem or use case, not just the solution
- Keep requests focused on a single idea
- Fork the repo and create a branch from
main - Make your changes, keeping the scope small and focused
- Follow the existing code style and patterns in that repo
- Fill out the PR template completely
- Link the related issue
- Describe what changed and why
- Link an issue when one exists
- Keep scope small — one concern per PR
- Tests pass before requesting review
- No breaking changes without discussion first
Each repo has its own setup instructions:
- agent — Python SDK (
pip install -e ".[dev]") - c-sdk — C library (see repo README for build instructions)
- ui — React components (
pnpm install)
- Follow existing patterns in whichever repo you're contributing to
- No style wars — consistency with the file you're editing wins
- If the repo has a linter or formatter configured, use it
Join our Discord for help and discussion.