MCP tool context_key does not change per task, breaking context isolation

Bug Reports
1

Issue Description

When calling MCP tools in QoderWork, the context_key field inside the context object remains the same across different task windows. This causes context pollution between tasks, as the MCP server cannot distinguish which task a request belongs to.

Steps to Reproduce

  1. Open task window A and call any MCP tool (e.g., mcp__xxx__do_something).
  2. After task window A completes, create a new task window B.
  3. In task window B, call the same MCP tool.
  4. On the MCP server side, log the received request parameters.
  5. Observe that context.context_key has the exact same value for both task A and task B.

Expected Behavior

Each task window should receive a unique context_key so that the MCP server can isolate context and state per task.

Actual Behavior

All tasks share the same context_key. The MCP server cannot distinguish between requests from different tasks, and context leakage occurs.

Screenshots / Screen Recordings

(Attach your screenshot here — the one showing identical context_key values from both task windows.)

2770A8B5-59BB-4AF8-B4D3-B5E9ECDDDDE0
2770A8B5-59BB-4AF8-B4D3-B5E9ECDDDDE01920×224 128 KB

Operating System

macOS

Current Qoder Version (Menu → About Qoder → Copy)

(Please fill in your Qoder version from the menu.)

Additional Info (for backend investigation)

  • MCP server dependency: com.alibaba.mcp:mcp-lite-hsf-server-starter:1.2.2
  • First reported via in-app feedback on 2026-05-20, no response received yet.