LogoAwesome Skills
  • Search
  • Category
  • Tag
  • Blog
LogoAwesome Skills
LogoAwesome Skills

Discover Open-Source Agent Skills for AI Coding Assistants

Product

  • Search
  • Category
  • Tag
  • Blog

Resources

  • Claude Skill Docs
  • Antigravity Skills Docs

Tools

  • Claude Code
  • OpenCode
  • Cursor
  • Codex
  • Antigravity

Company

  • Privacy Policy
  • Terms of Service
  • Sitemap

©2026 Awesome Skills. All rights reserved.

Privacy PolicyTerms
Back to Skills

sessions

Agents window architecture — covers the agents-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agents window.

187,164stars40,944forksUpdated 7/7/2026
Web DevelopmentDocumentation#documentation#vscode#code-guidelines#typescript#architecture

Security Assessment

Safe(100/100)
Security Score100/100

About sessions

Internal engineering guidance for working on the Agents window in the VS Code source tree, specifically the code under src/vs/sessions/. It describes an agents-first application built by layering on top of the workbench, and it is meant to be loaded before implementing features or fixing issues in that window so changes follow the established architecture.

Before any code change it requires reading the repository coding-guidelines and source-code-organization instruction files, then the specific specification document for the area being touched. Those specs are enumerated in a table and cover the internal layer hierarchy (core, services, contrib, providers with ESLint-enforced import restrictions), the fixed grid layout and titlebar, the per-session layout controller, the pluggable sessions and provider model, the sessions sidebar list, the mobile part architecture, and the AI customizations editor. Any implementation change must be mirrored back into the matching spec to keep them in sync.

A large portion of the document is a catalog of common pitfalls drawn from real mistakes: using the wrong menu identifiers, using events where observables are required, importing from provider-only modules, forgetting to register new contributions in the correct entry point, and modifying shared workbench code instead of extending it. It is emphatic that timeouts and arbitrary delays must never be used to paper over ordering or state problems, that provider-internal services must stay isolated to their provider, and that comments should be kept minimal. Use it as the authoritative checklist when contributing to the Agents window.

FAQ

When should I use this skill?

When implementing features or fixing issues in the VS Code Agents window under src/vs/sessions/.

What must I read before changing any code?

The coding-guidelines and source-code-organization instruction files, plus the specification document for the area you are changing.

What is the internal layer hierarchy?

core to services to contrib to providers, enforced by ESLint import restrictions; non-provider contrib code must not import from contrib/providers.

Should session state flow through events or observables?

Through observables using autorun and derived, not Event or onDid listeners.

Are setTimeout or arbitrary delays acceptable to fix bugs?

No. The guidance forbids timeouts as fixes and says to drive logic off deterministic signals like observables, explicit events, or lifecycle phases.

Install sessions

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

microsoft/vscode

Related Skills

import-on-interaction

256

radon-mcp

296

investigating-incidents-with-aws-devops-agent

2,945

mantis-structural-index

2,518