cx-composer
❯ cx-composer workspace
Extensions in Workspace sidebar view: rows appear one by one showing each CX with deploy status (built / stale / not built) and last-modified time. Hover reveals inline build + validate icons; clicking a row opens the client-extension.yaml in the editor.
CX COMPOSER: Extensions in Workspace ● my-widget 1 ext · built · 12m ago ⚠ checkout-step 2 ext · stale · 3h ago ○ product-catalog 1 ext · not built ● hero-banner 1 ext · built · 2d ago → click any row to open its yaml, hover for build / validate
03 · Workspace

See every client extension in your workspace.

A sidebar tree lists every client-extension.yaml in the workspace with extension count, deploy status (built / stale / not built), and last modified. Click a row to jump to its yaml; hover for one-click build or validate. Auto-refreshes when you save or when a new .zip lands.

at a glance
# ────── step by step ──────

How Workspace works, in 6 steps.

    01

    Open the panel

    Activity Bar → the ❯ cx CX Composer icon → Extensions in Workspace shows up at the top of the sidebar.

    02

    Every CX in one list

    Every client-extension.yaml in your workspace, grouped by folder. Multi-block manifests are counted per-extension.

    03

    Deploy status at a glance

    ● built (green) — zip newer than sources. ⚠ stale (amber) — sources newer than zip. ○ not built — no zip yet.

    04

    Click to jump

    Selecting a row opens the yaml in the editor and reveals the folder in the Explorer.

    05

    Inline actions on hover

    Hover a row → build + validate icons appear on the right. One click, no context menu chase.

    06

    Auto-refresh

    FileSystemWatcher on client-extension.yaml and build/*.zip → the view updates when you save or when Blade emits a new zip.