> ## 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.
# Overview
> Query the code across your repositories and the commits, sessions, and agent work that produced it.
Agentic Search answers questions about your code and the work that produced it. One query returns the commits and sessions behind a change alongside the matching code.
Search runs on a dual engine:
* **Semantic search** matches meaning and keywords across commits and sessions, surfacing the reasoning behind a change.
* **Code Search** finds literal text such as function names, error messages, and configuration keys. It is symbol-aware, with definitions and references.
[entire.io](/guides/search/search-in-entire-io) searches every repository you can access. The [Entire CLI](/guides/search/search-in-cli) starts with the current repository and widens with `--repo` or `--all-repos`.
Search reads Entire's indexes, not your local working tree. See [What Is Indexed and When](/guides/search/what-is-indexed) for what it covers and when new work shows up.
## Benefits of Using Search
* Ask why code is the way it is and get the commit, session, and prompt behind it, not just the lines that changed.
* Find precedent in repositories your agent has never cloned.
* Answer in fewer turns than cloning and grepping take, leaving more context window for the task.
* Find literal source text across your repositories in one query.
We benchmarked those claims. On nine engineering-history questions from our own repositories, run ten times each, an agent with Search answered 81 of 90 correctly. The same agent working from full Git history and the GitHub CLI answered 70 of 90, using more than twice the tokens and twice the steps.
These questions come from our own history rather than a public corpus. The harness, tasks, grading, and per-run results are at [entireio/searchmark](https://github.com/entireio/searchmark), so you can rerun it against your own organization.
## How to Use Search
| Surface | Semantic search | Code Search |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------- |
| [entire.io](/guides/search/search-in-entire-io) | Use the [**Commits** and **Sessions**](/guides/search/search-in-entire-io#review-results) tabs. | Use the **Code** tab. |
| [Entire CLI](/guides/search/search-in-cli) | Run `entire search "QUERY"`. | Run `entire search --code "TEXT"`. |
See [Use Search with Your Coding Agent](/guides/search/search-from-your-agent) for the Skill that runs these queries on your agent's behalf.
## Continue With
Use semantic search and Code Search from the Search page.
Search past work or indexed code from your terminal.
Let an agent find relevant commits and sessions.
Practice both kinds of search with one guided tutorial.
Check what Search can find and when new work becomes available.
Fix login, indexing, scope, and query issues.