_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

• 📝 Generate docstrings

src/tui/components/SettingsView.tsx (1)

80-81: Fallback to config.agents?.[0]?.name could return a value absent from the agents options list.

If the first configured agent name doesn't match any entry in the agents string[] prop (e.g., due to a typo or a plugin that failed to register), getValue returns a value not present in options. The select cycling logic handles this gracefully (indexOf returns -1, cycling starts from index 0), so there's no crash — but the UI would briefly show the unrecognised name before the user cycles.

This is a minor edge case; no action needed unless you want to add a guard.

src/commands/run.tsx (1)

1125-1148: availableAgentNames memo recomputes every render because availableAgents is unstable.

agentRegistry.getRegisteredPlugins() (line 1127) is called directly in the render body and likely returns a new array reference each time. Since availableAgents is in the dependency array of the availableAgentNames memo (line 1147), the memo never caches effectively.

Consider wrapping the plugin list in its own useMemo or computing everything in a single memo:

Suggested consolidation

-  const availableAgents = agentRegistry.getRegisteredPlugins();
   const availableTrackers = trackerRegistry.getRegisteredPlugins();
-  const configuredAgentNames = useMemo(
-    () =>
-      Array.from(
-        new Set(
-          (storedConfig?.agents ?? [])
-            .map((agent) => agent.name)
-            .filter((name): name is string => typeof name === 'string' && name.length > 0),
-        ),
-      ),
-    [storedConfig?.agents],
-  );
-  const availableAgentNames = useMemo(
-    () =>
-      Array.from(
-        new Set(
-          [...availableAgents.map((agent) => agent.id), ...configuredAgentNames],
-        ),
-      ),
-    [availableAgents, configuredAgentNames],
-  );
+  const availableAgentNames = useMemo(
+    () =>
+      Array.from(
+        new Set([
+          ...agentRegistry.getRegisteredPlugins().map((agent) => agent.id),
+          ...(storedConfig?.agents ?? [])
+            .map((agent) => agent.name)
+            .filter((name): name is string => typeof name === 'string' && name.length > 0),
+        ]),
+      ),
+    // agentRegistry contents are stable after initialisation;
+    // only storedConfig?.agents changes at runtime (settings save).
+    [storedConfig?.agents],
+  );

This keeps availableAgents (now only used for trackers) out of the dependency array and avoids the redundant intermediate memo. If the registry can genuinely change at runtime, add a trigger signal instead.

• X
• Mastodon
• Reddit
• LinkedIn

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.