Skip to content

Investigate code patterns

Search can help you understand where a public code pattern appears and how it is used. This workflow works for API integrations, configuration names, distinctive error strings, and project-specific identifiers.

Start with a recognizable literal, such as api.example.com or EXAMPLE_CLIENT_ID. Avoid surrounding quotation marks unless the quotes are part of the text you want.

Open several file previews. Compare paths, surrounding calls, and available commit references. Use repository and file-type filters to organize matches already received. These filters do not expand or rerun the search.

Enable regex to search a small set of alternatives, for example (EXAMPLE_CLIENT_ID|EXAMPLE_APP_ID). If a query fills the first 100 matches, make it more specific and run a new search.

Use Save search to return to the query later. Give it a descriptive name such as “Example integration configuration.” Save individual results separately if you need to preserve their references and excerpts.

For supported automation, follow the API quickstart. The public API exposes literal code search and workspace listing. It does not expose every operation available inside the application.