5d4fd9cf72
- Use router.replace() instead of history.replaceState() so Next.js router's internal state is updated on chat start. This ensures subsequent "New Chat" clicks are treated as a real cross-route navigation (actual-id → "new") rather than a no-op same-path navigation, which was causing stale content to persist. - In ChatLayout, increment the SubtasksProvider key only when navigating TO "new" from a non-"new" route. This forces a full remount for a fresh new-chat state without remounting when the URL transitions from "new" → actual-id (which would interrupt streaming). Made-with: Cursor Co-authored-by: DanielWalnut <45447813+hetaoBackend@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| app | ||
| components | ||
| core | ||
| hooks | ||
| lib | ||
| server/better-auth | ||
| styles | ||
| typings | ||
| env.js | ||