Unverified50% confidenceReleaseExact time
v2.1.311 fixes the issue where a Remote Control session got stuck at "Connecting" for about two minutes when a network proxy blocked the startup request, and makes unfinished WebFetch/WebSearch requests fail after 300 seconds instead of hanging indefinitely.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/26/2026
First Seen
Valid until: 1/24/2027
Sources
Related Entities
Related Claims
Unverified远程控制修复了重连请求无响应时的问题,现在会在30秒后放弃并重试76% similarUnverifiedThe Remote Control feature fixes a bug where the host would exit and disconnect the session after server credentials expired (approximately 30 days); it now supports automatic re-registration and maintains the connection.72% similarUnverifiedv2.1.258 fixed the issue in remote sessions and scheduled sessions where failed re-sending of permission approvals threw a 'user messages must have non-empty content' error, causing session failures.69% similarUnverifiedThis update fixes an issue where the gateway OTLP telemetry relay would pause all forwarding for 30 seconds after rejecting malformed or oversized payloads.68% similarUnverifiedv3.36.0 concentrated on fixing multiple boundary issues related to Realtime WebSocket, including cleanup of failed connection establishment, respect for native options, ending sync WebSocket recovery on interruption, respecting Translation receipt with timeout during terminal cleanup, preserving WebSocket close state across recovery and cancellation scenarios, and respecting native options for the legacy beta socket (PR #4121, #4129, #4132, #4117, #4120).64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1101292API
curl https://kongchang.com/api/v1/knowledge/claims/1101292MCP
get_claim(id=1101292)