sessions

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

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Niiihuel/openide --skill sessions-niiihuel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sessions
Source: https://github.com/Niiihuel/openide/tree/main/vscode/.github/skills/sessions
Command: npx skills add https://github.com/Niiihuel/openide --skill sessions-niiihuel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working on the Agents Window in the OpenIDE codebase requires respecting strict layering rules, provider-neutral contracts, and a large set of architecture specifications; this Skill routes contributors to the right specification and workflow so changes under src/vs/sessions stay consistent. ## Core Features & Use Cases - Core principles enforcement: Preserves layer direction (vs/sessions may import vs/workbench, never the reverse), observable-based session state, and provider-neutral shared code. - Specification routing: Maps each change area (layout, sessions list, mobile, providers, AI customizations) to its authoritative specification document before implementation. - Proportional validation: Directs developers to run typecheck-client, the mandatory valid-layers-check, and focused unit tests matching the change scope. - Use Case: When adding a new session grouping feature to the sidebar, use this Skill to read SESSIONS_LIST.md, trace existing implementations, implement against ISessionsService, and validate with the layers check. ## Quick Start Ask the agent to implement or review a change under src/vs/sessions and it will apply the sessions workflow automatically.

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 or LAYOUT.md. Trace the existing implementation and tests, implement against the owning service contract, and validate with typecheck and the layers check.

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 after any import or module ownership change, since it is mandatory and catches violations.

When should I update an architecture specification document?▼

Update a specification only when component ownership, an interface or lifecycle contract, a state machine, persistence, or a cross-component invariant changes. Bug fixes, styling, copy, telemetry fields, and settings defaults belong in code and focused tests instead.

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, not as a parallel state model or for control flow. Consumers should derive UI state reactively from the observable session state.

Which validation commands should I run after a sessions change?▼

Run npm run typecheck-client for TypeScript compilation, never tsc directly, and always run npm run valid-layers-check. Add focused unit tests via scripts/test.sh --grep with a pattern matching the affected area.