Documentation Index

Fetch the complete documentation index at: https://docs.latitude.so/llms.txt

Use this file to discover all available pages before exploring further.

​

Saved Searches

A saved search is a reusable search query, filter set, or both. Save it once, then return to the same cohort from the Search landing page.

​

What a Saved Search Stores

Each saved search stores:

• A query: The text from the search bar, if any
• A filter set: The filters active when you saved, if any
• A name: A human-readable label

A saved search must include a query, filters, or both. “All errors in production this week” might use only filters; “jailbreak attempts” might use only a query. Saved searches are project-scoped. Two projects can have saved searches with the same name; they’re independent.

​

The Saved Searches Page

When no query is active, the Search landing page shows saved searches. Each row includes: Click a row to reopen the saved search with its query and filters restored.

​

Creating a Saved Search

1. Open Search and run a query, apply filters, or both.
2. Click Save search in the toolbar.
3. Give it a descriptive name and confirm.

Latitude reloads the Search page with the saved search active. The new entry appears in the saved searches table the next time you clear the search.

​

Assigning Ownership

Each saved search can be assigned to an organization member. Assignment is only an ownership signal: everyone can still see and open the search. To assign or reassign:

• Open the row’s actions menu and pick Assign to, or
• Click the assignee cell directly in the table and choose a member from the dropdown.

The Annotated / Total ratio shows the assignee how much of the cohort still needs review.

​

Renaming and Deleting

The row’s actions menu lets you assign, rename, or delete a saved search. Deleting removes only the bookmark; the underlying traces are not affected.

​

Editing a Saved Search

When you change the query or filters on a loaded saved search, Latitude shows two actions:

• Update saved search: Overwrite the saved search with the current query and filters.
• Save as new search: Keep the original and create a new saved search from the current state.

Use Update saved search for changes you want to keep, such as expanding the time range from 7 to 30 days. Use Save as new search when you want a sibling search, such as one that adds a model filter. The update action is disabled until there’s a change to save.

​

Workflows

​

Investigate a specific cohort

You’re investigating reports that the agent gets confused during multi-turn checkout flows.

1. Run a search like "checkout" and add a filter for metadata.flow = "checkout" and spanCount >= 5.
2. Save it as “Checkout flows over 5 steps”.
3. Assign it to yourself.
4. Work through the matches. Total shows the cohort size; Annotated shows review progress.

​

Watch for a recurring issue

You’ve resolved a tool-retry issue and want to make sure it doesn’t return.

1. Run a search filtered to the relevant tag or metadata.
2. Save it as “Tool retry regressions”.
3. Check it weekly; Last found shows when the latest matching trace appeared.

​

Share a cohort with a teammate

You’ve found interesting jailbreak attempts and want a teammate to review them.

1. Save the search.
2. Reassign it to the teammate.
3. They’ll see it with their avatar the next time they open Search.

​

What Saved Searches Don’t Do

Saved searches are bookmarks, not subscriptions. They don’t notify you, generate evaluation scores, or run background processing when a new trace matches. For automated detection that produces scores and feeds issue discovery, see Flaggers.

​

Next Steps

• Search Overview: How search itself works
• Flaggers: Automatic annotators for common failure categories
• Inline Annotations: Leave feedback on traces from your saved search
• Filters: The shared filter system used inside searches