Search Files and Find Text in UAPP CodeSpace
Use CodeSpace's home-wide filename Quick Open, wildcard patterns and keyboard results, or Find text inside the active editor file.
CodeSpace provides two search tools: the header's Search files locates names across the account, and the toolbar's Find locates text inside the active editor file.
Search files / Quick Open
Type in Search files. The application waits about half a second after typing, then requests matches from the account home. Ctrl+P / Command+P focuses the search input. On narrow screens, use the search icon to reveal the field if needed.
Matching is recursive and case-insensitive. Plain text matches name substrings; patterns containing *, ? or [ use wildcard matching. For example, index matches names containing index, and *.json matches names ending in .json. This searches names, not file contents.
The interface requests at most 50 results, including any directory matches returned by the service. It has no scope selector or pagination. Narrow the pattern, or use File Studio Search to choose a specific location. Symlinks are excluded and linked directories are not traversed.
Choose a result
Results show a name and account-relative path. Use Arrow Down/Up to change the highlighted result, Enter or a click to open it, and Escape to clear and dismiss search. Arrow selection wraps through the list. On mobile, tapping outside also hides the search panel.
A file result opens an editor tab or activates its existing tab. Directory results can appear, but the current Quick Open handler does not navigate them; use Explorer for folders. Search is not filtered to guarantee editability, so unsupported file results can fail to open.
Find text in the active file
Open a file and click Find to invoke Monaco's in-editor Find widget. Enter the text and use the options and next/previous controls offered there. This searches the current editor model, including unsaved edits; it does not perform a server-wide content search or save replacements.
Review the active breadcrumb before editing a match. No results, an unsupported file and a failed search request are different outcomes. If Quick Open stops responding, preserve pending edits and use Explorer while the provider investigates; see Troubleshooting.