bru.setEnvVar() with { persist: true } doesn't write to environment file in VS Code extension

[Hansehart]

I'm using the Bruno VS Code extension and trying to persist an environment variable from a script:post-response block:

script:post-response {                                                                                                                                                                                                                                            
  let response = res.getBody();
  if (response.result?.approval_id) {
      bru.setEnvVar("approval_id", response.result.approval_id, { persist: true });
  }
}

Expected behavior

The approval_id value should be written back to the Development.bru environment file, so it's available across requests and sessions.

Actual behavior

• The value is set in-memory (confirmed via console.log and the main:script-environment-update broadcast)
• The value is never written to the .bru environment file
• Tested both with and without pre-defining approval_id: in the environment file and neither persists

Workaround

Using vars:post-response instead, which sets a runtime/collection variable that works within the same session:

vars:post-response {
approval_id: res.body.result.approval_id
}

Important: Do not define approval_id in the environment file, even as empty. The empty env var takes priority and will shadow the runtime variable set by vars:post-response.

Environment

• Bruno VS Code extension
• Linux (WSL2)

Question

1. Is { persist: true } supported in the VS Code extension? In the source code, the persistence mechanism uses IPC (main:persistent-env-variables-update) which is handled in bruno-electron. Is this wired up in the VS Code extension as well?
2. Does the sandbox mode (Safe vs Developer) affect bru.setEnvVar() or { persist: true } behavior in the VS Code extension? The desktop app uses QuickJS for Safe mode and NodeVM for Developer mode — does the VS Code extension respect this setting, and is
   there a way to configure it?