Skip to content

fix(web): discard unsaved profile changes before navigation - #460

Draft
youngbeom-shin wants to merge 2 commits into
mainfrom
main__fix-unsaved-agent-navigation
Draft

fix(web): discard unsaved profile changes before navigation#460
youngbeom-shin wants to merge 2 commits into
mainfrom
main__fix-unsaved-agent-navigation

Conversation

@youngbeom-shin

@youngbeom-shin youngbeom-shin commented Aug 7, 2026

Copy link
Copy Markdown
Member

Summary

  • discard unsaved agent profile changes before blocked navigation proceeds
  • allow the newly selected agent profile to load after the user confirms leaving
  • add regression coverage for switching between agent profiles with an unsaved model change

@youngbeom-shin

Copy link
Copy Markdown
Member Author

Fixes:

  1. When an agent profile has unsaved changes, confirming the leave prompt now correctly switches to the selected agent. The sidebar selection and displayed profile remain synchronized.
  2. Fixed the confirmation dialog appearing twice. Only one confirmation is now required to complete the navigation.
  3. Added regression coverage for switching agents after making an unsaved model change.

Verification:

  • Unsaved changes correctly trigger the leave confirmation.
  • Clicking “Confirm” once successfully switches agents.
  • The newly selected agent’s profile loads correctly.
  • Clicking “Cancel” keeps the current profile and unsaved changes intact.
  • Targeted tests and the complete frontend check pass.

Test recording:

2026-08-07.17.14.44.mov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant