Feat: Edit environment variables in place

[symtalha14]

I have checked the following:

• [x] I've searched existing issues and found nothing related to my issue.

This feature

• [ ] blocks me from using Bruno
• [x] would improve my quality of life in Bruno
• [ ] is something I've never seen an API client do before

Describe the feature you want to add, and how it would change your usage of Bruno

Hi,

It would be awesome if one could edit the variables for an environment just by clicking/hovering over the variable i.e. edit it in place without the need for opening the Environment configuration window.

How it is done currently? Currently, you have to go to the Environment Configuration window from top right.

Proposed featured Just hover over the variable and give a field to update the variable, as can be seen below.

Before Edit option

After Edit option

Outcomes Would make it easier to edit variable when something needs to be changed quickly, or there are multiple variables in a request. Postman already has a similar feature.

Mockups or Images of the feature

No response

[karloluis]

I like this idea, but I see it having issues where variables are determined from values in the .env file.

Maybe that's a different feature, because right now I don't think there's a way to edit the file from Bruno.

[FilipePintoReis]

I came to submit this exact same feature request and found this issue. Big +1!

[symtalha14]

Would like to work on this if any of the mentors can assign this to me. Thanks.

@anusree-bruno

[anusree-bruno]

Hi @symtalha14, thanks for your interest!

Would like to work on this if any of the mentors can assign this to me. Thanks.

We currently don’t have a formal assignment process—issues are open for anyone to contribute to, and we’ll review all PRs and go with the one that fits best.

That said, before jumping into implementation, there’s an important aspect to consider: In Bruno, variables can be defined at multiple levels—global, environment, collection, folder, request, and runtime. Since variables with the same name can exist across different scopes, how do we determine which one is being edited?

We’ll also need to make that clear to the user. So the follow-up question is: should we allow users to select the scope explicitly when editing a variable?

Would love to hear your thoughts on this! @symtalha14 @manishrw

[symtalha14]

@anusree-bruno Fair point. Let me get back to you on this in sometime. Thanks.

[symtalha14]

Hi,

I had a look. You are right about the different scopes of variables.

In postman, there are only 3 scopes- Collection, Vault, and Global. Basically, postman treats request and response variables as part of the collection environment scope. And, at the time of inserting a variable, it gives us option to select the scope as well, as seen below-

Postman (var1 is defined at both Global and Environment level)

However, In Bruno, it seems there is a preference order which implicitly decides which value to use in case of identical variable names.

Bruno (var1 is defined in Collection environment, Post-Response variables, and Pre-request variables)

Now, there is another question to consider in addition to the original question-

1. Which scope's variable to edit? (ORIGINAL) 2. Should we show all the available scopes for a variable in case of identical variable names?

Answer to the first one, in my opinion, is straightforward- whichever variable is decided by the preference order (implicitly), just modify that variable.

For example, what i observed is- If there is a Pre-Request variable set and a Collection Env variable set (both identical), then it gives preference to the Pre-Request variable. So, in this case, we'll modify the Pre-Request variable.

Please correct me if I am wrong somewhere, Thanks!

@anusree-bruno

[symtalha14]

@anusree-bruno any update on this?

[manishrw]

Isn't this a duplicate of #3453? @symtalha14 Please do a through check before posting the issue.

[symtalha14]

@manishrw noted. However, whats the status of this? Any clue?

[anusree-bruno]

I checked with the team, handling variable scopes is a bit tricky, and we haven’t yet decided on the best approach. Since this is a quality-of-life improvement, we’re currently prioritizing core features for Bruno and won’t be able to pick this up right now. Given the complexity of the feature, I’m also unsure if the team will have the bandwidth to review a contribution this quarter. We plan to revisit this in Q3

[symtalha14]

Noted.

[MSpaceDev]

Just wanted to add my support for this feature. The ability to hover over a variable like {{baseUrl}} and either see its value, edit it directly, or switch between environment options would be a massive quality-of-life improvement. It would significantly speed up my testing workflow. Thanks for considering it!

Also, the approach of editing the final preference scope variable sounds best to me. So if I have a Global and Collection-level variable defined, then editing should only edit the Collection-level variable, as that scope has preference over Global implicitly.

[CaptaiNiveau]

Came here to agree with what has been said before. I'm currently migrating our team to Bruno and it's been a quite seamless experience, besides the variable editing. Editing a variable like this was one of the first things my coworker tried to do, just like myself. This and session restore are my two biggest QoL complaints with Bruno, everything else has been great so far ^^

[helloanoop]

We've allocated bandwidth for this to be looked at in Nov 2025. I took a look the PR , its in the right direction. Will provide more feedback on the PR.