Back to Signal Feed
CodeTracked since May 21, 2026

Add durable local session tabs for Kilo sidebar/editor chats

The PR introduces local session tabs for sidebar and editor-tab chat so multiple repository-scoped chats can stay open simultaneously instead of replacing the active session when users start parallel work.

local session tabssidebar chateditor-tab chatwebview

What Happened

  • The PR introduces local session tabs for sidebar and editor-tab chat so multiple repository-scoped chats can stay open simultaneously instead of replacing the active session when users start parallel work.
  • The PR introduces local session tabs for sidebar and editor-tab chat so multiple repository-scoped chats can stay open simultaneously instead of replacing the active session when users start parallel work.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Implements persistent local tab/session state per webview, reuses the existing shared extension connection, and restores tab behavior to keep multiple local chats stable across creation/import race scenarios while matching Agent Manager-style interaction.

Why Track This

Why It Matters

Developers running parallel repository tasks in Kilo can keep multiple chats open without losing an active conversation, so they can switch contexts faster and continue work without manual session handoffs. The change now centralizes local session lifecycle handling (tabs, state restoration, and shared connection reuse); operators should monitor for regressions in tab import/create races and cross-webview session synchronization, since those paths can still cause one chat session to shadow another if state conflicts appear.

Impact

Developers running parallel repository tasks in Kilo can keep multiple chats open without losing an active conversation, so they can switch contexts faster and continue work without manual session handoffs. The change now centralizes local session lifecycle handling (tabs, state restoration, and shared connection reuse); operators should monitor for regressions in tab import/create races and cross-webview session synchronization, since those paths can still cause one chat session to shadow another if state conflicts appear.

What To Watch Next

  • Watch whether local session tabs becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: local_tab_state_corruption_in_race_conditions, cross_webview_session_desync.
Open Topic TimelineOpen Technical EventOpen Original Sourcelocal_tab_state_corruption_in_race_conditions / cross_webview_session_desync / shared_connection_contention / agent_manager_alignment_regression

Supporting Evidence