Desktop App: `envs` config block not forwarded to stdio extension subprocesses.

[botoxparty]

Bug: envs block in stdio extension config not passed to subprocess

Description

Environment variables defined in the envs block of a stdio extension config are not being
passed to the spawned subprocess. The subprocess falls back to its own defaults instead.

Steps to Reproduce

1. Configure a stdio extension in ~/.config/goose/config.yaml with an envs block:

extensions:
  my-extension:
    enabled: true
    type: stdio
    cmd: /path/to/binary
    args:
      - serve
    envs:
      MY_ENV_VAR: some-value

2. Launch goose and use the extension
3. The subprocess does not receive MY_ENV_VAR — it uses its default value instead

Workarounds Attempted

• Setting vars via ~/.zshrc — doesn't work (goose launched as app doesn't inherit shell env)
• Setting vars via launchctl setenv — doesn't work
• Using cmd: env with vars as args — still not working

Expected Behavior

Environment variables in the envs block should be forwarded to the stdio subprocess on launch.

Actual Behavior

Subprocess receives no env vars and falls back to defaults (e.g. localhost:3000 instead of
the configured URL).

Environment

• goose version: (run goose --version)
• OS: macOS
• Extension: mcp-grafana (but reproducible with any stdio extension)

Impact

Makes it impossible to configure stdio extensions that require env vars (e.g. API keys, URLs)
without workarounds. This affects any MCP server that reads configuration from environment
variables, which is the standard pattern.

[botoxparty]

BTW, works completely fine in CLI

[jamadeo]

What version of goose? If I put in my config.yaml:

  everything:
    enabled: true
    type: stdio
    name: everything
    cmd: npx
    args:
    - -y
    - '@modelcontextprotocol/server-everything'
    envs:
      MY_ENV_VAR: abc

and then ask goose "run the get-env tool and tell me the value of MY_ENV_VAR", I get the expected reply:

The value of MY_ENV_VAR is abc.

[sheikhlimon]

Not sure if this is macOS-specific since I'm on Linux, but envs is working for me in Desktop App. I'm using envs to set DOCS2DB_MCP_TRANSPORT: stdio (passing the transport type through env instead of type field) and it gets passed correctly. Server starts in stdio mode, so envs block is definitely being forwarded to the subprocess in my case.

[jamadeo]

Unable to reproduce this, please let me know if there are more details that could help.