Skip to main content
Search helps you find the context behind previous agent work. You can search from the CLI, in Entire.io, or from your agent with the search Skill. Search combines semantic matching with keyword matching, so you can find work by meaning, exact phrases, feature names, file names, or error text. In this tutorial, you will create a small app called Launch Log, make three agent-assisted commits, and search that history.

​
Prerequisites

Before you start, make sure you have:
  • Entire installed
  • An AI coding agent installed
  • Git configured for the project
  • An Entire account
Log in to Entire: 
entire login
You need to be logged in so search can return only repos and checkpoints you have access to.

​
Create a New Project

Create a Vite project: 
mkdir launch-log-search-demo
cd launch-log-search-demo
npm create vite@latest . -- --template vanilla-ts
npm install
Enable Entire for your agent. This example uses Codex: 
entire enable -y --agent codex
Replace codex with the agent you use. Start your agent: 
codex

​
Build the Starter App

Ask your agent: 
Build a small Launch Log app in this Vite project.

The app should track fictional space missions. Add a form with fields for mission name, launch site, target orbit, and mission status. Show submitted missions in a list.

Use the phrase "mission manifest" in the UI heading.
When the agent finishes, commit and push: 
git add .
git commit -m "Create launch log mission manifest"
git push
This gives you a clear phrase to search for later: mission manifest.

​
Add Readiness Scoring

Ask your agent: 
Add mission readiness scoring to Launch Log.

Each mission should have a readiness score from 0 to 100. Show a label that says Ready, Needs Review, or Hold based on the score.

Make the UI explain whether a mission is ready to launch.
Commit and push: 
git add .
git commit -m "Add mission readiness scoring"
git push
This gives you history that can be found by meaning, even if your search does not use the exact commit message.

​
Add an Archive

Ask your agent: 
Add a mission archive.

Users should be able to archive a mission without deleting it. Archived missions should move out of the main mission list into a separate archived section.
Commit and push: 
git add .
git commit -m "Add mission archive"
git push
This gives you another feature to search for from the CLI, Entire.io, or your agent.

​
Wait for Indexing

After your final git push, give Entire a couple minutes to index the pushed checkpoints. Then confirm you are still in an Entire-enabled repo: 
entire status

​
Search by Exact Phrase

Search for the phrase you asked your agent to add: 
entire search "mission manifest"
Exact phrase searches are useful when you remember a UI label, feature name, file name, error message, or specific wording from the work.

​
Search by Meaning

Now search without using the exact commit message or heading: 
entire search "how did we decide whether a mission is ready to launch?"
Search should find the readiness scoring work because the query describes the meaning of the change, not just its exact words.

​
Search in Entire.io

You can also search from Entire.io. Go to entire.io, sign in, choose Search in the sidebar, and search for: 
mission manifest
Search results can include related checkpoints, sessions, and commits. Open a result to inspect the captured agent work, code changes, and surrounding context.

​
Search from Your Agent

If you have Skills installed, your agent can search history for you. Open your agent and ask: 
/search where did we move old missions out of the main list
The search Skill uses entire search, summarizes likely matches, and helps your agent decide what context to inspect next.

​
Search Across Repos

If you have access to multiple Entire-enabled repos with indexed checkpoints, search across them: 
entire search "repo:* mission readiness"
Cross-repo search is useful when you remember the topic, but not which repo the work happened in.