> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Search in Entire.io
> Search past agent work and indexed source code from the Search page in Entire.io.
## Open Search
Once you are [logged in to Entire](/cli-reference/login), open **Search** from the sidebar.
You must be logged in to use Search, including when searching public repositories.
You can also:
* press `/` to open Search directly
* press `Command-K` on macOS or `Ctrl-K` elsewhere, enter a query, and choose the Search action
With an empty query, Search shows your recent searches.
## Choose Repositories
By default, Search includes every indexed repository you can access. Use the **Repository** filter to search one or more specific repositories.
You do not need a local clone to search a repository in Entire.io. The repository must be available to your Entire account and indexed. If it does not appear in the filter, you cannot search it from Entire.io yet.
## Enter a Query
Enter a phrase, question, function name, error message, or other text.
The examples below come from the indexed [Entire CLI repository](https://entire.io/gh/entireio/cli). They show how Search behaves, but this repository may not appear in your **Repository** filter.
### Find Past Work
To find related past work, enter a short phrase or ask a natural-language question.
Semantic search matches the content of past work, so describe what you are looking for rather than giving an instruction. A query like `git optimization` works better than `show me all of the latest git optimizations`: words such as "show me all of the" do not appear in the work itself and dilute the match. To find recent work, use the date filter instead of words like "latest".
```text Short phrase example theme={null}
history import when enabling Entire
```
```text Natural-language question example theme={null}
how did we decide to make history import explicit when enabling Entire?
```
### Find Text in Source Code
Use the **Code** tab when you know text that appears in a source file, such as a function name, error message, or configuration option:
```text Literal text example theme={null}
import-history
```
## Review Results
After you enter a query, choose a tab to review one kind of result:
* **Commits** show related Git commits.
* **Sessions** show related agent conversations.
* **Code** shows lines containing literal matches from indexed source files.
## Filter Results
Filter past-work results by repository, date, or branch, and sort them by relevance, date, author, or title. Code results can be filtered by repository.
Select a commit or session to open it. In **Code**, expand a file to view its matching lines.
## Continue with
Run both search modes from your terminal.
Practice both kinds of search with one guided tutorial.