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

# Search Troubleshooting

> Fix common history and Code Search issues in the CLI, Entire.io, and the search Skill.

Use this page when Search does not appear or cannot find the work or code you expect.

<AccordionGroup>
  <Accordion title="The CLI says you are not authenticated">
    Run:

    ```shell theme={null}
    entire login
    ```

    Search only returns repositories, history, and code your account can access.
  </Accordion>

  <Accordion title="`entire search` does not appear in `entire --help`">
    [Update the Entire CLI](/updating). In versions 0.9.0 and earlier, `entire search` was hidden from help output but still runnable.

    ```shell theme={null}
    entire version
    ```

    `entire checkpoint search` is an equivalent alias in every version.
  </Accordion>

  <Accordion title="Search opens an interactive view when you expected plain output">
    Use `--json` for scripts, automation, or agent instructions:

    ```shell theme={null}
    entire search "auth token refresh" --json
    ```

    Running a history search in a terminal opens the interactive results view. Redirected or piped output is JSON automatically.
  </Accordion>

  <Accordion title="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:

    ```shell theme={null}
    entire status
    ```

    If the work happened in another repository, use `--repo OWNER/REPO` or `--all-repos`.
  </Accordion>

  <Accordion title="Search returns results from the wrong scope">
    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:

    ```shell theme={null}
    entire search "retry logic" --repo OWNER/REPO
    ```

    Search all accessible repositories:

    ```shell theme={null}
    entire search "retry logic" --all-repos
    ```
  </Accordion>

  <Accordion title="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:

    ```shell theme={null}
    entire search "duplicate validation error banner" branch:main date:month
    ```
  </Accordion>

  <Accordion title="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`.
  </Accordion>

  <Accordion title="`author:`, `branch:`, or `date:` do not filter Code Search">
    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.
  </Accordion>

  <Accordion title="Can Code Search match exact letter case?">
    Not currently. The CLI accepts `--case-sensitive`, but the search backend does not yet apply it.
  </Accordion>

  <Accordion title="The search Skill returns no useful history">
    Confirm the agent has the [Skills workflow](/learn/skills) installed and can run `entire search --json`.

    Make the prompt more specific:

    ```text theme={null}
    search past work for duplicate validation in the checkout form
    ```
  </Accordion>
</AccordionGroup>

## Continue with

<CardGroup cols={2}>
  <Card title="Search" icon="magnifying-glass" href="/guides/search/overview">
    Compare semantic and keyword search with literal code search.
  </Card>

  <Card title="Search in the CLI" icon="terminal" href="/guides/search/search-in-cli">
    Review both CLI search modes.
  </Card>
</CardGroup>