We love contributions — code, docs, triage, examples, and tests. Start on Discord so scope is clear before you invest time.
Daily contributor sync: every day at 10:00 PM IST
- Discord → questions, mentoring, sync, realtime unblocking
- GitHub → bugs, proposals, design threads, review
Non-trivial work? Comment on the issue or ping Discord first. Get a thumbs-up, then build.
| Type | Examples |
|---|---|
| Code | Fixes, features, adapters, performance |
| Docs | README, docs/, architecture notes |
| Triage | Repro bugs, tighten reports, label suggestions |
| Examples / tests | Recipes, edge cases, flaky-test hunts |
- Join Discord — say hi and get guidance
- Read the contract — AGENTS.md (layout, commands, hard rules, PR hygiene)
- Pick something focused — open issues; prefer
good-first-issue/help wanted - Claim it — comment
I'd like to work on thisand wait for assignment - Open a clear PR — narrow change, link the issue, user-visible impact, tests
- Iterate — address review; maintainers merge
Need the product/run overview first? Start with README.md and docs/architecture.md.
Use the GitHub issue forms (Bug report / Feature request) so reports stay reproducible. Bug reports should include AO version, environment, repro steps, and expected vs actual behavior.
New PRs are prefilled from .github/pull_request_template.md.
Also follow PR hygiene in AGENTS.md: branch from main, one issue per PR, conventional commits, explain intentional omissions, and keep CI green for the area you touched.
Be respectful, constructive, and assume good intent. Report problems to maintainers via Discord DM.
Thanks for making agent-orchestrator better for the next person who shows up.