I have checked the following:
This bug is:
Bruno version
4.1.0
💻 Operating System
Linux
Specific OS Version / Distro
No response
🐞 Describe the bug
When Bruno is installed via snap (strict confinement), the built-in terminal feature cannot execute npm commands. cd and other shell builtins work fine, but any external binary like npm fails with a permission error, presumably because the snap's AppArmor/seccomp sandbox blocks access to binaries outside the snap's own confined environment.
📝 Steps to reproduce
- Install Bruno via
sudo snap install bruno
- Open the built-in terminal inside Bruno
- Run
cd some/path works
- Run
npm install (or any npm command) fails with permission denied
Expected behavior:
The integrated terminal should be able to run npm (and other locally installed CLI tools) the same way a regular system terminal does.
Actual behavior:
npm commands are denied inside Bruno's integrated terminal.
Environment:
- OS: Ubuntu 24.04 (noble)
- Bruno installation method: snap
- Bruno version: [PREENCHER — ver em Help > About]
- npm installed via: [PREENCHER — ex: nvm, apt, ou binário do sistema]
Additional context:
This appears to be caused by snap's strict confinement, which isolates the app from the host filesystem/binaries outside its own sandbox. A classic confinement option (if feasible) or documented workaround (e.g. exposing PATH/home access) would help snap users.
📁 Collection to reproduce
Not applicable this issue is not related to a specific collection; it happens with any collection since it's caused by the snap sandbox blocking terminal access.
📷 Screenshots/Live demo link
I have checked the following:
This bug is:
Bruno version
4.1.0
💻 Operating System
Linux
Specific OS Version / Distro
No response
🐞 Describe the bug
When Bruno is installed via snap (strict confinement), the built-in terminal feature cannot execute
npmcommands.cdand other shell builtins work fine, but any external binary likenpmfails with a permission error, presumably because the snap's AppArmor/seccomp sandbox blocks access to binaries outside the snap's own confined environment.📝 Steps to reproduce
sudo snap install brunocd some/pathworksnpm install(or any npm command) fails with permission deniedExpected behavior:
The integrated terminal should be able to run npm (and other locally installed CLI tools) the same way a regular system terminal does.
Actual behavior:
npm commands are denied inside Bruno's integrated terminal.
Environment:
Additional context:
This appears to be caused by snap's strict confinement, which isolates the app from the host filesystem/binaries outside its own sandbox. A
classicconfinement option (if feasible) or documented workaround (e.g. exposing PATH/home access) would help snap users.📁 Collection to reproduce
Not applicable this issue is not related to a specific collection; it happens with any collection since it's caused by the snap sandbox blocking terminal access.
📷 Screenshots/Live demo link