Search & Recall

Find the session where you already solved the problem instead of starting from scratch.

What gets indexed

Longhouse builds a full-text search index over every session it imports. The index covers:

Conversation messages — both user prompts and assistant responses
Tool calls and outputs — file edits, bash commands, search results, and every other tool the model used
Session metadata — project name, git branch, working directory, timestamps

Search from the browser

The timeline page has a search bar at the top. Type any keyword, file name, function name, error message, or natural language description. Results are ranked by relevance and recency.

Use the sidebar filters to narrow by date range, provider, or project.

Search from the API

terminal

curl "http://localhost:8080/api/agents/sessions?query=retry+logic"

The same search index powers the browser, CLI, and API. All three return the same results.

Recall

Recall is semantic search — it finds sessions by meaning, not just keywords. When you search for "how did I handle rate limiting," recall finds sessions where you solved rate limiting even if those exact words were never used.

terminal

longhouse-server recall "how did I handle auth token refresh"
longhouse-server recall "the session where I fixed the CI pipeline"

Recall vs. search: Search matches exact keywords. Recall matches meaning. Use search when you know the exact term; use recall when you remember what happened but not the words.

See also: the wall query, GET /api/agents/sessions/wall, returns active and recently active sessions across projects — a quick way to find what you or others are working on right now.

Tips

Search for file names to find sessions that touched specific code
Search for error messages to find how you solved similar issues before
Search for tool names like "Edit" or "Bash" to find sessions with specific types of work
Use project filters to scope results to a single codebase