---
# System prepended metadata

title: Nushell core team meeting 2025-08-20

---

# Nushell core team meeting 2025-08-20
## Attendees
- Darren
- Piepmatz
- Michael
- Bahex
- Stefan
- Rose
- Jack
- Antoine

## Agenda
- [ ] {%preview https://github.com/nushell/nushell/pull/16451 %}
- [ ] if Rose is available: basic tutorial on how to make the new release note system happy
- [x] 

## Discussed Topics
- Issue Closed counter was at 5094 when it was announced last week

### AI Policy - revisited
- Example of a disclosure policy by Mitchell on Ghostty https://github.com/ghostty-org/ghostty/pull/8289
- Signs of AI writing: https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing
- Vibe coding complex changes in Rust: https://www.youtube.com/watch?v=EL7Au1tzNxE

### ShellError size rework - larger topic of performance engineering
- Piepmatz has valiantly worked on getting ShellError smaller
- tradeoffs for usability
    - different compact string types with slightly different APIS
    - Boxing particular parts/the whole shell erro has its pros and cons (especially usability cons).
- Any work that aims to improve performance needs to show its benefits and should be measured by benchmarks etc.
    - For larger systems: don't microoptimize for one thing but bring a general improvement 
    - Need to make a decision on some trade-offs (one use favored, another pessimised).
    - Have a broader collection of benchmarks to be aware of those trade offs when making larger changes (for smaller optimization reasonable assumptions with singular benchmarks can be made) 