src/patches/agentsMd.ts (1)

159-177: Consider making the fallback pattern more specific.

The fallback pattern /(\})(}catch)/ is quite generic and could potentially match unintended locations within the function body if there are nested structures with }}catch. While limiting the search to file.slice(funcStart) helps, a more specific pattern could improve robustness.

That said, given the documented examples and that this is a fallback for older CC versions, this may be acceptable as-is if it works reliably in practice.

src/ui/components/ClaudeMdAltNamesView.tsx (1)

70-82: Stale closure on delete index adjustment.

After updateSettings removes an item, altNames still reflects the old state within this render cycle. The adjustment logic on lines 79-81 uses altNames.length - 1 (the pre-deletion length), which may set selectedIndex one position higher than intended.

For example, if you have 3 items and delete the last one (index 2), altNames.length - 1 is still 2, so selectedIndex >= 2 is true, and it gets set to Math.max(0, 3 - 2) = 1, which is correct. However, the logic is fragile if the timing changes.

Consider using the length after deletion for clarity:

♻️ Suggested improvement

     } else if (input === 'd') {
       // Delete
       if (altNames.length > 0) {
+        const newLength = altNames.length - 1;
         updateSettings(s => {
           if (!s.claudeMdAltNames) return;
           s.claudeMdAltNames = s.claudeMdAltNames.filter(
             (_, index) => index !== selectedIndex
           );
         });
-        if (selectedIndex >= altNames.length - 1) {
-          setSelectedIndex(Math.max(0, altNames.length - 2));
+        if (selectedIndex >= newLength) {
+          setSelectedIndex(Math.max(0, newLength - 1));
         }
       }