Session Search
Session Search lets Anyy look through earlier conversation history in the current session scope. It is useful for recalling decisions, references, and unfinished threads without copying an entire transcript into persistent memory.
Search from Chat
Ask naturally:
Search my earlier sessions for the discussion about the release checklist.
Show my three most recent prior conversations.
With no query, Anyy lists recent sessions. With a query, it searches messages and groups matches by session.
Available Filters
| Input | Behavior |
|---|---|
| Query | Optional text search; omit it for recent sessions |
| Role filter | Optional comma-separated roles such as user, assistant, or tool_result |
| Limit | 1–5 sessions; default 3 |
Results always report the current session ID so you can distinguish the active conversation from prior matches. Tool-sourced sessions and child sessions are excluded from the recent-session view.
Continue the Right Conversation
Search helps locate a session; Conversations & Sessions explains how to inspect, switch, or continue one from supported surfaces. Check the session ID before resuming when several conversations have similar titles.
Names, filenames, decisions, and unusual phrases work better than generic terms such as “the task” or “yesterday.”
Session Search vs. Memory
- Use Session Search to recover what was said.
- Use Persistent Memory for a curated fact that should affect future answers.
- Use Tasks for structured obligations.
Do not save a full transcript to memory just to make it searchable; conversation history already serves that purpose.
Privacy and Scope
Search is read-only and limited to the current session scope. A result preview is bounded, so ask Anyy to open or summarize the matching session when you need more context.
Troubleshooting
| Problem | Fix |
|---|---|
| No relevant result | Use a distinctive phrase or remove an overly narrow role filter |
| Expected session is missing | Confirm you are using the correct Profile, Role, and Workspace context |
| Preview lacks needed detail | Continue or inspect the matched session rather than widening memory |
| Too many similar results | Add a filename, person, date, or decision phrase to the query |