Unlike Saved Views, which store table settings, custom views reshape the underlying data.
Where you can create a custom view
Custom views use the data already available on each surface:Create a view
Open Customize Tabs on a trace and click Create Custom View to generate a view with Alyx.
1
Start
From a trace or session, open Customize Tabs and click Create Custom View. From a labeling-queue record, click +. You can also open Alyx directly (Cmd+L / Ctrl+L) and ask it to create a view.
2
Describe the layout you want
Tell Alyx what you want to see, in plain language. Be specific about the data and the shape: a list, a table, a chat transcript, or side-by-side panels.
3
Preview and refine
Adjust the live preview until it looks right. Nothing is saved until you click Accept.
4
Accept, manage, and share
Click Accept to add the tab. In Customize Tabs, you can edit the view or show and hide its tab. You can rename or delete views you created; org admins can also delete published views. Creators who are org admins can select Visible to everyone to publish a view. The creator or an org admin can unpublish it. For labeling queues, the creator or an org admin can select Show on all queues. Tab visibility is browser-specific and applies only to you.
What to ask Alyx
Name the data and layout you want:- Trace: “Show all tool calls with their inputs and outputs.” You can also request a conversation, side-by-side comparison, span timeline with errors highlighted, or sortable table of LLM latency, tokens, and cost.
- Session: “Show each turn as a chat bubble with its latency.” Other useful layouts include a trace table with status, duration, and token counts or a running token-usage total.
- Labeling queue: “Put the model output beside the annotation rubric.” You can also ask Alyx to turn the record’s columns into a scannable card.
Refining a view: ask Alyx to edit an existing custom view to also show cost per span.
Good to know
- Nothing saves until you accept. Refine a preview as much as you want before committing it.
- Views can only show available data. Trace inputs and outputs belong to the selected span; session views receive them for every span. If requested data is unavailable, Alyx suggests what it can show.
- New views are personal by default. Their creator must be an org admin to publish them.
- Controls are display-only. They can search, sort, filter, expand, collapse, or select a span, but cannot write data, record feedback, or submit annotations. Labeling-queue views are read-only.