Issue in Bruno CLI when installed via @latest in GitHub Actions

[vishwanathtaware]

I have checked the following:

• I have searched existing issues and found nothing related to my issue.

This bug is:

• making Bruno unusable for me
• slowing me down but I'm able to continue working
• annoying
• this feature was working in a previous version but is broken in the current release.

Bruno version

Bruno CLI v3.0.0 (released on 5 Jan 2026)

Operating System

Git Actions Ubuntu Latest

Describe the bug

We are facing an issue after upgrading to Bruno CLI v3.0.0 (released on 5 Jan 2026) while running our API automation tests using Bruno CLI in a GitHub Actions workflow.

Background

In our GitHub Actions workflow, we install Bruno CLI using npm and run our API test collections as part of CI. One of the requests handles authentication/token generation, where we validate the presence of id_token and control request flow using Bruno scripting

This setup was working fine earlier.

Issue Observed

When we install Bruno CLI using the latest version:
npm install -g @usebruno/cli@latest

we start seeing the following runtime error during test execution:
Cannot read properties of undefined (reading 'owner')

This happens even though:

1. The API response is correct
   

2. id_token is present
   

3. Token generation succeeds
   

4. Subsequent API requests execute successfully
   

Validation Performed

To isolate the issue, we updated the GitHub Actions workflow to install a fixed version of Bruno CLI:
npm install -g @usebruno/cli@2.15.1

With Bruno CLI v2.15.1, the same collections run successfully without any assertion failures or runtime errors.

Request

Could you please help confirm:

If any script updates are required for CLI execution in CI after the upgrade v3.0.0

Or if this is a issue from bruno sid in CLI v3.0.0

.bru file to reproduce the bug

No response

Screenshots/Live demo link

NA

[helloanoop]

Hi @vishwanathtaware

We recently released version 3, which has some breaking changes. Please see: https://www.usebruno.com/v3-release

The most important change in CLI is that we run on Safe Mode by default instead of developer mode.
For most people who see their CLI breaking, you should be able to pass --sandbox=developer and that would resolve the failures.

[ornkrist]

@helloanoop - On a similar note ( using v 3.0.0 ), I have a utility npm package that I use in pre and post scripts. During CI using the sandbox param and running tests it will prevent my utility from having access to bru ---> ReferenceError: bru is not defined

[helloanoop]

@ornkrist could you share more details please. bru should always be defined in safe as well as developer sandbox

[ornkrist]

@helloanoop please take a look below. I’ve created a sample Bruno project that uses my util package and a CI workflow to demonstrate the behavior.

https://github.com/ornatwork/test-bruno-cli/actions/runs/20766449593

[ynathaniel-source]

Based on the information provided and the discussion around the transition to Bruno CLI v3.0.0, it appears the core issue stems from the breaking changes introduced, specifically the default operation mode shifting to Safe Mode. This change impacts script execution and the accessibility of certain variables or objects, which seems to align with the errors you're encountering (Cannot read properties of undefined (reading 'owner') and ReferenceError: bru is not defined).

Given the context and the errors mentioned, a couple of points come to mind:

1. Safe Mode Restrictions: The transition to Safe Mode by default could indeed restrict access to certain properties or objects that were previously available. This aligns with the errors you're seeing, as it might be blocking access to expected properties or the bru object itself.

2. Compatibility with Existing Scripts: If your scripts were working with the previous version, it's possible that they rely on behaviors or access patterns that are no longer available or function differently in Safe Mode. The --sandbox=developer flag mentioned could be a workaround by reverting to a less restrictive environment, but it might not address all compatibility issues.

To move forward, I would suggest the following steps:

• Experiment with the --sandbox=developer Option: Since this was mentioned as a potential solution, have you tried running your scripts with this flag? This could help determine if the issue is indeed related to the Safe Mode restrictions.

• Review Safe Mode Documentation: It might be helpful to review any available documentation on what Safe Mode restricts or changes compared to the previous default mode. Understanding these changes could guide necessary adjustments to your scripts or usage of the Bruno CLI.

• Debugging and Isolation: Try to isolate the exact point of failure in your script. Since bru is mentioned as not defined, is there a specific operation or script line causing this? Sometimes, adding verbose logging or breaking down the script into smaller parts can help identify the exact trigger for these errors.

Questions to further clarify the situation:

• When running with the --sandbox=developer flag, do you encounter the same errors, or do they change in any way?
• Can you confirm if there are specific script operations or lines where these errors (Cannot read properties of undefined and ReferenceError: bru is not defined) are consistently reproducible?

Understanding the exact nature of the scripts and operations leading to these errors could provide further insights into whether the issue is strictly related to the Safe Mode environment or if there might be other factors at play.

[ornkrist]

Hi @ynathaniel-source @helloanoop

The 3.x version does not work for me.

The project I created to demonstrate the problem is located here
https://github.com/ornatwork/test-bruno-cli/actions/runs/20855854163
You can fork it if you want to test further.

This small test project runs UnitTests using Github action / workflow
Bruno CLI ( pinned version ) 2.15.1
- Without sandbox param - success
- With sandbox param - success
Bruno CLI 3.x
- Without sandbox param - fails
- With sandbox param - fails

The updateCounter() code

// Update counter if iteration is 0
if (bru.runner.iterationIndex == 0 || bru.runner.iterationIndex == undefined) {
  const counterValue = bru.getEnvVar("counter");

...