You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goose session fails to start with gdrive extension on Mac.
Failed to start extension: gdrive, "Failed to start the MCP server from configuration `Stdio(gdrive: npx -y @modelcontextprotocol/server-gdrive)` `Call to '' failed for 'initialize'. Error from mcp-server: Stdio process error: Credentials not found. Please run with 'auth' argument first.\n`"
Please check extension configuration for gdrive.
The problem is in step 5 "Add your environment variables"
The path for the two extension variables mentioned in the instructions is relative to home directory. It should be absolute, instead.
Expected behavior
Goose session should start without any issue
Actual behavior
Goose session fails to start
Please provide following information:
OS & Arch: [macOS Sequoia 15.3.1 x86]
Interface: CLI
Version: [1.0.10]
Extensions enabled: [developer, gdrive]
Provider & Model: [Bedrock Nova]
Additional context
Fix
The path of files should be absolute path, not relative to user home directory. Either the instructions page needs an update, or a section can be added in the troubleshooting page.
The text was updated successfully, but these errors were encountered:
@kalvinnchau - i don't know where they need to be resolved. I can tell you the problem that if i provide relative paths, i get an error. If i provide absolute paths for these 2 environment variables, the extension works fine.
Describe the bug
Goose session fails to start with gdrive extension on Mac.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Goose session should start without any issue
Actual behavior
Goose session fails to start
Please provide following information:
Additional context
Fix
The path of files should be absolute path, not relative to user home directory. Either the instructions page needs an update, or a section can be added in the troubleshooting page.
The text was updated successfully, but these errors were encountered: