Extending and Contributing to TinyAGI
1. Start with the narrowest surface​
TinyAGI offers several obvious extension areas:
| Goal | First place to look |
|---|---|
| Agent or team behavior | agent and team runtime code |
| Channel support | channel adapters |
| Operator UX | TinyOffice |
| Integrations and hooks | plugin system |
| Queue or persistence behavior | queue and storage code |
2. Why boundaries matter​
Because TinyAGI combines 24/7 runtime behavior with a UI and channel surfaces, broad patches can become hard to review quickly. Narrow contributions are much easier to trust.
3. Best first contributions​
- docs and onboarding fixes,
- TinyOffice clarity improvements,
- plugin examples,
- targeted queue or retry fixes,
- channel setup polish.
4. Think in operator workflows​
A good TinyAGI contribution should improve:
- reliability,
- observability,
- collaboration clarity,
- or safer background operation.
5. Before opening a PR​
Validate the full flow your patch touches, especially if it crosses queue, channel, and UI boundaries.