### Summary 💡 Document headless Multiple values Autocomplete in Base UI. ### Examples 🌈 I think that https://mui.com/material-ui/react-autocomplete/#customized-hook would be better in the Base UI's docs. ### Motivation 🔦 When landing in https://mui.com/base/react-autocomplete/ the component feels limited in terms of features while it's feature rich. I saw this need from browsing: https://github.com/shadcn/ui/issues/66. I think that it would be great to move as much as possible from https://mui.com/material-ui/react-autocomplete/ and https://mui.com/joy-ui/react-autocomplete/ to be present on Base UI docs instead.
Summary 💡
Document headless Multiple values Autocomplete in Base UI.
Examples 🌈
I think that https://mui.com/material-ui/react-autocomplete/#customized-hook would be better in the Base UI's docs.
Motivation 🔦
When landing in https://mui.com/base/react-autocomplete/ the component feels limited in terms of features while it's feature rich. I saw this need from browsing: shadcn-ui/ui#66.
I think that it would be great to move as much as possible from https://mui.com/material-ui/react-autocomplete/ and https://mui.com/joy-ui/react-autocomplete/ to be present on Base UI docs instead.