[FEATURE] Per-tab IDE context isolation in VS Code extension

Resolved 💬 3 comments Opened Apr 7, 2026 by drabels Closed May 24, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When running multiple chat tabs in the VS Code extension, all tabs share the same ide_opened_file context. If I'm working with a file in Tab A, then switch to Tab B (an unrelated conversation), Tab B sees that file as the currently open file and may start commenting on it or offering to help with it.

This causes cross-talk between conversations — tabs react to files that have nothing to do with their context.

Proposed Solution

Scope the ide_opened_file context to the tab that was active when the file was opened/viewed, rather than broadcasting it to all tabs. Each chat tab should only see file context relevant to its own conversation.

Alternative Solutions

A simpler alternative: only inject ide_opened_file into the tab the user is currently interacting with, and suppress it for background tabs entirely.

Priority

Medium - Would be very helpful

Feature Category

IDE Integration

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗