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

# Semantic Search Troubleshooting

> Fix common semantic search issues in the CLI, Entire.io, and the search Skill.

Use this page when Semantic Search cannot find expected checkpoints, sessions, or commits.

<AccordionGroup>
  <Accordion title="`entire search` says you are not authenticated">
    Run:

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

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

  <Accordion title="`entire search` does not appear in `entire --help`">
    Run the command directly:

    ```shell theme={null}
    entire search --help
    ```

    If that fails, update Entire from the [updating guide](/updating), then try again.
  </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 `entire search` without `--json` can open an interactive results table when stdout is a terminal.
  </Accordion>

  <Accordion title="You do not see recent work">
    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, pass a repo filter:

    ```shell theme={null}
    entire search "auth token refresh" --repo OWNER/REPO
    ```
  </Accordion>

  <Accordion title="Search returns results from the wrong scope">
    CLI search is scoped to the current repository by default.

    To search one specific repository:

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

    To search across all accessible repositories:

    ```shell theme={null}
    entire search "retry logic" --all-repos
    ```

    You can also use the inline filter:

    ```shell theme={null}
    entire search "repo:* retry logic"
    ```
  </Accordion>

  <Accordion title="The query is too broad">
    Add details that would have appeared in the prompt, commit, transcript, or files:

    * feature names
    * user-facing labels
    * error messages
    * file names
    * the decision or behavior you remember
    * an author, branch, date, or repo filter

    Example:

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

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

    Then make the prompt more specific:

    ```text theme={null}
    search past work for duplicate validation in the checkout form
    ```

    If the agent says authentication is missing, run `entire login` in the same environment where the agent runs.
  </Accordion>
</AccordionGroup>

## Continue with

<CardGroup cols={2}>
  <Card title="Semantic Search" icon="sparkles" href="/guides/search/semantic-search/overview">
    Learn what Semantic Search finds and where to use it.
  </Card>

  <Card title="Search Past Agent Work" icon="terminal" href="/learn/search-past-agent-work">
    Practice semantic search with known checkpoints and queries.
  </Card>
</CardGroup>