Skip to content

Latest commit

 

History

History
73 lines (56 loc) · 2.98 KB

code-server-extensions.md

File metadata and controls

73 lines (56 loc) · 2.98 KB

code-server Control Center

Agent Workspace presents one code-server Activity Bar entry for onboarding and daily operations:

  • extensions/control-center: five-step first-run guide plus Overview, Agents, MCP & Skills, Services, Desktop, Network, and Diagnostics pages.
  • extensions/selkies-desktop: embedded Selkies desktop support used by the Control Center's Open desktop action.

The UI is unified, while its components remain decoupled. Control Center reads the versioned workspacectl status --json contract and sends mutations back through workspacectl; proxy routing and service supervision therefore remain usable from a terminal or by any installed Agent.

The top bar switches between English and Simplified Chinese. The action updates the durable workspace locale and restarts code-server, so editor menus and Control Center change together.

Install or refresh the extensions inside a running container:

agent-workspace-manager install code-server-extensions

The installer packages source with VSCE, installs the VSIX files through the code-server CLI, and removes legacy standalone Services and Caddy sidebar extensions. Installed extensions are persisted under:

/config/.local/share/code-server/extensions

Reload the code-server window after an upgrade:

Developer: Reload Window

On a fresh profile, Control Center opens automatically until its guide is completed or skipped. It can always be reopened from the Agent Workspace icon or from Agent Workspace: Show Getting Started in the Command Palette.

The layout follows the active VS Code theme, uses a compact sidebar summary and a responsive editor-area dashboard, and collapses cleanly on narrow screens. Its operational pages are:

  • Overview: readiness, durable workspace, quick actions, and Docker boundary.
  • Agents: install or launch Codex, Claude Code, Hermes, and the same-origin DeepSeek Harness Web Agent.
  • MCP & Skills: inspect configuration across all four Agents, install global Skills through npx skills, and optionally use MCPM as the install-once MCP backend. Secrets remain in Agent environment/OAuth flows.
  • Services: filter and operate persistent user services and s6 services.
  • Desktop: Selkies runtime, editor integration, desktop session, and access.
  • Network: SSH access, custom-domain Caddy routing, private Tailscale access, proxy routes, and listening ports.
  • Diagnostics: capability state, environment checks, source update, and operation logs.

The historical extensions/service-manager and extensions/caddy-proxy-manager directories remain as reference modules, but normal installations no longer expose their separate Activity Bar containers.

Validate extension changes with:

node --check extensions/control-center/extension.js
node --check extensions/selkies-desktop/extension.js

Changes to package.json contributions must increment the extension version so code-server invalidates its manifest cache during installation.