sessions

Guides implementation and review of Agents Window changes under src/vs/sessions.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill sessions-basedgod55hjl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sessions
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/.github/skills/sessions
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill sessions-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working on the Agents Window in the VS-BRAX editor need to respect strict layering rules, provider-neutral contracts, and observable-based state modeling, and this Skill routes them to the correct specification and workflow before they write code. ## Core Features & Use Cases - Architecture Guardrails: Enforces layer direction (vs/sessions may import vs/workbench, never the reverse), provider neutrality, and observable-based session state. - Specification Routing: Maps each change area (layout, sessions list, mobile, providers, AI customizations) to its owning specification document under src/vs/sessions. - Proportional Validation: Directs focused unit tests, valid-layers-check, and targeted type checking based on the scope of the change. - Use Case: When adding a new session provider or modifying the sessions sidebar, use this Skill to identify the owning spec, trace existing implementations, and apply the contract without breaking layer boundaries. ## Quick Start Use the sessions skill to plan and implement my change to the sessions sidebar grouping logic under src/vs/sessions.

Frequently Asked Questions about sessions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make changes to the Agents Window in src/vs/sessions?▼

Start with src/vs/sessions/README.md, then read only the specification matching your change area, such as SESSIONS.md for the model or LAYOUT.md for workbench parts. Trace the current implementation and tests before modifying code, and keep changes within the owning layer.

What layering rules apply between vs/sessions and vs/workbench?▼

The vs/sessions layer may import vs/workbench and lower layers, but vs/workbench must never import vs/sessions. Run npm run valid-layers-check whenever imports or module ownership change to verify the boundary holds.

How should session and chat state be modeled in this codebase?▼

Model mutable session and chat state with observables, and use events only for notifications, never as a parallel state model or for control flow. Providers expose provider-neutral state through ISession and IChat interfaces.

Can shared Sessions code import provider implementations?▼

No, shared Sessions code must stay provider-neutral, and non-provider contributions must not import provider implementations. Provider-specific decisions belong inside the provider, such as the Copilot Chat or Agent Host provider directories.

When should a specification document be updated?▼

Update a specification when its architecture or durable behavior changes. Do not add implementation chronology, rejected approaches, or bug narratives; concrete behavior belongs in regression tests instead.