Awesome-omni-skill sessions
Agent Sessions window architecture — covers the sessions-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agent Sessions window.
git clone https://github.com/diegosouzapw/awesome-omni-skill
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/sessions" ~/.claude/skills/diegosouzapw-awesome-omni-skill-sessions && rm -rf "$T"
skills/development/sessions/SKILL.mdWhen working on the Agent Sessions window (
src/vs/sessions/), always follow these guidelines:
1. Read the Specification Documents First
The
src/vs/sessions/ directory contains authoritative specification documents. Always read the relevant spec before making changes.
| Document | Path | Covers |
|---|---|---|
| Layer spec | | Layering rules, dependency constraints, folder conventions |
| Layout spec | | Grid structure, part positions, sizing, CSS classes, API reference |
| AI Customizations | | AI customization editor and tree view design |
| Chat Widget | | Chat widget wrapper architecture, deferred session creation, option delivery |
| AI Customization Mgmt | | Management editor specification |
| AI Customization Tree | | Tree view specification |
If you modify the implementation, you must update the corresponding spec to keep it in sync. Update the Revision History table at the bottom of
LAYOUT.md with a dated entry.
2. Architecture Overview
2.1 Layering
vs/base ← Foundation utilities vs/platform ← Platform services vs/editor ← Text editor core vs/workbench ← Standard VS Code workbench vs/sessions ← Agent Sessions window (this layer)
Key constraint:
vs/sessions may import from vs/workbench and all layers below it. vs/workbench must never import from vs/sessions.
2.2 Dependency Rules
- ✅ Import from
,vs/base
,vs/platform
,vs/editorvs/workbench - ✅ Import within
(internal)vs/sessions - ❌ Never import
fromvs/sessionsvs/workbench - Run
to verify layeringnpm run valid-layers-check
2.3 How It Differs from VS Code
| Aspect | VS Code Workbench | Agent Sessions Window |
|---|---|---|
| Layout | Configurable part positions | Fixed layout, no settings customization |
| Chrome | Activity bar, status bar, banner | Simplified — none of these |
| Primary UX | Editor-centric | Chat-first (Chat Bar is a primary part) |
| Editors | In the grid layout | Modal overlay above the workbench |
| Titlebar | Menubar, editor actions, layout controls | Session picker, run script, toggle sidebar/panel |
| Navigation | Activity bar with viewlets | Sidebar (views) + sidebar footer (account) |
| Entry point | workbench class | class |
3. Folder Structure
src/vs/sessions/ ├── README.md # Layer specification (read first) ├── LAYOUT.md # Authoritative layout specification ├── AI_CUSTOMIZATIONS.md # AI customization design document ├── sessions.common.main.ts # Common (browser + desktop) entry point ├── sessions.desktop.main.ts # Desktop entry point (imports all contributions) ├── common/ # Shared types and context keys │ └── contextkeys.ts # ChatBar context keys ├── browser/ # Core workbench implementation │ ├── workbench.ts # Main Workbench class (implements IWorkbenchLayoutService) │ ├── menus.ts # Agent sessions menu IDs (Menus export) │ ├── layoutActions.ts # Layout toggle actions (sidebar, panel, auxiliary bar) │ ├── paneCompositePartService.ts # AgenticPaneCompositePartService │ ├── style.css # Layout-specific styles │ ├── widget/ # Agent sessions chat widget │ │ ├── AGENTS_CHAT_WIDGET.md # Chat widget architecture doc │ │ ├── agentSessionsChatWidget.ts # Main wrapper around ChatWidget │ │ ├── agentSessionsChatTargetConfig.ts # Observable target state │ │ ├── agentSessionsTargetPickerActionItem.ts # Target picker for input toolbar │ │ └── media/ │ └── parts/ # Workbench part implementations │ ├── parts.ts # AgenticParts enum │ ├── titlebarPart.ts # Titlebar (3-section toolbar layout) │ ├── sidebarPart.ts # Sidebar (with footer for account widget) │ ├── chatBarPart.ts # Chat Bar (primary chat surface) │ ├── auxiliaryBarPart.ts # Auxiliary Bar (with run script dropdown) │ ├── panelPart.ts # Panel (terminal, output, etc.) │ ├── projectBarPart.ts # Project bar (folder entries) │ ├── agentSessionsChatInputPart.ts # Chat input part adapter │ ├── agentSessionsChatWelcomePart.ts # Welcome view (mascot + target buttons + pickers) │ └── media/ # Part CSS files ├── electron-browser/ # Desktop-specific entry points │ ├── sessions.main.ts # Desktop main bootstrap │ ├── sessions.ts # Electron process entry │ ├── sessions.html # Production HTML shell │ └── sessions-dev.html # Development HTML shell └── contrib/ # Feature contributions ├── accountMenu/browser/ # Account widget for sidebar footer ├── aiCustomizationManagement/browser/ # AI customization management editor ├── aiCustomizationTreeView/browser/ # AI customization tree view sidebar ├── changesView/browser/ # File changes view ├── chat/browser/ # Chat actions (run script, branch, prompts) ├── configuration/browser/ # Configuration overrides └── sessions/browser/ # Sessions view, title bar widget, active session service
4. Layout
Use the
agent-sessions-layout skill for detailed guidance on the layout. Key points:
4.1 Visual Layout
┌─────────┬───────────────────────────────────────────────────────┐ │ │ Titlebar │ │ ├────────────────────────────────────┬──────────────────┤ │ Sidebar │ Chat Bar │ Auxiliary Bar │ │ ├────────────────────────────────────┴──────────────────┤ │ │ Panel │ └─────────┴───────────────────────────────────────────────────────┘
- Sidebar spans full window height (root grid level)
- Titlebar is inside the right section
- Chat Bar is the primary interaction surface
- Panel is hidden by default (terminal, output, etc.)
- Editor appears as a modal overlay, not in the grid
4.2 Parts
| Part | Default Visibility | Notes |
|---|---|---|
| Titlebar | Always visible | 3-section toolbar (left/center/right) |
| Sidebar | Visible | Sessions view, AI customization tree |
| Chat Bar | Visible | Primary chat widget |
| Auxiliary Bar | Visible | Changes view, etc. |
| Panel | Hidden | Terminal, output |
| Editor | Hidden | Main part hidden; editors open via into |
Not included: Activity Bar, Status Bar, Banner.
4.3 Editor Modal
The main editor part is hidden (
display:none). All editors open via MODAL_GROUP into the standard ModalEditorPart overlay (created on-demand by EditorParts.createModalEditorPart). The sessions configuration sets workbench.editor.useModal to 'all', which causes findGroup() to redirect all editor opens to the modal. Click backdrop or press Escape to dismiss.
5. Chat Widget
The Agent Sessions chat experience is built around
AgentSessionsChatWidget — a wrapper around the core ChatWidget that adds:
- Deferred session creation — the UI is interactive before any session resource exists; sessions are created on first message send
- Target configuration — observable state tracking which agent provider (Local, Cloud) is selected
- Welcome view — branded empty state with mascot, target buttons, option pickers, and input slot
- Initial session options — option selections travel atomically with the first request
- Configurable picker placement — pickers can appear in welcome view, input toolbar, or both
Read
browser/widget/AGENTS_CHAT_WIDGET.md for the full architecture.
Key classes:
(AgentSessionsChatWidget
) — main wrapperbrowser/widget/agentSessionsChatWidget.ts
(AgentSessionsChatTargetConfig
) — reactive target statebrowser/widget/agentSessionsChatTargetConfig.ts
(AgentSessionsChatWelcomePart
) — welcome viewbrowser/parts/agentSessionsChatWelcomePart.ts
(AgentSessionsChatInputPart
) — standalone input adapterbrowser/parts/agentSessionsChatInputPart.ts
6. Menus
The agent sessions window uses its own menu IDs defined in
browser/menus.ts via the Menus export. Never use shared MenuId.* constants from vs/platform/actions for agent sessions UI — use the Menus.* equivalents instead.
| Menu ID | Purpose |
|---|---|
| Left toolbar (toggle sidebar) |
| Not used directly (see CommandCenter) |
| Right toolbar (run script, open, toggle auxiliary bar) |
| Center toolbar with session picker widget |
| Submenu intercepted to render |
| Panel title bar actions |
| Sidebar title bar actions |
| Sidebar footer (account widget) |
| Auxiliary bar title actions |
| Auxiliary bar left title actions |
| "Open..." split button (Open Terminal, Open in VS Code) |
| Chat bar title actions |
7. Context Keys
Defined in
common/contextkeys.ts:
| Context Key | Type | Purpose |
|---|---|---|
| | ID of the active chat bar panel |
| | Whether chat bar has keyboard focus |
| | Whether chat bar is visible |
8. Contributions
Feature contributions live under
contrib/<featureName>/browser/ and are registered via imports in sessions.desktop.main.ts (desktop) or sessions.common.main.ts (browser-compatible).
8.1 Key Contributions
| Contribution | Location | Purpose |
|---|---|---|
| Sessions View | | Sessions list in sidebar, session picker, active session service |
| Title Bar Widget | | Session picker in titlebar center |
| Account Widget | | Account button in sidebar footer |
| Run Script | | Run configured script in terminal |
| Branch Chat Session | | Branch a chat session |
| Open in VS Code / Terminal | | Open worktree in VS Code or terminal |
| Prompts Service | | Agentic prompts service override |
| Changes View | | File changes in auxiliary bar |
| AI Customization Editor | | Management editor for prompts, hooks, MCP, etc. |
| AI Customization Tree | | Sidebar tree for AI customizations |
| Configuration | | Configuration overrides |
8.2 Service Overrides
The agent sessions window registers its own implementations for:
→IPaneCompositePartService
(creates agent-specific parts)AgenticPaneCompositePartService
→IPromptsService
(scopes prompt discovery to active session worktree)AgenticPromptsService
→IActiveSessionService
(tracks active session)ActiveSessionService
8.3 WindowVisibility.Sessions
WindowVisibility.SessionsViews and contributions that should only appear in the agent sessions window (not in regular VS Code) use
WindowVisibility.Sessions in their registration.
9. Entry Points
| File | Purpose |
|---|---|
| Common entry — imports browser-compatible services, workbench contributions |
| Desktop entry — imports desktop services, electron contributions, all modules |
| Desktop bootstrap |
| Electron process entry |
| Production HTML shell |
| Development HTML shell |
10. Development Guidelines
10.1 Adding New Features
- Core workbench code (layout, parts, services) →
browser/ - Feature contributions (views, actions, editors) →
contrib/<featureName>/browser/ - Register by importing in
(orsessions.desktop.main.ts
for browser-compatible)sessions.common.main.ts - Use
fromMenus.*
for menu registrations — never sharedbrowser/menus.tsMenuId.* - Use separate storage keys prefixed with
orworkbench.agentsession.*workbench.chatbar.* - Use agent session part classes, not standard workbench parts
- Mark views with
so they only appear in this windowWindowVisibility.Sessions
10.2 Layout Changes
- Read
first — it's the authoritative specLAYOUT.md - Use the
skill for detailed implementation guidanceagent-sessions-layout - Maintain fixed positions — no settings-based customization
- Update
and its Revision History after any changesLAYOUT.md - Preserve no-op methods for unsupported features (zen mode, centered layout, etc.)
- Handle pane composite lifecycle when hiding/showing parts
10.3 Chat Widget Changes
- Read
firstbrowser/widget/AGENTS_CHAT_WIDGET.md - Prefer composition over modifying core
— add behavior in the wrapperChatWidget - Use
observable for target state, not direct session creationIAgentChatTargetConfig - Ensure
travel atomically with the first requestinitialSessionOptions - Test both first-load (extension not yet activated) and new-session flows
10.4 AI Customization Changes
- Read
first — it covers the management editor and tree view designAI_CUSTOMIZATIONS.md - Lean on existing VS Code services (
,IPromptsService
,IMcpService
)IChatService - Browser compatibility required — no Node.js APIs
- Active worktree comes from
IActiveSessionService
10.5 Validation
- Check
task output for compilation errors before declaring work completeVS Code - Build - Run
for layering violationsnpm run valid-layers-check - Verify part visibility toggling (show/hide/maximize)
- Test editor modal open/close behavior
- Test sidebar footer renders with account widget