Forumics logo Forumics
Issue 01

Back to issue

All Cline known issues

CLAIM C078 Supported 2026-11-09

GitHub issue #15579 in cline/cline, opened 2026-11-06 by The-time-forever, records a report that a saved Cline CLI 3.0.74 session cannot be resumed from /history because the Hub connection closes with code 1006 and reason Connection ended, that the Hub log records repeated abnormal socket closures with reason Received too big message, and that a session file of about 23.4 MiB containing 775 messages is a likely match for the affected session. The author states the socket-closure log entries carry no session ID, so the association cannot be confirmed from the logs alone.

Verbatim Excerpts from Cited Records
“A saved Cline CLI session cannot be resumed from `/history`. Selecting it produces:”
— The-time-forever · cline/cline (issue 15579 opening body, Description section) · 2026-11-06T16:20:48Z ·GitHub Issue ↗
“`Error: Failed to resume session: Hub connection closed (code=1006, reason=Connection ended)`”
— The-time-forever · cline/cline (issue 15579 opening body, Description section) · 2026-11-06T16:20:48Z ·GitHub Issue ↗
“{"message":"socket.closed","code":1006,"reason":"Received too big message","heartbeatTerminated":false,"serverClosing":false}”
— The-time-forever · cline/cline (issue 15579 opening body, Description section, Hub log JSON) · 2026-11-06T16:20:48Z ·GitHub Issue ↗
“A session associated with the workspace has a `messages.json` file of 24,499,544 bytes (approximately 23.4 MiB), containing 775 messages. It is a likely match for the affected session, although the socket-closure log entries do not include a session ID, so I cannot confirm the association from the logs alone.”
— The-time-forever · cline/cline (issue 15579 opening body, Description section) · 2026-11-06T16:20:48Z ·GitHub Issue ↗
Counter-record: Issue remains open. API returned 5 comments; all 5 were read. linear-code[bot] (2026-11-06) linked the report to CLINE-3748. The author added on 2026-11-08 that the same session resumes successfully in Cline Desktop but fails from CLI /history, and confirmed the CLI resume path calls readMessages and passes the full message list with no cursor-based or paginated loading in that path. Laotree (2026-11-08) suggested the resume pushes the whole history through one socket frame and asked about a cursor or paginated history path. No maintainer response appears in the thread. No retraction or correction appears in the thread. The claim documents only the original report, not a verified current state. Falsification probe: If issue 15579 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.