vscode (Flatpak) not working using Reopen in Devbox Shell environment

[lordgreg]

What happened?

I've installed VSCode using Flatpak on Fedora.

Installing the plugin worked also, this is the entry I see in Output (Extension Host):

2025-04-09 18:58:54.326 [info] ExtensionService#_doActivateExtension jetpack-io.devbox, startup: false, activationEvent: 'onStartupFinished'

Reopening the VSCode also works since it recognizes the devbox and, when opening Integrated Terminal, I can immediatelly execute devbox:

However, executing "Reopen in Devbox Shell environment" doesn't work and yields to the exception:

2025-04-09 19:08:04.059 [error] Error: spawn devbox ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

Unsure what do to in this situation.

Steps to reproduce

Command

No response

devbox.json

{
  "$schema":  "https://raw.githubusercontent.com/jetify-com/devbox/0.14.0/.schema/devbox.schema.json",
  "packages": ["go@latest"],
  "shell": {
    "init_hook": [
      "echo 'Welcome to devbox!' > /dev/null"
    ],
    "scripts": {
      "test": [
        "echo \"Error: no test specified\" && exit 1"
      ]
    }
  }
}

Devbox version

0.14.0

Nix version

nix (Nix) 2.27.1

What system does this bug occur on?

Linux (x86-64)

Debug logs

No response

[mohsenari]

Hi @lordgreg can you please check if code is in your PATH in terminal? Reopen in Devbox relies on it to reopen vscode after it's closed.
For further debugging you can also enable debug mode in the settings and that will create a log file in your .devbox directory. You can run Reopen in Devbox again from VSCode and inspect the logs to get a better insight at which stage things go wrong.