v0.5.41

Highlights

A retrieval inside a tool call is now one step, in the timeline and for the judges. With Open WebUI v0.12.4.10, every content-reading tool emits execute_tool with a retrieval span for the same call inside it (the GenAI tracing standard). Studio recognises that pair by span structure alone, so the same applies to any framework that nests retrieval in a tool call.

Trajectory timeline

• One row per lookup: the tool's arguments plus the retrieved documents. A 5-turn agent run went from 22 rows to 16.
• Finding and judge links to the retrieval span open that row.
• A retrieval outside any tool call (for example memory recall) keeps its own row.

Judges

• Main judge: when the nested retrieval has documents, the tool result is replaced by a pointer to them, so the same content is not sent twice. A tool result with no documents (for example "No matches") is kept.
• Semantic agentic judge:
  • The 25-step evidence cap counts tool steps only. Before, model calls, retrievals and workflow spans counted too, so a long run could drop its later tool calls and be marked truncated.
  • Retrieved sources are listed by name, without also listing the same file by ID.