You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #429 and v0.6.1: the Cursor receive loop repeatedly concatenates each fragmented Connect frame, causing quadratic copying. An 8 MiB synthetic frame in 16 KiB chunks copies about 2 GiB. Cursor also constructs history in both rootPromptMessagesJson and turns; that local duplication does not establish duplicate model context, so protocol and Pi compaction boundaries need verification before any semantic change. Long child transcript rendering has an existing candidate in #327.
Scope
Replace quadratic frame accumulation while preserving frame limits, end/truncation errors, tool handoff, and cancellation.
Verify Cursor context/usage behavior using current Pi and protocol evidence; retain unknown usage as unknown rather than fabricating accounting.
Problem
Follow-up to #429 and v0.6.1: the Cursor receive loop repeatedly concatenates each fragmented Connect frame, causing quadratic copying. An 8 MiB synthetic frame in 16 KiB chunks copies about 2 GiB. Cursor also constructs history in both rootPromptMessagesJson and turns; that local duplication does not establish duplicate model context, so protocol and Pi compaction boundaries need verification before any semantic change. Long child transcript rendering has an existing candidate in #327.
Scope
No user runtime or configuration change is part of this repair.