# Nushell core team meeting 2025-12-10 ## Attendees - Auca - amtoine - Ayax - Bahex - fdncred - Forelyl - ndyg - Piepmatz - storm - kaictl - Johannes ## Agenda - [x] Adding MCP as default feature - [x] Revisit 1.0 discussion? - [x] New nu-parser in concert with 1.0 discussion ? ## Discussed Topics ### MCP as default feature Most of the team agreed that making it default is ok. Amtoine mentioned if it were his project it would be opt-in by default but was willing to have it opt-out now. ### 1.0 discussion + new_nu_parser Talked about what it takes to get to 1.0 and should new nu parser should be part of it. Need to know where new_nu_parser is so we understand the gaps. What's the integration plan? Investigate whether Sophia and/or Devyn would be willing to consult on architecture. Keep new_nu_parser on the roadmap for now. Some polish on the plugin api. e.g. closures may not work right now between host and plugin. Error handling needs to be cleaned up (Piet brought up that there are many unwrap calls) Name spacing. Should we be able to alias commands like the command name is `polars open` but we want to alias it to `p.open`. Should that be 1.0? Would be nice. Piet brought up a post 1.0 thought, making any external binary be able to use some protocol or something so that it could "speak" structured data inside of nushell. Can we raise funding to help accelerate 1.0 items?