Skip to main content
Use this page when Search does not appear or cannot find the work or code you expect.
Run:
Search only returns repositories, history, and code your account can access.
Update the Entire CLI. In versions 0.9.0 and earlier, entire search was hidden from help output but still runnable.
entire checkpoint search is an equivalent alias in every version.
Use --json for scripts, automation, or agent instructions:
Running a history search in a terminal opens the interactive results view. Redirected or piped output is JSON automatically.
Confirm the work has been committed and pushed, then give Entire a couple minutes to index it.Check that the current repository is Entire-enabled:
If the work happened in another repository, use --repo OWNER/REPO or --all-repos.
CLI search is scoped to the current repository by default. Entire.io searches all accessible indexed repositories by default.Search one repository from the CLI:
Search all accessible repositories:
Add a feature name, error message, file, decision, or filter that would have appeared in the prompt, commit, or transcript:
Code Search matches literal text, not a description of behavior. Search for a function or variable name, error message, config key, or unique string that appears in the file.If you remember the work but not the source text, use semantic and keyword search without --code.
Code Search supports only the repo: inline filter. The other tokens are treated as literal query text. Use history search without --code when you need author, branch, or date filters.
Not currently. The CLI accepts --case-sensitive, but the search backend does not yet apply it.
Confirm the agent has the Skills workflow installed and can run entire search --json.Make the prompt more specific:

​
Continue with

Search

Compare semantic and keyword search with literal code search.

Search in the CLI

Review both CLI search modes.