goose session -> Failed to start the MCP server from configuration Builtin(developer) `Call to '' failed for 'initialize'. Error from mcp-server: Stdio process error: \nthread 'main' panicked

[Dan-Wuensch]

Describe the bug

Note: Please check some common questiosn on https://block.github.io/goose/docs/troubleshooting before filing the report

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Run goose session on MacOS 15.3.1
2. Observe the following error:

Failed to start extension: developer, "Failed to start the MCP server from configuration Builtin(developer) Call to '' failed for 'initialize'. Error from mcp-server: Stdio process error: \nthread 'main' panicked at /Users/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tracing-appender-0.2.3/src/rolling.rs:154:14:\ninitializing rolling file appender failed: InitError { context: \"failed to create initial log file\", source: Os { code: 13, kind: PermissionDenied, message: \"Permission denied\" } }\nnote: run with RUST_BACKTRACE=1 environment variable to display a backtrace\n"

Expected behavior
goose session runs without sudo

Screenshots
If applicable, add screenshots to help explain your problem.

Please provide following information:

• OS & Arch: MacOS 15.3.1
• Interface: CLI
• Version: 1.0.9
• Extensions enabled: developer
• Provider & Model: Bedrock, us.anthropic.claude-3-7-sonnet-20250219-v1:0

Additional context
Running sudo bypasses this error, but then I end up encountering other issues due to sudo not having context to AWS credentials, etc