[GH-ISSUE #3866] [feature]: Remember the chosen environment per tab #1358

New issue

Open

opened 2026-03-16 19:58:33 +03:00 by kerem · 0 comments

kerem commented

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

Owner

Originally created by @mikej0 on GitHub (Feb 28, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3866

Is there an existing issue for this?

I have searched the existing issues

Summary

Hello,

I have a situation where I am dealing with multiple different apis at once. Each time I need to call one of them, I need to go to the api call tab, choose the environment, trigger the call, and repeat that process whenever I make another call.

Can Hoppscotch not remember the environment chosen per call so I don't have to manually change it every single time? Even if it's only rememberd for as long as the tabs are open, that would be fine.

I have tried running the Windows desktop application several times, but it seems set that trying to start a second instance only takes you to the first, and I can't think of any other workarounds.

Why should this be worked on?

Any scenario where you're working across multiple distinct apis is tedious at the moment, and users are prone to forgetting to keep switching environment, potentially resulting in incorrect or dangerous api calls.

Originally created by @mikej0 on GitHub (Feb 28, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3866 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary Hello, I have a situation where I am dealing with multiple different apis at once. Each time I need to call one of them, I need to go to the api call tab, choose the environment, trigger the call, and repeat that process whenever I make another call. Can Hoppscotch not remember the environment chosen per call so I don't have to manually change it every single time? Even if it's only rememberd for as long as the tabs are open, that would be fine. I have tried running the Windows desktop application several times, but it seems set that trying to start a second instance only takes you to the first, and I can't think of any other workarounds. ### Why should this be worked on? Any scenario where you're working across multiple distinct apis is tedious at the moment, and users are prone to forgetting to keep switching environment, potentially resulting in incorrect or dangerous api calls.