Extending and Contributing to Crush
1. Start with one focused product layer​
Crush contributions are easiest when you choose one clear target:
| Goal | First place to look |
|---|---|
| Runtime behavior | core source code |
| Onboarding or docs | repo docs and examples |
| Packaging and distribution | build and release files |
| UX polish | terminal interaction and output behavior |
2. Why this matters​
With terminal agents, the interaction loop is the product. A small improvement to clarity or predictability can matter more than a flashy new feature.
3. Best first contributions​
- docs and setup fixes,
- terminal UX improvements,
- targeted runtime correctness fixes,
- config clarity,
- better examples.
4. Think in developer experience​
A good Crush contribution should improve at least one of these:
- clarity,
- speed,
- trust,
- reviewability.
5. Before opening a PR​
Validate the full terminal workflow you changed and make sure the new behavior is easy for another developer to understand without reading the whole codebase.