$ loading_
Understand the Agents window architecture for feature development and issue fixing.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "sessions" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/vscode/main/.github/skills/sessions/SKILL.md 2. Save it as ~/.claude/skills/sessions/SKILL.md 3. Reload skills and tell me it's ready
Based on the Agents window architecture, explain which layers, folders, and entry points I should modify to add a new session sidebar button, and provide a recommended implementation order and key considerations.
An architectural implementation guide covering relevant directories, extension points, steps, and development guidelines.
I have an issue where a menu event does not fire in the Agents window chat widget. Based on the architecture, identify the likely contributions, menus, entry points, and a debugging order.
A structured debugging checklist to locate likely causes and fix points for the broken menu event.
Summarize the Agents-first app layering, folder structure, and module responsibilities so a new team member can quickly understand Sessions development conventions.
An onboarding-style architecture guide explaining layer boundaries, folder responsibilities, and common development entry points.
MANDATORY: Before writing or modifying any code in src/vs/sessions/, you must read these documents:
.github/instructions/coding-guidelines.instructions.md — Naming conventions, code style, string localization, disposable management, and DI patterns..github/instructions/source-code-organization.instructions.md — Layers, target environments, dependency injection, and folder structure conventions.Then read the relevant spec for the area you are changing (see table below). If you modify the implementation, you must update the corresponding spec to keep it in sync.
| Document | Path | When to read |
|---|---|---|
| Layer rules | src/vs/sessions/LAYERS.md | Before adding any cross-module imports. Defines the internal layer hierarchy (core → services → contrib → providers) with ESLint-enforced import restrictions. Key rule: contrib/* must NOT import from contrib/providers/*. |
| Layout spec | src/vs/sessions/LAYOUT.md | Before changing any part, grid structure, titlebar, or CSS. Documents the fixed grid layout (Sidebar | ChatBar | AuxiliaryBar), part positions, the modal editor system, per-session layout state persistence, and the titlebar's three-section design. |
| Layout controller spec | src/vs/sessions/LAYOUT_CONTROLLER.md | Before changing LayoutController or per-session layout state. Details how the auxiliary bar, panel, and editor working sets are captured/restored when switching sessions, multi-session suppression, the auto-reveal-on-changes flow, workspace-folder ordering, and storage/migration. |
| Sessions spec | src/vs/sessions/SESSIONS.md | Before changing session/provider interfaces or data flow. Covers the pluggable provider model (ISessionsProvider → ISessionsProvidersService → ISessionsManagementService), ISession/IChat interfaces, observable state propagation, workspace/folder model, and session type system. |
| Sessions list spec | src/vs/sessions/SESSIONS_LIST.md | Before changing the sessions sidebar list. Covers the tree widget (WorkbenchObjectTree), renderers, grouping (workspace/date), filtering (type/status/archived/read), pinning, read/unread state, workspace capping, mobile adaptations, storage keys, and registered actions. |
| Mobile spec | src/vs/sessions/MOBILE.md | Before adding any phone-specific UI. Covers the mobile part subclass architecture, viewport classification (phone < 640px), MobileTitlebarPart, drawer-based sidebar, MobilePickerSheet, view/action gating with IsPhoneLayoutContext, and the desktop → mobile component mapping. |
| AI Customizations | src/vs/sessions/AI_CUSTOMIZATIONS.md | Before working on the customization editor or tree view. Documents the management editor (in vs/workbench) and the tree view/overview (in vs/sessions/contrib/aiCustomizationTreeView). |
MenuId.* from vs/platform/actions for Agents window UI. Always use Menus.* from browser/menus.ts.IObservable, not Event. Use autorun/derived for reactive UI, not onDid* event listeners.contrib/* code must never import from contrib/providers/*. Extract shared interfaces to services/ or common/.sessions.*.main.ts entry point to be loaded (for example sessions.common.main.ts, sessions.desktop.main.ts, sessions.web.main.ts, or sessions.web.main.internal.ts).…
Run vscode.dev locally to test the VS Code workbench and Agents window.
Create reusable SKILL.md skills that package repeatable workflows for future use.
Run and filter integration tests in the VS Code repo confidently.
Audit code for memory leaks and improper disposal across common lifecycle patterns.
Generate a structured .instructions.md file for project rules or conventions.
Validate Azure DevOps pipeline changes and troubleshoot builds and YAML faster.
Let AI agents operate Windows for files, apps, UI actions, and QA testing.
Analyze codebases and generate AGENTS.md files for AI coding agents.
Monitor multi-agent workflows with live calls, sessions, and usage observability.
Provide messaging rooms for AI agents to hand off context across environments.
Search Agent Architects knowledge base content and member profiles for AI workflows.
Build, run, inspect, and debug AI agents with better visibility.