Bug: Embedding traces incorrectly shown with chat UI in trace drawer

[mmabrouk]

Description

Embedding traces are being rendered with the chat UI (chat bubbles/messages) in the trace drawer, which is incorrect. Embeddings are not conversational and should be displayed differently.

Expected Behavior

Embedding traces should show a raw data view — displaying the embedding input and output as raw data, not as chat messages.

Actual Behavior

Embedding traces display with chat bubbles/messages UI, which is confusing and inappropriate for embedding data.

Severity

Low — confusing but data is still visible

Steps to Reproduce

1. Make an embedding API call that gets traced
2. Open the trace in observability
3. Open the trace drawer
4. Embedding is shown with chat UI instead of raw data view

[linear]

AGE-3611

[dosubot]

The root cause is that the OverviewTabItem component decides to render chat UI based only on the data structure (e.g., if inputs.prompt or outputs.completion are arrays of objects with a 'role' property), not on the trace node type. This means embedding traces that happen to have similar data structures are incorrectly shown with chat bubbles.

To fix this, update OverviewTabItem to check if activeTrace.node.type === 'chat' before rendering chat UI. For all other types—including 'embedding'—always render the inputs and outputs as raw data, regardless of their structure. The node type is already available in the component, so this change is straightforward and aligns with Agenta's intended UI behavior for different span kinds (docs).

This approach will ensure embedding traces are always shown as raw data, while chat traces keep their specialized formatting.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[Vishesh-Paliwal]

Hey @mmabrouk , would like to raise a quick PR for this .
to confirm , the part looking wrong is this bubble appearing for embedding right , which I feel can be removed :

or does something inside the actual trace drawer also looks weird ?

[mmabrouk]

No that is not the issue. The issue is that the embedding spans are considered as chat, as a result the inputs and the outputs are shown as collapsible chat messages when you open the span. They should instead be shown as two collapsibles with input/output.

Let me know if it makes sense.

I'd chat with the Agent to determine where we process the spans and the different ways we process them in the trace drawer. And then determine how we determine that a chat span is a chat span, what are the conditions there. And find why are we showing spans of type embeddings as chat.

[mmabrouk]

Assigned to you @Vishesh-Paliwal

[Vishesh-Paliwal]

so basically , this as in prod :

should look something like this right ( raw data ) :

let me know if understood wrong again 😅

[mmabrouk]

That is exactly it!

[Vishesh-Paliwal]

cool , have linked the PR already 👍