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
Describe the bug
I’m seeing a large number of zombie or idle mcp processes accumulating on my machine over time. These appear to be started by Goose or related tooling, but are never cleaned up — even after closing Goose or finishing a session.
These stale processes date back several days and continue to persist unless manually killed.
A clear and concise description of what the bug is.
To Reproduce
ps aux | grep 'mcp_glean' | grep -v grep
Expected behavior
mcp processes should exit cleanly when no longer needed — for example:
• When the user closes Goose
• When a task completes
• Or when the subprocess times out or exits on its own
Describe the bug
I’m seeing a large number of zombie or idle mcp processes accumulating on my machine over time. These appear to be started by Goose or related tooling, but are never cleaned up — even after closing Goose or finishing a session.
These stale processes date back several days and continue to persist unless manually killed.
A clear and concise description of what the bug is.
To Reproduce
Expected behavior
mcp processes should exit cleanly when no longer needed — for example:
• When the user closes Goose
• When a task completes
• Or when the subprocess times out or exits on its own
Screenshots
https://sq-block.slack.com/archives/C06PBQ52MCK/p1744730007918479
Please provide following information:
• Device: Apple MacBook Pro (M1 Max)
• OS: macOS Sequoia 15.3.2
• Goose version: Goose 1.0.17
• CLI tool: uv
The text was updated successfully, but these errors were encountered: