From 995fd1b1e5964cd39071bd0ee21c28768b3aa71e Mon Sep 17 00:00:00 2001
From: hugocasa <hugo@casademont.ch>
Date: Wed, 30 Sep 2026 14:07:34 +0200
Subject: [PATCH] fix: the agent editor dialog's levels slide in built on the
 first visit

Warmed, as the evals pane's levels are, so settings and evals are mounted before the first
navigation rather than inside its transition. Evals are only in the strip where they can be
opened.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---
 .../components/flows/content/AgentEditorModal.svelte  | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/frontend/src/lib/components/flows/content/AgentEditorModal.svelte b/frontend/src/lib/components/flows/content/AgentEditorModal.svelte
index 69dec38fd2..642a2fa002 100644
--- a/frontend/src/lib/components/flows/content/AgentEditorModal.svelte
+++ b/frontend/src/lib/components/flows/content/AgentEditorModal.svelte
@@ -460,16 +460,19 @@
 					title="Deployed <> Unsaved agent changes"
 				/>
 			</div>
-			<!-- Two pages of one strip, so opening evals slides in from the right the way its own
-				     levels do. No `onNavigate`: the arrow keys belong to whichever pane is on screen,
-				     and evals answers them for its own levels. -->
+			<!-- One strip of pages, so a level slides in from the right the way evals' own levels do.
+			     No `onNavigate`: the arrow keys belong to whichever pane is on screen, and evals answers
+			     them for its own levels. Warmed, as those levels are: a page built on its first visit
+			     lands inside the transition and arrives empty. Evals only where they can be opened,
+			     since warming them loads them. -->
 			<PagedContent
+				warm
 				class="flex-1 min-h-0"
 				current={inEvals ? 'evals' : inSettings ? 'settings' : 'agent'}
 				pages={[
 					{ key: 'agent', content: agentPage },
 					{ key: 'settings', content: settingsPage },
-					{ key: 'evals', content: evalsPage }
+					...(draftOnly || readOnly ? [] : [{ key: 'evals', content: evalsPage }])
 				]}
 			/>
 		</div>