# Nushell core team meeting 2025-03-26
## Attendees
- Darren
- Piet
- Bahex
- Andy
- Douglas
- Rose
- Stefan
- Yash
- Michael
- Wind

## Agenda
- [X] optional predicate for `any`
- [x] External completors no longer working with custom commands and aliases - feature or bug? (Changed in [#15086](https://github.com/nushell/nushell/pull/15086). Also see [Doc PR#1847](https://github.com/nushell/nushell.github.io/pull/1847/files) and [Doc Issue #1845](https://github.com/nushell/nushell.github.io/issues/1845))
- [ ] external background jobs
- [x] Quick status on https://github.com/nushell/nushell/pull/15360

## Discussed Topics

### Brief discussion: type coercion like tweaks
- sleep with int
- `any` accepting a `list<any>` w/o closure and interpreting just the bools in the list. (no truthy coercion but weird behavior on mixed collections)
- weirdness around mixed collection leads us to preferring the verbose variant

### external (or written in nu) completers for internal definitions regressed

- Custom completers only get a single string with the whole line, rather than a list of strings

`std/config` addition proposed by Rose:

def "nu-complete external" [context: string] {
  do $env.config.completions.external.completer ($context | split row " ")
}

(note: we could also use `ast -f` to split here instead of `split row` for more accurate argument splitting)

Q: testing of external completer integrations