AnoobFeng 5ddf698895

fix(frontend): reset new chat on client-side navigation (#3673) ...

* fix(frontend): reset new chat on client-side navigation

Drive the chat reset effect with Next.js's reactive pathname instead of the render-time window.location-derived flag.

During App Router transitions, window.location may still point to the previous thread until commit, leaving chat state stale until another UI interaction triggers a render. Preserve the stale 'new' param guard so created thread UUIDs are not overwritten.

* test(frontend): add e2e to cover history-only new chat reset

* docs(frontend): clarify new chat pathname synchronization

2026-06-21 11:44:36 +08:00

..

e2e

fix(frontend): reset new chat on client-side navigation (#3673)

2026-06-21 11:44:36 +08:00

e2e-real-backend

fix: align auth-disabled mode and mock history loading (#3471)

2026-06-10 16:11:00 +08:00

e2e-record

fix(replay-e2e): match by conversation, not the living system prompt (#3436)

2026-06-08 17:32:41 +08:00

unit

feat: support regenerating latest answer (#3637)

2026-06-20 18:59:42 +08:00