src/renderer/store/slices/sessionDetailSlice.ts (1)

589-610: Nit: Redundant reassignment on line 592.

oldGroupIds is immediately assigned from prevGroupIds, which is already a const in scope. You can use prevGroupIds directly in the filter predicate.

♻️ Simplified diff

       // Auto-expand newly arrived AI groups if the setting is enabled.
       // Uses prevGroupIds snapshotted before set() so the diff is accurate.
       if (get().appConfig?.general?.autoExpandAIGroups) {
-        const oldGroupIds = prevGroupIds;
         const newGroupIds = newConversation.items
           .filter(
             (item) =>
               item.type === 'ai' &&
-              !oldGroupIds.has((item as { type: 'ai'; group: { id: string } }).group.id)
+              !prevGroupIds.has((item as { type: 'ai'; group: { id: string } }).group.id)
           )
           .map((item) => (item as { type: 'ai'; group: { id: string } }).group.id);

The overall differential expansion logic is correct — it properly preserves user-collapsed groups while auto-expanding only newly arrived AI responses during live sessions. Based on learnings: "Use tabUISlice to maintain independent UI state per tab with expandedAIGroupIds... keyed by tabId to prevent UI state from one tab affecting another."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/renderer/store/slices/sessionDetailSlice.ts` around lines 589 - 610,
Remove the redundant local assignment oldGroupIds = prevGroupIds and use
prevGroupIds directly in the filter predicate; update the filter/map logic that
computes newGroupIds to reference prevGroupIds instead of oldGroupIds so the
behavior of the auto-expand block (get().appConfig?.general?.autoExpandAIGroups,
latestAllTabs, expandAIGroupForTab) is unchanged but without the unnecessary
reassignment.

src/renderer/components/settings/sections/GeneralSection.tsx (1)

30-30: Consider narrowing the type to only boolean keys of AppConfig['general'].

The current signature accepts any key from AppConfig['general'], but value is typed as boolean. Since AppConfig['general'] includes non-boolean properties (theme, defaultTab, claudeRootPath), this allows invalid calls like onGeneralToggle('theme', true) to pass type checking.

♻️ Proposed type-safe alternative

+type BooleanGeneralKeys = {
+  [K in keyof AppConfig['general']]: AppConfig['general'][K] extends boolean ? K : never;
+}[keyof AppConfig['general']];
+
 interface GeneralSectionProps {
   readonly safeConfig: SafeConfig;
   readonly saving: boolean;
-  readonly onGeneralToggle: (key: keyof AppConfig['general'], value: boolean) => void;
+  readonly onGeneralToggle: (key: BooleanGeneralKeys, value: boolean) => void;
   readonly onThemeChange: (value: 'dark' | 'light' | 'system') => void;
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/renderer/components/settings/sections/GeneralSection.tsx` at line 30, The
onGeneralToggle signature accepts any key of AppConfig['general'] but the value
is always boolean, allowing invalid calls for non-boolean fields; narrow the key
type to only those keys whose AppConfig['general'] value is boolean by changing
the type of the first parameter to the extracted boolean keys (e.g. use a
conditional mapped type like { [K in keyof AppConfig['general']]:
AppConfig['general'][K] extends boolean ? K : never }[keyof
AppConfig['general']] or Extract<keyof AppConfig['general'], ... boolean
check>), keeping the value as boolean so onGeneralToggle only accepts boolean
properties of AppConfig['general'] (referencing onGeneralToggle and
AppConfig['general']).

src/renderer/store/slices/sessionDetailSlice.ts (2)

566-572: Consider using a type guard for cleaner type narrowing.

The filter already checks item.type === 'ai', but the subsequent map still requires a type assertion. A small type guard could simplify this pattern throughout the file.

♻️ Optional: Extract a type guard helper

+const isAIItem = (item: { type: string }): item is { type: 'ai'; group: { id: string } } =>
+  item.type === 'ai';
+
 const prevGroupIds = new Set(
   (latestState.conversation?.items ?? [])
-    .filter((item) => item.type === 'ai')
-    .map((item) => (item as { type: 'ai'; group: { id: string } }).group.id)
+    .filter(isAIItem)
+    .map((item) => item.group.id)
 );

As per coding guidelines: "Use TypeScript type guards with isXxx naming convention for runtime type checking."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/renderer/store/slices/sessionDetailSlice.ts` around lines 566 - 572,
Introduce a TypeScript type guard named isAIItem (e.g., function isAIItem(item):
item is { type: 'ai'; group: { id: string } }) and use it to replace the
filter+type assertion when building prevGroupIds: call
(latestState.conversation?.items ?? []).filter(isAIItem).map(i => i.group.id).
Update any other similar patterns in this file to use the same isAIItem guard so
you can remove the manual (item as ...) assertions and achieve cleaner type
narrowing.

---

592-613: Redundant variable assignment on line 595.

oldGroupIds is assigned directly from prevGroupIds without modification. Consider using prevGroupIds directly to reduce noise.

♻️ Suggested simplification

       // Auto-expand newly arrived AI groups if the setting is enabled.
       // Uses prevGroupIds snapshotted before set() so the diff is accurate.
       if (get().appConfig?.general?.autoExpandAIGroups) {
-        const oldGroupIds = prevGroupIds;
         const newGroupIds = newConversation.items
           .filter(
             (item) =>
               item.type === 'ai' &&
-              !oldGroupIds.has((item as { type: 'ai'; group: { id: string } }).group.id)
+              !prevGroupIds.has((item as { type: 'ai'; group: { id: string } }).group.id)
           )
           .map((item) => (item as { type: 'ai'; group: { id: string } }).group.id);

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/renderer/store/slices/sessionDetailSlice.ts` around lines 592 - 613, The
assignment oldGroupIds = prevGroupIds is redundant; update the code to use
prevGroupIds directly in the filter (remove oldGroupIds variable) where
newGroupIds is computed, keeping the rest of the logic unchanged (references:
prevGroupIds, newConversation.items, latestAllTabs, expandAIGroupForTab,
get().appConfig.general.autoExpandAIGroups). Ensure you only replace oldGroupIds
with prevGroupIds in that block and remove the unused declaration.

CHANGELOG.md (1)

11-12: Remove extra blank line for consistency.

Two blank lines appear after the new entry, while the rest of the changelog uses single blank lines between entries.

🧹 Proposed fix

 - `general.autoExpandAIGroups` setting: automatically expands all AI response groups when opening a transcript or when new AI responses arrive in a live session. Defaults to off. Stored in the on-disk config so it persists across restarts.
-

 - Strict IPC input validation guards for project/session/subagent/search limits.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 11 - 12, Remove the extra blank line after the new
changelog entry in CHANGELOG.md so entries use a single blank line separator;
locate the latest release/entry block (the newly added entry) and delete one of
the two consecutive newline lines immediately following it to match the rest of
the file's formatting.