We’re gradually rolling out a new variables and environments experience designed to make variable management simpler, safer, and more predictable.

Why the change?

In the old model, “Initial” and “Current” values often caused confusion. Many users accidentally synced secrets to their teams or even public workspaces. The new design eliminates this risk by making sharing explicit and keeping variables local by default.

What’s new

• Single Value field → Replaces Initial and Current. This field always shows the value used in requests and runs.
• Explicit sharing → Variables start as local-only. You choose when to share with teammates, either individually or in bulk.
• Clearer states → If your local value differs from the shared one, the variable is flagged as Edited, prompting you to update or reset.
• Safer defaults → Nothing is shared unless you decide. Sensitive variables can be masked, and you’ll see warnings before sharing them.
• Autosave + Descriptions → Changes save automatically, and you can now add descriptions to document variable usage.

⸻

What happens to existing variables

• Variables with an initial value → Shown as Shared.
• Variables with only a current value → Shown in the Value field, Unshared.
• If initial ≠ current → Value field shows the current value, with an Edited state.
• Secrets → Stay masked.
• Existing variables and environment follow the above pattern to keep everything compatible with older versions of the app

⸻

We know this is a change from the old UI, but the intent is to reduce confusion and make variable management more reliable. We’re actively listening, so please continue sharing feedback if something feels unclear or harder in the new design.