[GH-ISSUE #3864] [bug]: Switching context doesn't invalidate environment variables and requests #1356

New issue

Open

opened 2026-03-16 19:58:07 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 19:58:07 +03:00

Owner

Originally created by @jobartim44 on GitHub (Feb 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3864

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I change my Workspace the environment variables are still set. I use generic variables along my different workspace and collections like <<base_url>> so this is source of mistake if they are not unset.

The same way I would like request tabs to be closed when switching my workspace.

Steps to reproduce

Configure différent workspaces with environment variables having the same name.
Swith workspace, don't select any environment, variables are still set.

Environment

Production

Version

Self-hosted

Originally created by @jobartim44 on GitHub (Feb 27, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3864 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I change my Workspace the environment variables are still set. I use generic variables along my different workspace and collections like <<base_url>> so this is source of mistake if they are not unset. The same way I would like request tabs to be closed when switching my workspace. ### Steps to reproduce Configure différent workspaces with environment variables having the same name. Swith workspace, don't select any environment, variables are still set. ### Environment Production ### Version Self-hosted

kerem added the

bug

need testing

labels

2026-03-16 19:58:07 +03:00

kerem commented

2026-03-16 19:58:18 +03:00

Author

Owner

@jobartim44 commented on GitHub (Feb 27, 2024):

If we close every tabs, we should have an empty panel. This is not possible at the moment we always need to have an open request atb.

@jobartim44 commented on GitHub (Feb 27, 2024): If we close every tabs, we should have an empty panel. This is not possible at the moment we always need to have an open request atb.

kerem commented

2026-03-16 19:58:23 +03:00

Author

Owner

@nivedin commented on GitHub (May 15, 2024):

If we close every tabs, we should have an empty panel. This is not possible at the moment we always need to have an open request atb.

Thank you for sharing your observation. Could you please provide more insight into the use case for this feature? Understanding its intended purpose will help us address any limitations or consider potential improvements.

@nivedin commented on GitHub (May 15, 2024): > If we close every tabs, we should have an empty panel. This is not possible at the moment we always need to have an open request atb. Thank you for sharing your observation. Could you please provide more insight into the use case for this feature? Understanding its intended purpose will help us address any limitations or consider potential improvements.

kerem commented

2026-03-16 19:58:28 +03:00

Author

Owner

@jobartim44 commented on GitHub (May 21, 2024):

If we close every tabs, we should have an empty panel. This is not possible at the moment we always need to have an open request atb.

Thank you for sharing your observation. Could you please provide more insight into the use case for this feature? Understanding its intended purpose will help us address any limitations or consider potential improvements.

I like to only have opened tabs that related to the current workspace. The easier way is to close every tabs when switching from one workspace to another. But if this action closed every request tabs we should have something to show. It could be an empty panel or tab (watever the way it takes). We could also have quick actions in this 'welcome' tab like creating a new request.

@jobartim44 commented on GitHub (May 21, 2024): > > If we close every tabs, we should have an empty panel. This is not possible at the moment we always need to have an open request atb. > > Thank you for sharing your observation. Could you please provide more insight into the use case for this feature? Understanding its intended purpose will help us address any limitations or consider potential improvements. I like to only have opened tabs that related to the current workspace. The easier way is to close every tabs when switching from one workspace to another. But if this action closed every request tabs we should have something to show. It could be an empty panel or tab (watever the way it takes). We could also have quick actions in this 'welcome' tab like creating a new request.