GitHub issue #14059 in cline/cline, opened 2026-09-11 by Energytechglobal, records a report that when multiple Cline terminals run in the same workspace, a shared relay state file can associate requests with the wrong task, that the OpenAI-compatible request does not receive a request-scoped x-litellm-trace-id header from Cline, and that when a shared relay or state workaround is used, the most recently captured task ID can overwrite the other terminal's ID, causing requests to be attributed to the wrong session; the issue proposes adding the header from the current request-scoped session ID.
Verbatim Excerpts from Cited Records
“When multiple Cline terminals run in the same workspace, a shared relay state file can associate requests with the wrong task. The existing request-header resolution already receives a request-scoped `sessionId`, which can be used directly to preserve per-terminal correlation.”
“The issue was observed while using multiple Cline CLI terminals with an OpenAI-compatible LiteLLM provider.”
·
cline/cline (issue 14059 opening body, Affected version and surfaces section)
·
2026-09-11T08:10:49Z
·GitHub Issue ↗
“The OpenAI-compatible request does not receive a request-scoped `x-litellm-trace-id` from Cline.”
·
cline/cline (issue 14059 opening body, Actual result section)
·
2026-09-11T08:10:49Z
·GitHub Issue ↗
“other terminal's ID, causing requests to be attributed to the wrong session.”
·
cline/cline (issue 14059 opening body, Actual result section)
·
2026-09-11T08:10:49Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 3 comments were read. linear-code[bot] (2026-09-11) linked the Linear record CLINE-3255. Energytechglobal (2026-10-10) notes PR #14151 is the active PR for this issue and asks for maintainer review; no maintainer reply appears in the surveyed thread, and the proposed header was not independently verified as shipped here. dabazti (2026-11-08) describes a similar use case with a local llama.cpp inference server and a session-aware proxy, not a reproduction of this report. The claim documents only the reported behaviour and the proposal, not that the proposed header has shipped.
Falsification probe: If GitHub issue #14059 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.