From a86f0c310b8c7aaa9ecee80b378e9d4130cb629f Mon Sep 17 00:00:00 2001
From: Jinjing <6427696+AmethystLiang@users.noreply.github.com>
Date: Sun, 19 Jul 2026 16:11:58 -0700
Subject: [PATCH] Use flex/gap instead of space-y for fieldset spacing

space-y margins use :where() (zero specificity), so m-0 on nested
fieldsets collapses the gap. flex flex-col with gap-8 maintains
proper spacing between sections.
---
 .../src/components/settings/AgentCatalogSectionView.tsx      | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/renderer/src/components/settings/AgentCatalogSectionView.tsx b/src/renderer/src/components/settings/AgentCatalogSectionView.tsx
index ffae0e4e78e..e7e89c7272d 100644
--- a/src/renderer/src/components/settings/AgentCatalogSectionView.tsx
+++ b/src/renderer/src/components/settings/AgentCatalogSectionView.tsx
@@ -175,7 +175,10 @@ export function AgentCatalogSectionView({
   }
 
   return (
-    <div className="space-y-8">
+    // Why: gap (not space-y) — the default fieldset uses m-0, and Tailwind v4's
+    // space-y margins are :where() (zero specificity) so m-0 would collapse the
+    // gap between Default agent and Agents.
+    <div className="flex flex-col gap-8">
       {/* Why: read-only disabling is scoped per control group (not one pane-wide
           fieldset) so the catalog search box stays usable on paired clients. */}
       <fieldset disabled={readOnly} className="m-0 min-w-0 border-0 p-0">