Search Conversation Tool

What is it?

The Search Conversation tool lets Yukkai search through your entire, uncompacted conversation history — every message ever sent in the current session, including tool outputs, file contents, and code snippets that may have been trimmed or summarized during automatic compaction.

As conversations grow long, Yukkai automatically compacts older parts of the conversation to save memory. This is normal and keeps things running smoothly — but it means some details (like a specific error message or a file's content) can be lost from the active context. The Search Conversation tool recovers those details on demand.

Think of it as a search engine for your chat history — it digs into the original, unmodified log so nothing is truly gone.

How it works

When you ask Yukkai about something that was discussed earlier but seems to have been forgotten, Yukkai can use this tool to:

1. Search the full conversation log — the complete, unfiltered history of every message and tool output in the session.
2. Find matching results using natural-language search — you don't need exact keywords; just describe what you're looking for.
3. Return the relevant excerpts so the information is back in context and Yukkai can act on it.

Key concept: Compaction vs. the full log

	Compacted summary	Full conversation log
What it is	A condensed version of older messages	The original, word-for-word messages
Used for	Day-to-day context in long chats	Deep search when details are needed
Searchable?	No (it's a summary)	✅ Yes — via this tool

Even if something has been compacted out of the active summary, it still exists in the full log and can be found with this tool.

How to use it

You don't need to invoke this tool directly — Yukkai uses it automatically when it detects that you're asking about something from earlier in the conversation that may no longer be in active context. However, you can also nudge Yukkai to use it:

Parameters

Parameter	Required	Description	Default
query	✅ Yes	A natural-language description of what you're looking for (minimum 3 characters)	—
max_results	No	Maximum number of results to return (max: 20)	5

What to say

You can simply reference something from earlier in the chat:

• "What was the error from the build command earlier?"
• "Can you find that file content we looked at before?"
• "Search the conversation for the output of the last test run."

Yukkai will automatically search the full history and bring the relevant details back.

Examples

Example 1: Recovering a lost error message

You: "What was the exact error we got when running the tests earlier?"

Yukkai searches the full log and finds:

Tests failed: 2
  - testUserCreation(): expected 200, got 500
  - testLoginFlow(): timeout after 30s

Example 2: Finding a file's content

You: "Can you check what was in the config file we read a while ago?"

Yukkai searches for "config file" and recovers the exact content from earlier in the conversation — even if the active summary has been compacted.

Example 3: Searching for a specific command output

You: "Search our conversation for the grep output."

Yukkai runs a search with query: "grep output" and max_results: 10, returning the original tool output that may have been summarized away.

Tips & best practices

• Be descriptive in your search. Natural language works well — "the Swift compilation error from earlier" is better than just "error".
• Use it before giving up. If Yukkai says "I don't have that anymore," a conversation search may still find it in the full log. Ask Yukkai to search the conversation first.
• More results for broader searches. If your search is vague, increase max_results (up to 20) to surface more potential matches.
• Exact matches aren't required. The search is semantic — it understands meaning, not just keywords. "the build failure" will also match "compilation error."
• Best for long sessions. In short conversations, compaction rarely kicks in. This tool shines in extended sessions where a lot of information has been exchanged and older context has been summarized.
• It searches within the current session only. The full log covers the current conversation — not past sessions or other chats.