fix(web): remove router.refresh() after router.push() to fix Next.js 16 navigation (#974)

* fix(web): remove router.refresh() after router.push() to fix Next.js 16 navigation

In Next.js 16, the prefetch cache and navigation system was completely
rewritten. Calling router.refresh() immediately after router.push() creates
a race condition where the cache invalidation interrupts the in-flight
navigation, causing the page to not load.

Removed the router.refresh() calls from:
- useCreateNewChatThread.ts
- chatName.tsx
- chatSidePanel.tsx
- inviteMemberCard.tsx

Also documents this pattern in CLAUDE.md to prevent future regressions.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* chore: update CHANGELOG for #974

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: brendan-kellam

CHANGELOG.md

@@ -14,6 +14,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 - Preserve regex and case sensitivity query parameters when loading more search results. [#972](https://github.com/sourcebot-dev/sourcebot/pull/972)
+- Fixed page navigation failing after Next.js 16 upgrade by removing `router.refresh()` calls immediately following `router.push()`. [#974](https://github.com/sourcebot-dev/sourcebot/pull/974)
 
 ## [4.13.1] - 2026-02-28
 

CLAUDE.md

@@ -182,6 +182,21 @@ export const GET = apiHandler(async (request: NextRequest) => {
 });
 ```
 
+## Next.js Router Navigation
+
+Do NOT call `router.refresh()` immediately after `router.push()`. In Next.js 16, the prefetch cache and navigation system was completely rewritten, and calling `router.refresh()` right after `router.push()` creates a race condition — the refresh invalidates the cache and can interrupt the in-flight navigation, leaving the page stuck or not loading.
+
+```ts
+// Bad - router.refresh() races with router.push() in Next.js 16
+router.push(url);
+router.refresh(); // ❌ can cancel the navigation
+
+// Good - if navigating to a new route, the page will fetch fresh data on load
+router.push(url); // ✅
+```
+
+If you need to refresh server component data after a mutation, use the server-side `refresh()` from `next/cache` in a Server Action instead of `router.refresh()` on the client.
+
 ## Docs Images
 
 Images added to `.mdx` files in `docs/` should be wrapped in a `<Frame>` component:

packages/web/src/app/[domain]/chat/components/chatName.tsx

@@ -61,7 +61,6 @@ export const ChatName = ({ name, id, isOwner = false, isAuthenticated = false }:
                 description: `✅ Chat deleted successfully`
             });
             router.push(`/${SINGLE_TENANT_ORG_DOMAIN}/chat`);
-            router.refresh();
             return true;
         }
     }, [id, toast, router]);

packages/web/src/app/[domain]/chat/components/chatSidePanel.tsx

@@ -115,7 +115,6 @@ export const ChatSidePanel = ({
                 router.push(`/${SINGLE_TENANT_ORG_DOMAIN}/chat`);
             }
 
-            router.refresh();
             return true;
         }
     }, [chatId, router, toast]);

packages/web/src/app/[domain]/settings/members/components/inviteMemberCard.tsx

@@ -68,7 +68,6 @@ export const InviteMemberCard = ({ currentUserRole, isBillingEnabled, seatsAvail
                 } else {
                     form.reset();
                     router.push(`?tab=invites`);
-                    router.refresh();
                     toast({
                         description: `✅ Successfully invited ${data.emails.length} members`
                     });

packages/web/src/features/chat/useCreateNewChatThread.ts

@@ -54,7 +54,6 @@ export const useCreateNewChatThread = ({ isAuthenticated = false }: UseCreateNew
         const url = createPathWithQueryParams(`/${SINGLE_TENANT_ORG_DOMAIN}/chat/${response.id}`);
 
         router.push(url);
-        router.refresh();
     }, [router, toast, setChatState]);
 
     const createNewChatThread = useCallback(async (children: Descendant[], selectedSearchScopes: SearchScope[]) => {