> ## Documentation Index
> Fetch the complete documentation index at: https://docs.entire.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Search Past Work and Code

> Find the context behind past agent work and exact text in indexed source files.

## Before You Start

Use a test repository that:

* Is [mirrored to Entire](/learn/mirror-a-github-repository)
* Has [checkpoint capture set up for your agent](/guides/checkpoints/capture-checkpoints)
* Can be committed and pushed to its remote

Make sure you are [logged in to Entire](/cli-reference/login).

## Create Searchable Work

Run your agent from the repository. After it completes each prompt, commit and push the change before moving on. If Entire asks whether to link the commit to the session context, choose `yes` or `always`. Each linked commit creates a separate checkpoint.

First, ask:

```text theme={null}
Build a simple mission tracker using the repository's existing language and
framework. Users should be able to add a mission with a name, launch site,
target orbit, and status, then view their missions in a list.
```

Commit and push the change:

```shell theme={null}
git add .
git commit -m "Build mission tracker"
git push
```

Next, ask:

```text theme={null}
Add a mission archive. Users should be able to archive a mission without
deleting it. Move archived missions into a separate section.
```

Commit and push the change:

```shell theme={null}
git add .
git commit -m "Add mission archive"
git push
```

Finally, ask:

```text theme={null}
Add mission readiness status to this project.

Choose score thresholds for Ready, Needs Review, and Hold. Explain why you chose
those thresholds, then implement them in a function named
getMissionReadinessStatus.
```

Commit and push the change:

```shell theme={null}
git add .
git commit -m "Add mission readiness status"
git push
```

Give Entire a couple of minutes to index all three changes.

## Find the Decision

Ask about the reasoning captured in the agent session:

```shell theme={null}
entire search "how did we decide whether a mission is ready to launch?"
```

Search can return the readiness-related checkpoints, sessions, and commits, including the agent's explanation of the thresholds.

## Find the Code

Search for the function in the indexed source:

```shell theme={null}
entire search --code "getMissionReadinessStatus"
```

Code Search returns the files and lines that contain the function name.

## Repeat the Search in entire.io

Run the same searches in the browser. Open **Search** from the sidebar in [entire.io](https://entire.io), enter the readiness question, and review the **Commits** and **Sessions** tabs. Then switch to the **Code** tab and search for `getMissionReadinessStatus`.

See [Search in entire.io](/guides/search/search-in-entire-io) for filters, sorting, and keyboard shortcuts.

## Continue With

> **[Search in entire.io](/guides/search/search-in-entire-io)**
>
> Search past work and source code in the browser.

> **[Search in the CLI](/guides/search/search-in-cli)**
>
> Learn about queries, filters, and script-friendly output.