Thanks for your interest in improving AG-UI!
This short guide shows the fastest way to get your idea merged. You can find more detailed contribution guides at ag-ui.com
Before writing code, open a new Discussion and briefly cover:
- Problem – what you’re trying to solve.
- Proposal – how you plan to solve it (code, docs, design, etc.).
- Alternatives – other options you considered.
Early feedback keeps everyone aligned and saves re-work.
Meet the team and potential collaborators in our bi-weekly community call.
Need a quick sync?
- Markus: @mme_xyz on X (Twitter)
- Book a chat: https://calendly.com/markus-copilotkit/ag-ui
Resource | Link |
---|---|
Learn how to connect to AG-UI with JS | https://docs.ag-ui.com/quickstart/connect |
Learn how to connect to AG-UI with Python | https://docs.ag-ui.com/quickstart/build |
Dojo reference implementation | https://github.com/ag-ui-protocol/ag-ui/tree/main/dojo |
- Fork the repo and create a feature branch.
- Keep changes focused—one PR per feature or fix.
- Link back to your Discussion in the PR description.
We review PRs weekly. Feel free to nudge us in your Discussion if you haven’t heard back in a few days.
Thank you for making AG-UI better!