Pimp My IDE / garage dispatchBack to the garage
October 8, 2026 / agent UX / parallel work

Four panes are still four write paths.

A session grid makes parallel agents easier to watch. It does not tell you which checkout, shell, or landing decision each pane owns.

Tile the work. Marshal the authority.
01 / FEATUREActive
workspace A
02 / TESTWatching
workspace A
03 / DOCSWatching
worktree B
04 / REVIEWWatching
no writes

The grid shows activity. The active-scope card keeps files, changes, commands, and landing custody tied to the selected pane.

The grid solves a real problem.

Visual Studio Code 1.141 adds a two-dimensional grid to the Agents window. You can drag sessions into horizontal or vertical splits, resize panes, maximize one session, and return to the grid.[1] That is better than opening every session to discover which one finished, stalled, or needs input.

The same release adds filters for environment, harness, and creating application.[1] Those are useful labels because a local session, a cloud session, and a remote-host session can sit beside each other while reaching different machines.

Visibility is not ownership. A tiled pane needs a named workspace and landing route.

The active pane changes the controls.

VS Code documents one active session at a time. Selecting a pane changes the chat, Files view, Changes view, terminal and tasks, and browser state shown by the Agents window.[2] The blue outline is therefore more than a focus decoration. It is a scope switch.

A reviewer should be able to answer four questions before typing into the active pane. Which folder or worktree is attached? Which changes belong to this task? Are commands still running there? Who will review and land the result?

Conversation borders do not separate files.

VS Code's session documentation says each chat has its own history, title, status, and model selection. Chats in one session still share the same workspace and code isolation. Both chats can edit the same files.[3] A clean pane border can hide that shared write path.

A linked Git worktree gives its checkout a separate HEAD and index, but the Git manual says it remains attached to the same repository and shares everything except per-worktree files.[4] Use worktrees to separate file edits. Do not call them complete security boundaries.

Make the handoff travel with focus.

Put a compact marshalling card beside the grid. When focus moves, update the visible session name, workspace identity, change scope, running-command status, and landing owner together. The card should show missing fields without inventing evidence.

The control below drafts that card. It does not inspect VS Code, create a worktree, read a shell, or confirm a merge. Its job is to prevent an attractive grid from becoming four unlabeled write paths.

Interactive makeover / session tabs plus handoff card

Marshal the active bay.

This replaces a plain grid focus outline with one active-scope route and four handoff fields. It is better because every pane change updates the same workspace and landing receipt. Native radios preserve one active session. Native checkboxes keep the handoff fields independent.

FeatureTestDocsReview

Session selector

Choose the pane that owns the next action. Then select the fields this handoff should request.

Active session
Handoff fields
Marshalling card / structure only

Active-scope receipt

FEATURE BUILD / LOCALShared checkout. Coordinate edits before two chats touch the same files.
0 handoff fields selectedSelect the fields this card should request. No runtime evidence is attached.
Sources read / October 8, 2026

Source log

Open the evidence boundary
  1. Visual Studio Code 1.141 release notes, released October 7 and read October 8, 2026. Microsoft documents the resizable two-dimensional session grid, maximize and return flow, and the new environment, harness, and creating-application filters.
  2. VS Code Agents window documentation, read October 8, 2026. Microsoft defines the active session and states that chat, files, changes, terminal and tasks, and browser state update with that selection.
  3. VS Code sessions and chats documentation, read October 8, 2026. Microsoft states that chats have independent conversation histories while chats in one session share the workspace and code isolation and can edit the same files.
  4. Git worktree manual, version 2.56.0 documentation read October 8, 2026. The manual says a linked worktree shares the repository except for per-worktree files such as HEAD and the index.

Evidence boundary: we read the release and product documentation. We did not install VS Code 1.141 or connect this teaching component to a live Agents window. The component produces a request template, not observed session state.