Agents
🔎 Announced at Interrupt: AI Search in LangSmith You used to need an evaluator or read hours of conversations to find traces that answer qu…
🔎 Announced at Interrupt: AI Search in LangSmith You used to need an evaluator or read hours of conversations to find traces that answer questions such as: 💬 Does the user seemed frustrated?' 💬 Where
🔎 Announced at Interrupt: AI Search in LangSmith You used to need an evaluator or read hours of conversations to find traces that answer questions such as: 💬 Does the user seemed frustrated?" 💬 Where did the agent fail to complete the task? 💬 Where is the user trying to cancel their subscription? Now, just describe it. LangSmith returns the traces where it happened. https://www.langchain.com/blog/agent-traces-ai-search-langsmith Media
Related
- Just announced at Interrupt! SmithDB. Agent traces have outgrown the databases built to hold them. That’s why we built SmithDB, a purpose-bu…
- Observability going from 'read the traces' to 'the traces read themselves and tell you what to fix.' That's the feedback loop most agent tea…
- Much of the valuable information in agent traces isn’t directly filterable with existing techniques like full text search or metadata filter…
- LangSmith Engine is a phase shift because traces are no longer just records to be manually inspected, they’re now the catalyst for recursive…
Source: Harrison Chase (X) | 2026-10-13