Shadcn Autocomplete Search Results

When to use

• Search and filter fields that suggest matching options while the user types
• People and record lookups, grouped by team or fetched from a server as the query changes
• Form fields whose typed or picked text is validated with the rest of the form on submit

When not to use

• Options known up front in the page, with no request, loading or error states: use the Autocomplete Clear & Trigger example
• A selection that stores the chosen option rather than typed text, or several as chips: use the Combobox component
• Options nested in levels that the user drills into one level at a time: use the Cascader component
• A palette of app actions and keyboard shortcuts, often opened in a dialog: use the Command component

Agent notes

• Replace searchDevelopers with your request; it waits 200 to 1000ms at random and throws on 2% of calls or when the query is "error"
• Keep the ignore flag when you swap in a real fetch, since it discards a response that lands after the query changed
• shouldRenderPopup keeps the popup unmounted while searchValue is empty, so the chevron opens nothing before typing
• value and onValueChange carry the input text as a string; picking an item only fills that text and stores no item object
• Both twins are built on @base-ui/react, so installing it in a radix project adds Base UI as a dependency
• A Server Component cannot create the function child of AutocompleteList, so the file that renders it needs a use client directive

Third-party API docs

• Base UI v1: API reference, docs, llms.txt