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
{{ message }}
Repository navigation
fix(dsh): honor server fallback flag in Context tab ownership check #2
handlePluginStatus emits fallback:true for fallback=latest responses, while parseCtxStatus reads only viaFallback. The Context tab ownership guard therefore never fires for real server responses. Opening conversation B before its first model call can embed conversation A’s compression view.
The existing regression mock used viaFallback:true, unlike the actual server contract. Fix: accept the real fallback field, retaining the legacy alias; test real server-shaped foreign fallback rejection and own-conversation fallback acceptance.
This is a functional display bug, not a security audit. No server protocol or config changes are needed. Related upstream ranxianglei#4118 established the guard but did not align the field name; source at the current fork baseline still mismatches.
Activity