agent-sessions-layout
Skill17 starsChanged 8 months agoMITView on GitHub
Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- OpenCortexIDE/cortexideword for word, first seen Oct 8, 2026
- gitpod-io/openvscode-serveredited, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 1
- OpenCortexIDE/cortexide★ 175100% same
Edited · 1
- gitpod-io/openvscode-server★ 6.2k84% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- launchSkill
- accessibilitySkill
- add-policySkill
- author-contributionsSkill
- auto-perf-optimizeSkill
- azure-pipelinesSkill
- chat-customizations-editorSkill
- component-fixturesSkill
- cpu-profile-analysisSkill
- fix-ci-failuresSkill
- fix-errorsSkill
- heap-snapshot-analysisSkill
- hygieneSkill
- integration-testsSkill
- memory-leak-auditSkill
- sessionsSkill
- tool-rename-deprecationSkill
- unit-testsSkill
- update-screenshotsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
When working on the Agents workbench layout, always follow these guidelines:
- Distinctive: line 14
Before making any changes to the layout code, read and understand the current spec.
- Very specific: line 27
If you modify the layout implementation, you must update LAYOUT.md to reflect those changes.
- Very specific: line 36
Update the Revision History table at the bottom of LAYOUT.md with a dated entry describing what changed.
- Distinctive: line 40
When proposing or implementing changes, follow these rules from the spec:
- Distinctive: line 77
After modifying layout code:
- Very specific: line 79
Verify the build compiles without errors via the VS Code - Build task
- Distinctive: line 80
Ensure the grid structure matches the spec's visual representation
- Very specific: line 82
Test that editors open in the ModalEditorPart overlay and that it closes properly
- Distinctive: line 83
Verify sidebar footer renders with account widget
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When working on the Agents workbench layout, always follow these guidelines:
1. Read the Specification First
The authoritative specification for the Agents layout lives at:
src/vs/sessions/LAYOUT.md
Before making any changes to the layout code, read and understand the current spec. It defines:
- The fixed layout structure (grid tree, part positions, default sizes)
- Which parts are included/excluded and their visibility defaults
- Titlebar configuration and custom menu IDs
- Editor modal overlay behavior and sizing
- Part visibility API and events
- Agent session part classes and storage keys
- Workbench contributions and lifecycle
- CSS classes and file structure
2. Keep the Spec in Sync
If you modify the layout implementation, you must update LAYOUT.md to reflect those changes. The spec should always match the code. This includes:
- Adding/removing parts or changing their positions
- Changing default visibility or sizing
- Adding new actions, menus, or contributions
- Modifying the grid structure
- Changing titlebar configuration
- Adding new CSS classes or file structure changes
Update the Revision History table at the bottom of LAYOUT.md with a dated entry describing what changed.
3. Implementation Principles
When proposing or implementing changes, follow these rules from the spec:
- Maintain fixed positions — Do not add settings-based position customization
- Panel must span the right section width — The grid structure places the panel below Chat Bar and Auxiliary Bar only
- Sidebar spans full height — Sidebar is in the main content branch, spanning from top to bottom
- New parts go in the right section — Any new parts should be added to the horizontal branch alongside Chat Bar and Auxiliary Bar
- Preserve no-op methods — Unsupported features (zen mode, centered layout, etc.) should remain as no-ops, not throw errors
- Handle pane composite lifecycle — When hiding/showing parts, manage the associated pane composites
- Use agent session parts — New part functionality goes in the agent session part classes (
SidebarPart,AuxiliaryBarPart,PanelPart,ChatBarPart,ProjectBarPart), not the standard workbench parts - Use separate storage keys — Agent session parts use their own storage keys (prefixed with
workbench.agentsession.orworkbench.chatbar.) to avoid conflicts with regular workbench state - Use agent session menu IDs — Actions should use
Menus.*menu IDs (fromsessions/browser/menus.ts), not sharedMenuId.*constants
4. Key Files
| File | Purpose |
sessions/LAYOUT.md | Authoritative layout specification |
sessions/browser/workbench.ts | Main layout implementation (Workbench class) |
sessions/browser/menus.ts | Agents menu IDs (Menus export) |
sessions/browser/layoutActions.ts | Layout actions (toggle sidebar, panel, secondary sidebar) |
sessions/browser/paneCompositePartService.ts | AgenticPaneCompositePartService |
sessions/browser/media/style.css | Layout-specific styles |
sessions/browser/parts/parts.ts | AgenticParts enum |
sessions/browser/parts/titlebarPart.ts | Titlebar part, MainTitlebarPart, AuxiliaryTitlebarPart, TitleService |
sessions/browser/parts/sidebarPart.ts | Sidebar part (with footer and macOS traffic light spacer) |
sessions/browser/parts/chatBarPart.ts | Chat Bar part |
sessions/browser/parts/auxiliaryBarPart.ts | Auxiliary Bar part (with run script dropdown) |
sessions/browser/parts/panelPart.ts | Panel part |
sessions/browser/parts/projectBarPart.ts | Project Bar part (folder entries, icon customization) |
sessions/contrib/configuration/browser/configuration.contribution.ts | Sets workbench.editor.useModal to 'all' for modal editor overlay |
sessions/contrib/sessions/browser/sessionsTitleBarWidget.ts | Title bar widget and agent picker |
sessions/contrib/chat/browser/runScriptAction.ts | Run script split button for titlebar |
sessions/contrib/accountMenu/browser/account.contribution.ts | Account widget for sidebar footer |
sessions/electron-browser/parts/titlebarPart.ts | Desktop (Electron) titlebar part |
5. Testing Changes
After modifying layout code:
- Verify the build compiles without errors via the
VS Code - Buildtask - Ensure the grid structure matches the spec's visual representation
- Confirm part visibility toggling works correctly (show/hide/maximize)
- Test that editors open in the
ModalEditorPartoverlay and that it closes properly - Verify sidebar footer renders with account widget
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.