Forumics logo Forumics
Issue 01

Back to issue

All Cline known issues

CLAIM C105 Supported 2026-11-12

GitHub issue #14045 in cline/cline, opened 2026-09-10 by lamian521, records a report that in Cline CLI 3.0.61-nightly, fresh session/new sessions work normally, but after restoring a session with two completed turns in a new process, session/load succeeds and replays the history, yet the immediately following session/prompt emits only session_info_update and resolves with end_turn, zero new agent_message_chunk events and zero body characters, so the requested token is not recalled; the report rules out the post-load model pin as the cause, since both variants failed identically.

Verbatim Excerpts from Cited Records
“Fresh `session/new` sessions work normally: multi-turn context, cancellation and reuse, and permission rejection all behave as expected.”
— lamian521 · cline/cline (issue 14045 opening body, What happened section) · 2026-09-10T22:47:36Z ·GitHub Issue ↗
“However, after restoring a session that already has two completed turns in a new process, `session/load` succeeds and replays the history, but the immediately following `session/prompt` emits only `session_info_update` and resolves with `{"stopReason":"end_turn"}`.”
— lamian521 · cline/cline (issue 14045 opening body, What happened section) · 2026-09-10T22:47:36Z ·GitHub Issue ↗
“It emits zero new `agent_message_chunk` events and zero body characters, so the requested token is not recalled.”
— lamian521 · cline/cline (issue 14045 opening body, What happened section) · 2026-09-10T22:47:36Z ·GitHub Issue ↗
“After a successful load and complete history replay, the restored session should continue normally.”
— lamian521 · cline/cline (issue 14045 opening body, Expected section) · 2026-09-10T22:47:36Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 3 comments were read. linear-code[bot] (2026-09-10) linked CLINE-3253. Dante-dan (2026-09-10) traced the ACP path on main, described the load as starting a new CLI core session with the persisted messages as initialMessages, and proposed a focused session-lifecycle investigation with a deterministic regression test for two completed turns, load, then next prompt. github-actions[bot] (2026-11-11) marked the issue stale after 60 days with no activity. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #14045 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.