starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #5580] [bug]: Environment secrets are not syncing between Browser and Desktop clients #2155

New issue

Closed

opened 2026-03-16 23:23:53 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 23:23:53 +03:00

Owner

Originally created by @roopepaajanen on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5580

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Web App

Browser

Chrome

Operating System

macOS

Bug Description

Environment secrets created or modified in the Browser client do not appear in the Desktop client — and vice versa. This results in API requests failing due to missing secret values.

Steps to Reproduce

Create a new environment in the Browser client.
Add an API key secret to the environment.
Make an API call in the browser that inherits the API key from the environment — the request succeeds as expected.
Open the Desktop client — the new environment is visible.
Make the same API call in the Desktop client, inheriting the API key from the environment → the API returns "missing api key".
Open the environment secrets in the Desktop client — the API key secret is present but its value is missing.
Add the missing secret value in the Desktop client — the API request now works.
Move back to the Browser client and make the same request — it now fails, and checking the environment shows the API key value is missing again.

Expected Behaviour

Environment secrets (names and values) should sync consistently across Browser and Desktop clients.

Actual Behaviour

Secret keys sync, but secret values do not, causing secrets to disappear depending on where the last edit was made

Configurations:

Hoppscotch_SelfHost_mac_aarch64.dmg from v25.10.1-0 Release
Chrome Version 142.0.7444.135 (Official Build) (arm64)
You can find my application network configurations from issue 5541

Deployment Type

Self-hosted (on-prem deployment)

Version

2025.10.1

Originally created by @roopepaajanen on GitHub (Nov 13, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5580 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Chrome ### Operating System macOS ### Bug Description Environment secrets created or modified in the Browser client do not appear in the Desktop client — and vice versa. This results in API requests failing due to missing secret values. Steps to Reproduce 1. Create a new environment in the **Browser** client. 2. Add an API key secret to the environment. 3. Make an API call in the browser that **inherits the API key from the environment** — the request succeeds as expected. 4. Open the **Desktop** client — the new environment is visible. 5. Make the same API call in the Desktop client, inheriting the API key from the environment → the API returns "missing api key". 6. Open the environment secrets in the Desktop client — the API key secret is present but its value is missing. 7. Add the missing secret value in the Desktop client — the API request now works. 8. Move back to the Browser client and make the same request — it now fails, and checking the environment shows the API key value is missing again. ### Expected Behaviour Environment secrets (names and values) should sync consistently across Browser and Desktop clients. ### Actual Behaviour Secret keys sync, but secret values do not, causing secrets to disappear depending on where the last edit was made Configurations: - Hoppscotch_SelfHost_mac_aarch64.dmg from [v25.10.1-0 Release](https://github.com/hoppscotch/releases/releases/tag/v25.10.1-0) - Chrome Version 142.0.7444.135 (Official Build) (arm64) - You can find my application network configurations from issue [5541](https://github.com/hoppscotch/hoppscotch/issues/5541) ### Deployment Type Self-hosted (on-prem deployment) ### Version 2025.10.1

kerem

2026-03-16 23:23:53 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 23:24:09 +03:00

Author

Owner

@roopepaajanen commented on GitHub (Nov 13, 2025):

The UI on the other platform after changing the value:

@roopepaajanen commented on GitHub (Nov 13, 2025): The UI on the other platform after changing the value: <img width="762" height="287" alt="Image" src="https://github.com/user-attachments/assets/e865e923-cf65-4e91-a302-0c22148b8789" />

kerem commented

2026-03-16 23:24:14 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 13, 2025):

This is an expected behavior because secrets are never stored on Hoppscotch servers. It’s expected that users will populate the value of the secret variable at runtime. While we’re enhancing the user experience of this feature, we welcome feedback. For more information, refer to the documentation on Types of Variables in an Environment.

@liyasthomas commented on GitHub (Nov 13, 2025): This is an expected behavior because secrets are never stored on Hoppscotch servers. It’s expected that users will populate the value of the secret variable at runtime. While we’re enhancing the user experience of this feature, we welcome feedback. For more information, refer to the documentation on [Types of Variables in an Environment](https://docs.hoppscotch.io/documentation/features/environments#types-of-variables-in-an-environment).

kerem commented

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

Author

Owner

@roopepaajanen commented on GitHub (Nov 13, 2025):

Thanks for the quick response and for clarifying the functionality, @liyasthomas!

I understand the limitation around storing secrets in the Hoppscotch cloud. However, for self-hosted customers using an external database, secrets are fully under our control. In that setup, many of us would benefit from (or at least appreciate the option for) seamless use of both the Browser and Desktop clients — for example, by allowing secrets to be stored in the external database.

This ticket can be closed. Thanks again for the fast response!

@roopepaajanen commented on GitHub (Nov 13, 2025): Thanks for the quick response and for clarifying the functionality, @liyasthomas! I understand the limitation around storing secrets in the Hoppscotch cloud. However, for self-hosted customers using an external database, secrets are fully under our control. In that setup, many of us would benefit from (or at least appreciate the option for) seamless use of both the Browser and Desktop clients — for example, by allowing secrets to be stored in the external database. This ticket can be closed. Thanks again for the fast response!

kerem referenced this issue

2026-03-17 01:14:23 +03:00

[PR #2145] [MERGED] chore: introduce curl parser tests and minor changes #3641