Skip to content

20260310-143224.md

Latest commit

 

History

History
53 lines (45 loc) · 2.25 KB

20260310-143224.md

File metadata and controls

53 lines (45 loc) · 2.25 KB
Raw

Result Log 2026-03-10 14:32 CST

Scope

  • Verify whether the Codex restart plus host reconnect attached the live MCP client to the updated hot shell.
  • Determine whether the previously observed long-call defect still exists after the restart.
  • Separate DevServer failures from general shell or worker health.

Benchmarks Run

1. Live Shell Sanity

  • Clipboard(get): pass
  • Snapshot: pass
  • Wait(1): pass
  • Interpretation:
    • the live shell is not broadly wedged;
    • the MCP connection is active and normal public tools still work.

2. Live Wait(8) After Restart

  • Expected:
    • pass if the restarted shell loaded the shell-local Wait mitigation.
  • Actual:
    • pass.
  • Interpretation:
    • the restarted live shell is serving the patched shell-owned Wait path.

3. Live DevServer(mode="health")

  • Expected:
    • prompt JSON health response from the restarted shell.
  • Actual:
    • still timed out at the outer 120 second tools/call deadline.
  • Contrast evidence:
    • live Clipboard, Snapshot, and Wait all succeeded;
    • local shell DevServer.health returned immediately with the new source-hash fields.
  • Interpretation:
    • this is now a tool-path-specific live integration failure, not evidence that the shell restart failed.

4. Live Forwarded Long-Call Check With PowerShell

  • Start-Sleep -Seconds 8; Write-Output 'wmcp-long-call-ok': fail, outer 120 second timeout
  • Start-Sleep -Seconds 4; Write-Output 'wmcp-short-call-ok': pass
  • Interpretation:
    • the long-call defect is generic to forwarded worker calls and not specific to Wait.

Process Evidence

  • Live process tree observed through PowerShell:
    • uv.exe --directory C:\Users\Rufus\src\Windows-MCP run windows-mcp --dev hot
    • child windows-mcp.exe
    • child shell python.exe
    • child worker python.exe -m windows_mcp.__main__ --internal-worker --transport streamable-http --host 127.0.0.1 --port 49946 --generation 1

Conclusion

  • The host reconnect succeeded and the live shell restart took effect for shell-local behavior.
  • The remaining reliability defect is the internal worker streamable-http bridge for longer-running forwarded calls.
  • DevServer should now be treated as a separate host-facing integration problem, not as the main indicator of shell freshness.