Skip to main content
Search queries Entire’s indexes. It does not read your local working tree.

​
What Search Indexes

History search uses semantic and keyword matching. It folds checkpoint matches into their owning sessions. If you have the checkpoint ID, you can open it directly:
For a checkpoint from another GitHub repository, add --repo OWNER/REPO and use the full checkpoint ID. Code Search matches text in the repository index. It does not search uncommitted changes, untracked files, or commits that exist only in your local clone.

​
When New Content Appears

Commit and push the branch that contains your work. Push the checkpoint data so history search can index agent-session content. Indexing runs after the remote content reaches Entire, so recent work may not appear immediately. Allow 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:
By default, entire.io searches all accessible indexed repositories. Use the Repository filter to narrow the scope. Authentication and repository permissions apply to both surfaces. A local clone does not make a repository searchable. Your Entire account must have access to the repository, and Entire must finish syncing and indexing it.

​
What an Empty Result Means

An empty result can be a successful search with no matches. It does not by itself indicate an authentication or indexing error. Before changing the query, confirm that you pushed the work, allowed time for indexing, and searched the intended repository. Then check the search mode:
  • Use history 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.

​
Continue With

Search in the CLI

Search history and source code from your terminal.

Search in entire.io

Search accessible indexed repositories in the browser.

Search Troubleshooting

Diagnose missing commands, results, or repositories.