Login and Setup
The CLI Says You Are Not Authenticated
The CLI Says You Are Not Authenticated
Run:Search only returns repositories, history, and code your account can access.
entire search Does Not Appear in entire --help
entire search Does Not Appear in entire --help
Update the Entire CLI, then check the installed version:
entire checkpoint search is an equivalent alias in every version.Your Agent Is Not Using Search
The Search Skill Returns No Useful History
The Search Skill Returns No Useful History
Confirm the agent has the Skills workflow installed and can run
entire search --json.Make the prompt more specific:Results Are Missing or Incomplete
Recent Work or Code Does Not Appear
Recent Work or Code Does Not Appear
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.Search Warns That Results May Be Incomplete
Search Warns That Results May Be Incomplete
A query fans out across regions, and a slow or unreachable one degrades the response instead of hanging it. entire.io reports that some sources were unavailable, and the CLI writes One query fans out to every region holding repositories you can access, so narrowing to a repository in the failing region does not help. That is where the query has to go. Check status.entire.io for a regional incident.Semantic search reports this warning on standard error only, so
results may be incomplete to standard error.Run the query again. If the warning persists, scope it to a repository that lives outside the affected region:--json output carries no sign of it. Code Search reports the affected jurisdictions in its JSON.Results Are Not What You Expected
Search Returns Results from the Wrong Scope
Search Returns Results from the Wrong Scope
CLI search is scoped to the current repository by default, while entire.io searches all accessible indexed repositories.Search one repository from the CLI:Search all accessible repositories:
Search Opens an Interactive View When You Expected Plain Output
Search Opens an Interactive View When You Expected Plain Output
Use Running a semantic search in a terminal opens the interactive results view. Redirected or piped output is JSON automatically.
--json for scripts, automation, or agent instructions:Past-Work Results Are Too Broad
Past-Work Results Are Too Broad
Add a feature name, error message, file, decision, or filter that would have appeared in the prompt, commit, or transcript:
Code Search Does Not Find the Expected Code
Code Search Does Not Find the Expected Code
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.A Multi-Term Code Search Returns Nothing
A Multi-Term Code Search Returns Nothing
Code Search matches your query literally, so a phrase of several words often has no match even when each word appears in the repository. Search one distinctive token instead:Use semantic search without
--code when you want to describe the change rather than name the text.Can Code Search Match Exact Letter Case?
Can Code Search Match Exact Letter Case?
Not currently. The CLI accepts
--case-sensitive, but the search backend does not yet apply it.checkpoint explain --repo Rejects a Commit SHA
checkpoint explain --repo Rejects a Commit SHA
entire checkpoint explain takes a checkpoint ID or a commit SHA, and it resolves a commit through the Entire-Checkpoint trailer in your local clone. Adding --repo removes that fallback, so a cross-repository lookup needs the full checkpoint ID the result carries rather than a commit SHA.Continue With
Search
Compare semantic and keyword search with literal Code Search.
Search in the CLI
Review both CLI search modes.
What Is Indexed and When
Check availability, timing, scope, and empty-result expectations.