> ## 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.

# What Is Indexed and When

> Understand what Search can find, when new content appears, and how repository scope affects results.

Search queries Entire's indexes. It does not read your local working tree.

## What Search Indexes

| Search mode     | Indexed content                                                                           | Results                         |
| --------------- | ----------------------------------------------------------------------------------------- | ------------------------------- |
| Semantic search | Git commits from repositories Entire has synced and agent history pushed with checkpoints | Commits and sessions            |
| Code Search     | Text from tracked files available in an indexed repository                                | Literal matches grouped by file |

Semantic search indexes user prompts and assistant prose. It leaves out tool-only turns and the code inside a transcript, and folds checkpoint matches into their owning sessions. If you have the checkpoint ID, open it directly:

```shell theme={null}
entire checkpoint explain CHECKPOINT_ID
```

For a checkpoint from another GitHub repository, add `--repo OWNER/REPO` and use the full checkpoint ID.

Code Search does not find uncommitted changes, untracked files, commits that exist only in your local clone, or branches other than the one Entire indexes.

## When New Content Appears

Commit and push the branch that contains your work. Push the checkpoint data so semantic search can index agent-session content.

Indexing runs after your content reaches Entire, so recent work may not appear right away. Give it a couple of minutes before treating a missing result as a problem.

## Which Repositories Search Includes

The CLI searches the current repository by default. Use `--repo` for a specific indexed repository or `--all-repos` for all indexed repositories your account can access:

```shell theme={null}
entire search "retry logic" --repo entireio/cli
entire search "retry logic" --all-repos
```

By default, entire.io searches all accessible indexed repositories. Use the **Repository** filter to narrow the scope.

A local clone does not make a repository searchable. Your Entire account needs access to it, and Entire must finish syncing and indexing it.

## What an Empty Result Means

An empty result usually means the search worked and found nothing. It is not by itself a sign of an authentication or indexing error.

Before changing the query, confirm you pushed the work, gave indexing time, and searched the right repository. Then check the search mode:

* Use semantic search for prompts, decisions, commits, and agent-session context.
* Use Code Search for literal source text such as function names, error messages, and configuration keys.

If the content should be indexed and the scope is correct, continue with [Search Troubleshooting](/guides/search/troubleshooting).

## Continue With

<CardGroup cols={2}>
  <Card title="Search in entire.io" icon="globe" href="/guides/search/search-in-entire-io">
    Search accessible indexed repositories in the browser.
  </Card>

  <Card title="Search in the CLI" icon="terminal" href="/guides/search/search-in-cli">
    Semantic and Code Search from your terminal.
  </Card>

  <Card title="Search Troubleshooting" icon="wrench" href="/guides/search/troubleshooting">
    Diagnose missing commands, results, or repositories.
  </Card>
</CardGroup>