UI Inconsistencies with JS file and Workspace

[ganesh-bruno]

I have checked the following:

• I have searched existing issues and found nothing related to my issue.

This bug is:

• making Bruno unusable for me
• slowing me down but I'm able to continue working
• annoying
• this feature was working in a previous version but is broken in the current release.

JIRA

Bruno version

3.4.1

Operating System

Mac

Describe the bug

Observed a couple of UI inconsistencies in Bruno v3.4.0 related to workspace handling and file synchronization.

Issue 1: Deleted JS files still visible in Bruno UI

Steps to Reproduce:

1. Create or open a JS file inside a Bruno collection/workspace
2. Delete the file directly from the file system
3. Return to Bruno UI

Actual Result

The deleted JS file is still visible in the Bruno sidebar/UI even though it no longer exists on the file system. Only restart is a workaround.

Expected Result

Bruno should automatically refresh/sync the workspace state and remove deleted files from the UI.

Screen.Recording.2026-05-22.at.6.21.06.PM.mov

Issue 2: Workspace switch toast appears unnecessarily

Steps to Reproduce:

1. Open a workspace
2. Click on the same currently active workspace again

Actual Result

A workspace switch toast/notification is displayed even though the user is already inside the selected workspace.

Expected Result

No toast or workspace switch action should occur when clicking the currently active workspace.

Screen.Recording.2026-05-22.at.6.22.28.PM.mov

.bru file to reproduce the bug

NA

Screenshots/Live demo link

NA

[coderabbitai]

🔗 Related PRs

#6457 - fix: duplicate message on workspace rename and close [merged]
#6574 - fix: collection already opened in other workspace [merged]
#6677 - fix: rename requests double notifications [merged]
#7750 - fix: make "Remove Collection" consistent with "Remove Workspace" [merged]
#7883 - fix: show whitespace-only error on Create workspace and collection modal [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[DeviSriSaiCharan]

Hi @sanish-bruno , I checked both issues and I would like to work on them. Could you please assign them to me?

Issue 1: Deleted JS files still visible in Bruno UI

Current Behavior

From the current implementation, unlink events are handled only for request-related files (.bru and .yml).

• collection-watcher.js sends unlink events only for supported request files.
• hasRequestExtension currently allows only .bru and .yml.
• The renderer already handles unlink events correctly and removes items from Redux/state.

This means auto-removal already works for:

• Request files
• Environment files
• Folders

But arbitrary .js files are not part of this sync pipeline, so deleting them from disk will not trigger sidebar/UI updates.

Proposed Fix

I plan to extend the watcher flow so the UI refreshes correctly when supported JS-related files are deleted, instead of requiring an app restart.

Doubt

When I tested this locally, I created a .js file directly inside the collection folder and reopened the collection, but the file was not shown in the Bruno sidebar/UI at all.

Could you please clarify how the .js file becomes visible inside Bruno before deletion? Are there any specific steps to reproduce that part? @ganesh-bruno

---

Issue 2: Workspace Toast Fix

Current Behavior

Right now, the success toast ("Switched to...") is shown even when the user selects the already active workspace. Also, the switchWorkspace action still runs snapshot reset and hydration logic even when no actual workspace change happens.

Proposed Fix

My plan is to:

• Add a check inside switchWorkspace to return early if the selected workspace is already active.
• Update handleWorkspaceSwitch to show the success toast only when the workspace actually changes.
• Apply the same check in handleOpenWorkspace so navigation and toast only happen after a real switch.

This will avoid unnecessary background work and make the UI feedback more accurate.