Extending and Contributing to Coworker
1. Start with the product surface you want to improve​
Coworker contributions usually fit one of these layers:
| Goal | First place to look |
|---|---|
| Desktop UX | app and UI layers |
| Local action behavior | core runtime surfaces |
| Provider support | model integration areas |
| Tool connections | external integration layers |
| Safety or review | logs and approval mechanisms |
2. Why narrow changes matter​
A local desktop agent sits close to real user data. That means small, well-validated changes are especially important for trust.
3. Best first contributions​
- docs and onboarding fixes,
- provider integration polish,
- better approval messaging,
- clearer logs,
- small workflow reliability improvements.
4. Think in user trust​
A strong Coworker contribution should improve:
- clarity,
- predictability,
- usefulness,
- or local control.
5. Before opening a PR​
Validate the exact desktop workflow your patch affects and make sure the approval and logging story still makes sense end to end.