Back to Signal Feed
CodeTracked since May 21, 2026

Add durable local session tabs for sidebar and editor chats

This PR changes chat session behavior in Kilo-Org/kilocode so local sessions are no longer replaced when users start parallel work in the same repository. It introduces durable local session tabs in the sidebar and editor-tab surfaces, keeping multiple repository-scoped chats available from the existing workflow without switching context to Agent Manager.

local session tabssidebar chateditor-tab chatwebview tab state

What Happened

  • This PR changes chat session behavior in Kilo-Org/kilocode so local sessions are no longer replaced when users start parallel work in the same repository. It introduces durable local session tabs in the sidebar and editor-tab surfaces, keeping multiple repository-scoped chats available from the existing workflow without switching context to Agent Manager.
  • This PR changes chat session behavior in Kilo-Org/kilocode so local sessions are no longer replaced when users start parallel work in the same repository. It introduces durable local session tabs in the sidebar and editor-tab surfaces, keeping multiple repository-scoped chats available from the existing workflow without switching context to Agent Manager.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented persistent local chat-tab session handling by reintroducing real per-webview local tabs and stabilizing session state across tab creation and import paths, so local sessions are not replaced when new parallel sessions are started.

Why Track This

Why It Matters

Developers can continue multiple repository-level chats at once without one chat accidentally replacing another, so parallel investigation, coding, or debugging stays continuous instead of being disrupted by session loss. The change works by reusing the shared extension connection and restoring tab state per webview, with behavior aligned to Agent Manager session tabs; it should be monitored for regressions in session-state race handling during fast tab creation/import flows and cross-surface tab consistency.

Impact

Developers can continue multiple repository-level chats at once without one chat accidentally replacing another, so parallel investigation, coding, or debugging stays continuous instead of being disrupted by session loss. The change works by reusing the shared extension connection and restoring tab state per webview, with behavior aligned to Agent Manager session tabs; it should be monitored for regressions in session-state race handling during fast tab creation/import flows and cross-surface tab consistency.

What To Watch Next

  • Watch whether local session tabs becomes a repeated pattern.
  • Track follow-up changes around AI Integration in IDEs.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: parallel_session_race_conditions, tab_state_desync_across_webviews.
Open Topic TimelineOpen Technical EventOpen Original Sourceparallel_session_race_conditions / tab_state_desync_across_webviews / fallback_to_single_session_on_fast_session_open

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

Kilo-Org/kilocode PR #10466: feat(vscode): add local session tabs

The update adds durable local session tabs so users can keep multiple repository-scoped chats open, with stable tab/session state and alignment to Agent Manager tab interaction.