about request time out error

[ghghdfd]

I'm really enjoying using the extension — great work!

However, I occasionally encounter a "Request timed out" error during use, which causes tool detection or invocation failures. This mainly happens when I'm using relatively complex instructions that involve multiple tool calls, such as those using sequential-thinking. When I trigger sequential-thinking several times, this error occurs and eventually the server itself becomes unresponsive.

I'm experiencing this issue both on Aistudio and ChatGPT, under the same conditions.

Browser information

• Microsoft Edge
• Version: 135.0.3179.85

Error code

[mcp-superassistant-proxy] Error fetching tools from sequential-thinking: McpError: MCP error -32001: Request timed out
    at Timeout.timeoutHandler (file:///C:/Users/AppData/Local/npm-cache/_npx/63cc4b2a7e73c390/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:292:49) 
    at listOnTimeout (node:internal/timers:594:17)
    at process.processTimers (node:internal/timers:529:7) {
  code: -32001,
  data: { timeout: 60000 }
}

Do you have any suggestions or solutions to prevent or handle this timeout error?

[Kreijstal]

yea his code is buggy

[Sudo88888]

File : index.iife.js
// BEFORE: 30 seconds timeout
pendingRequestTimeoutMs: 3e4

// AFTER: 3 MINUTES timeout
pendingRequestTimeoutMs: 18e4 // ✅ CHANGED -- change this to whatever value you want , i have found thaat 3 min is more than enough

--

file : background.js
// BEFORE: Various short timeouts
Vl = 3e5 // 5 minutes (kept as default)
i = 3e4 // 30 seconds

// AFTER: Extended timeouts
Vl = 3e5 // ✅ KEPT at 5 minutes
i = 18e4 // ✅ CHANGED to 3 minutes
connectionTimeoutThreshold: 18e4 // ✅ CHANGED to 3 minutes -- the same here ,

to summ :
pendingRequestTimeoutMs: 18e4 → MCP tools get 3 minutes to complete
i = 18e4 → Server connections wait 3 minutes before failing
connectionTimeoutThreshold: 18e4 → Connection health checks every 3 minutes

[Sudo88888]

connectionTimeoutThreshold : i have changed this to 3 min , because ,when a timeout error , or any mcp error accurs ,the extension becomes unusable , and needs a restart or update , but i have found that , let it 3 min , it will execute the restart connection of the delay of 5 s , as the original , and that helps ,