[Bug] Windows/Codex: search_skills hangs after MCP tool discovery
Summary
On Windows with Codex using OpenSpace through stdio MCP, MCP initialization and tool discovery succeed, but search_skills never returns.
This is related to #36 but more specific: all OpenSpace tools are already visible before the local search call blocks.
Environment
- Windows; Python 3.12.5
- OpenSpace current
main, installed withpip install -e . - Codex desktop, stdio MCP
- MCP runtime:
mcp 1.29.0 - No cloud/LLM credentials configured for this local-search test
pip install -e . initially selected mcp 2.0.0, but OpenSpace imports mcp.server.fastmcp, which is absent in MCP 2. Installing mcp<2 was required to start the server.
Reproduction
- Start
openspace-mcpthrough a stdio MCP client withOPENSPACE_WORKSPACEset to a local ASCII checkout andOPENSPACE_HOST_SKILL_DIRSset to the host skills directory. - Initialize the session and call
list_tools. - Call
search_skillswith querydelegate task.
Actual result
- Tool discovery succeeds and returns:
cloud_auth_flow,cloud_browse_skills,execute_task,fix_skill,search_skills,upload_skill. search_skillsdoes not return within 240 seconds.- The same behavior remained after moving to an ASCII checkout path, granting the host write access for logs/runtime state, trying shell-only scope, and setting an ASCII session-storage directory.
Expected result
Local search should return results or an actionable error without waiting indefinitely. The host integration guide states local search_skills works without a cloud API key.
Notes
The host MCP configuration has tool_timeout_sec = 600 for long execute_task calls. This report is about the standalone local search_skills call. Sanitized logs are available on request.
Source: HKUDS/OpenSpace