It seems that when in CLI, closing a session and starting a new one gets developer tools stuck.

To Reproduce
Steps to reproduce the behavior:

1. Open goose cli
2. run a session for a while and then close it
3. open a new goose cli session (in the same terminal, but doesn’t seem to matter)
4. perform a task that would use developer tools (like listing files in current folder)
5. observe goose cli unable to do so, and ls -F command returning -32603 and -32002 error codes

These error codes seem to come from JSON-RPC, so I’m assuming this might be a MCP-related error.

What finally gets goose unstuck is disabling developer tools using goose configure and then re-enabling them.

Expected behavior
Developer tools should work without interruption

Screenshots

App Version: 1.12.1
OS: macos
OS Version: 24.6.0
Architecture: aarch64
Timestamp: 2025-12-04T21:03:41.725515+00:00

Diagnostics data

Download here