[Feature Request] Temporary Tabs, don't auto save

[BrendanBall]

• Insomnia Version: latest
• Operating System: All

Details

Basically, the postman workflow works well for me. workflows:

1. Create new tab, do stuff, maybe save to collection, maybe discard.
2. Open saved request, edit stuff like resource id or body, run request, discard changes ie. close tab without saving. workflow 1. is mainly for ad hoc stuff. I don't want a long lived request for every single request I want to make. It's much easier to close temporary tabs with Ctrl+w than manually doing multiple mouse clicks to delete a request in insomnia. workflow 2. is used a lot seen as I have many predefined collections. The current workflow of auto saving every change you make to the request doesn't work for me as my predefined collections will become very messy over time. I often open 5+ requests from a collection, change a resource id or data, use the requests, then close all those tabs by mashing Ctrl+w so that my collections are back to their pristine state.

This is basically whats preventing me from moving over from postman to insomnia. The last time I had a look at insomnia I gave up after realising this lack of feature in insomnia, but I recently found out insomnia has graphql support (minus the schema explorer which everyone still wants) which is making me look at insomnia again. IMHO temporary tabs and no auto saving are even more important features when it comes to graphql seen as you often mess around with the queries a lot more.

From the looks of it, I can see insomnia pretty much cannot support this, but I'd really like to see what other people think of this. Maybe even just disabling auto saving and not adding tabs might be good enough.

It would be really awesome if I can use one app for both rest and graphql.

[Horsty80]

We started work on tabs, here is a preliminary design. This would be a good time to share your feedback.

• We want to support Tabs so that different collections/tests/etc can be open at the same time.
• Tabs across different organizations can also be opened.

Thoughts?

Have you a screenshot for white theme ? in the dark theme the contrast are not very high:

• the green of the "post"
• the red of the "delete"

Maybe make the outline of all tabs mor visible ?

Cool stuff 🙌

[roskee]

• We want to support Tabs so that different collections/tests/etc can be open at the same time.

It should also be possible to open one request on multiple tabs! This is useful while working with multiple clients (like connecting to a websocket chat from different users, etc).

[subnetmarco]

@roskee This makes lots of sense.

[bbmatt]

This is still an issue, 6 years later?

Goodness me, just use Bruno and be done with it.

[rajeshranwa]

@subnetmarco we would really like to know the ETA for multitab feature. Thanks in advance.

[subnetmarco]

In September, October the latest.

[pavelicii]

@subnetmarco amazing, good news!

What about autosave feature thought? Will I be able to decide if I want to save the changes I did in specific tab or not?

As pointed out in the first message of this issue and by other participants, it is very common use-case to open some request in a new tab, do some ad-hoc things with it and close it without saving your changes.

[subnetmarco]

@pavelicii most likely we will need to split this scope of work in two different releases:

1. First, we will ship the tab capability on top of the current saving system.
2. Afterwards, once the tabs are there, we can discuss the ability to open a request and discarding the changes.

The second step is more complicated, so if we make the 2nd step a requirement, it will take a lot longer for tabs to show up in the product.