Code Server SSOT

4 min read

An interface proposal · reviewed 7 September 2026

Concept — not built

OMP Workbench

The full OMP harness. One clear cockpit.

A proposed home for OMP inside VS Code. Follow the task, inspect the context, and review what changes — without making every detail compete for your attention.

The diagrams explain the proposal. The artwork explores its look. Neither is a screenshot of a working extension.

Concept diagram of an OMP Workbench cockpit: one task with Run, Stats, Team, Memory, Files and Skills panels. The intended flow is give a task, watch the work, then review the result.
Concept diagram · not a working interface One task at the centre. The detail stays within reach. Open cockpit diagram full-size

The cockpit

Give a task. Watch the work. Review the result.

The proposed interface follows that sequence. Panels reveal different kinds of context, rather than turning everything into another chat message.

  1. Give a task

    Start with the task and its commands in Run.

  2. Watch the work

    Follow usage, traces, people and agents in their own places.

  3. Review the result

    Inspect the changes and what will be shared.

Six panels. Different jobs.

Run
The task, commands and review.
Stats
Cost, usage and traces.
Team
Human collaboration and agents, clearly distinguished.
Memory
Full records, provenance and review before mutations.
Files
Selections, unsaved buffers, diffs and sharing, with explicit exposure of what leaves the editor.
Skills
Commands, rules, skills and their configuration sources.

Memory you can inspect

Find a record. Read the whole thing. Review a change before making it.

The proposal gives memory a readable workspace, with provenance beside the record. Some records are read-only; finding one does not imply permission to change it.

Concept diagram of the memory workflow: find a record, inspect its full content and provenance, then review a proposed mutation. Some records remain read-only.
Concept diagram · not a working interface Find → inspect → review. A record is more than a search preview. Open memory diagram full-size

Source boundaryMemory primitives exist in the reviewed source. A complete, reviewed memory curator is still a proposal.

Continuity, with boundaries

Closing a window should not be confused with stopping the work.

In this proposal, a supervised runtime would continue while the host runs, even when the editor window closes. Work needing approval would pause. That is a design intention, not an existing survival guarantee.

Proposed continuity diagram separating the editor window from a supervised runtime. Closing the window would leave work running while the host runs, with work paused when approval is needed. Reconnect and replay are not yet proven.
Concept diagram · not a runtime guarantee The window may close. The host still has to run. Approval still matters. Open continuity diagram full-size

Two artistic directions

The diagrams above explain the structure. These full-width studies explore the visual direction: dark navy, cyan, lilac and warm gold, with room to read.

OpenAI · cockpit direction

OpenAI-generated artistic design study for a proposed OMP Workbench cockpit inside VS Code. This is visual inspiration, not a functioning extension.
AI-generated design study — not a working interface A visual direction for the whole cockpit, not evidence of implemented panels. OpenAI · Codex image_generation · routing model gpt-6-astra; image model undisclosed · 7 September 2026 · WebP, 1536 × 1024. Open OpenAI artwork full-size

Grok · OMP + Luna Paint

Grok-generated artistic design study of OMP chat alongside a Luna Paint image-editing canvas and tools in VS Code. It imagines an explicit image-editing handoff, not automatic synchronization.
AI-generated design study — not a working interface OMP generates an image. A person edits it in Luna Paint. The edited version is explicitly attached back to OMP. xAI · api.x.ai · requested model grok-imagine-image-2.0; response did not identify the model · 7 September 2026 · WebP, 2816 × 1584. Open Grok artwork full-size

What the source supports

These are source-reviewed building blocks, not proof that this Workbench exists. The OMP links are pinned to commit ce90ff4f776139d2e4d2b51d30a599441a63f152.

RPC contracts
Session, subagent and host bridge contracts provide existing building blocks.
Stats server
An existing stats dashboard provides a starting point for usage and traces.
Collaboration handlers
The reviewed handlers are tied to the terminal UI. They need decoupling for a different interface.
Memory state
Memory primitives exist. They do not constitute a complete, reviewed curator.

The VS Code remote extension documentation explains the platform’s local and remote extension model. It does not verify this proposed OMP integration.

Not proven yet

  • Full command parity.
  • Reconnect and replay after interruption.
  • Permission and revocation behavior.
  • End-to-end installed compatibility.

A clear cockpit is the direction. The implementation still has to earn the claims.