Extending and Contributing to AionUi
1. Start with the narrowest layer​
AionUi is broad enough that contributions should begin with one clear surface:
| Goal | First place to look |
|---|---|
| Desktop workflow or UX | desktop app and shell layers |
| Agent integrations | integration surfaces for external CLIs or providers |
| Built-in assistant behavior | assistant definitions and workflow logic |
| Automation or remote control | scheduling and connector layers |
2. Why narrow changes matter​
Because AionUi bridges business workflows and technical agent ecosystems, a change in one place can affect:
- usability,
- trust,
- automation behavior,
- and compatibility with existing agent setups.
3. Best first contributions​
- onboarding and docs fixes,
- integration compatibility improvements,
- assistant workflow polish,
- desktop UX clarity,
- safe automation ergonomics.
4. Think in real workflows​
A good AionUi contribution should improve at least one of these:
- cowork ergonomics,
- assistant reliability,
- local trust,
- team repeatability.
5. Before opening a PR​
Validate the exact user workflow your patch changes and keep the scope tight enough that both developers and product-oriented reviewers can understand the tradeoff.