Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Bridgetek ESD for Codex (Development)New to Visual Studio Code? Get it now.
Bridgetek ESD for Codex (Development)

Bridgetek ESD for Codex (Development)

Bridgetek

|
2 installs
| (0) | Free
Consent-driven local ESD MCP and canonical Skill integration for Codex CLI.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Bridgetek ESD for Codex

Bridgetek EVE Screen Designer (ESD) MCP integration as a Visual Studio Code extension — a Model Context Protocol (MCP) server and eight ESD Skills that help OpenAI Codex inspect ESD projects, discover widgets and components, plan user interfaces, author editable projects, and validate project structure and resources.

The extension bundles its own Python runtime, ESD MCP server and ESD Skills. No separate Python or Node.js installation is required to use the installed extension.

Interrupted setup recovery (0.0.21)

An extension-host restart or upgrade can interrupt configuration after components are installed but before completion is recorded. Version 0.0.21 resumes previously confirmed configuration through the existing installer lock, ownership checks and verification. It does not treat a saved pending flag as proof that installed components are broken. Pending state is cleared only after the selected components pass verification. A live installer retains its state and lock; modified/foreign components still stop with their specific actionable error. Changed paths still require confirmation.

If v0.0.20 reports Previous component setup did not complete after an upgrade, install v0.0.21 and reload VS Code. The existing selected configuration resumes automatically when automatic setup is enabled. The manual ESD: Configure Installed Components command remains available. No deletion of Codex configuration, Skills or VS Code state is required.

Two-stage setup notification (0.0.23)

After installing the VSIX, first activation in a trusted local Windows x64 workspace shows a native information notification when component setup is incomplete:

ESD MCP Server — Setup Required

ESD MCP Server has been installed successfully. Please configure the components you want to use with Codex.

The only action buttons are Configure Now and Later. Installation modes are not displayed in this notification. VS Code's native notification API provides one message field, so the requested title appears on the first line and the supplied message follows it. No Webview or custom notification UI is used.

Only Configure Now invokes the existing ESD: Configure Installed Components command. Its existing picker offers Full Installation (Recommended), MCP Server Only, and Skill Only. Select a mode, review the existing installation preview and choose Install. The existing workflow then installs, registers and verifies the selected components automatically. Verified success displays ESD MCP Server setup completed successfully. Restart/reconnect Codex afterward.

Later, dismissal, cancelling the mode picker, or cancelling the confirmation does not install/register components or mark setup complete. Notification history remains separate from installation/approval state and prevents repeated notifications on subsequent startups of the installed version. The manual configuration command remains available for later use. Existing valid installations retain their choices/configurations and continue verification/repair without a setup notification. The bridgetek.esd.automaticSetup preference still controls startup behavior; previously confirmed interrupted setup recovery is unchanged.

If setup fails, the existing error notification offers Configure Components to reopen the same workflow. Audit backups are retained. There is one component installer and one VSIX.

Selectable components (0.0.19)

One VSIX contains the MCP Server and all eight existing ESD Skills. After Configure Now (or opening the manual command), ESD AI Development Tools ? Setup offers:

Choice Installed integration
Full Installation (Recommended) MCP Server and all eight Skills
MCP Server Only MCP registration/private runtime; no discoverable Skill adapters
Skill Only All eight Skills, references and assets; no Python or MCP runtime deployment or execution

Select an option, review the affected configuration and adapter paths, then choose Install. Cancelling changes no installation state. Codex is the supported agent; authentication remains separate. MCP modes require a native Codex executable and installed ESD data. Skill Only requires Codex's Skill discovery location, without requiring its executable, Python, or ESD data for installation.

Use ESD: Configure Installed Components (bridgetek.esd.configureComponents) to switch modes or retry a failed setup. The legacy setup commands also reopen this selector. After confirmation, setup installs and verifies selected components, then removes deselected managed integration. Replacement verification occurs before removal, so a failure preserves existing valid components. Restart or reconnect Codex afterward.

MCP Server Only provides the existing MCP tools without the discoverable Skills that guide the complete development workflow. Internal canonical support files remain available for existing MCP validators; they are not registered as Skills. Skill Only supports all eight Skills' guidance and references. MCP-dependent discovery and validation require a configured, connected MCP Server; optional helper scripts have their own prerequisites. The adapters explain unavailable tools and never claim an operation or validation ran without evidence.

Existing 0.0.18 ownership receipts and saved approved paths are retained. Startup infers existing component selection from actual receipts rather than assuming Full Installation, and verifies/updates only selected components. Unknown ownership, modified files, ambiguous legacy scopes and incomplete MCP transactions stop with an actionable message. Setup never adopts a foreign same-name registration. Changed integration paths require confirmation. A failed operation records pending state and the last successful configuration in VS Code profile storage; choose Configure Components in the error notification to retry. Interrupted owned Skill writes can resume when every remaining file matches their journal. Modified journal/files require review.

Use ESD: Remove Managed Components (bridgetek.esd.removeComponents) to remove MCP integration, Skill integration, or both. Review the listed paths and confirm Remove. Skill removal works without Python or the MCP runtime. Only receipt-owned, unchanged adapter files and the owned MCP entry are removed. Canonical releases, profiles and audit backups are retained; this command is not a disk-space purge. Unrelated MCP servers, Skills, source files and ESD projects are preserved.

Run removal before uninstalling the VSIX. VS Code deactivation/uninstallation does not guarantee cleanup. If already uninstalled, reinstall the VSIX and use Remove Managed Components. If that is impossible, review esd-prototype-receipt.json at the selected Codex home and esd-skill-adapter-receipt.json at the selected Skill scope. Remove only their verified unchanged owned registration/adapters; do not replace the complete Codex configuration with an old backup or recursively delete a Skill directory containing user additions.

For errors, open Bridgetek ESD: Show ESD Integration Status and the Bridgetek ESD output channel. Ownership conflicts identify files to preserve for review. Missing owned adapters/canonical files can be restored from the verified bundle by retrying setup. Permission errors require an accessible selected location; no elevation or dependency installation occurs silently. Another active installer is never bypassed. Interrupted MCP ownership receipts require review rather than guessed rollback.

Quick Start

  1. Install the extension from your supplied VSIX file using Extensions: Install from VSIX..., or run code --install-extension <path>.vsix.
  2. Open a trusted local Windows workspace. On startup, choose Configure Now in the notification, then select Full Installation, MCP Server Only, or Skill Only in the component picker. You can also open the Command Palette (Ctrl+Shift+P) and run Bridgetek ESD: Complete ESD MCP and Skill Setup. Project access uses VS Code/Codex and OS filesystem permissions. No separate MCP folder authorization or folder-selection step is required. Report actual environment access denials without silently elevating.
  3. Review the displayed paths and permissions, then approve setup. The extension discovers Codex and the ESD data directory automatically, or asks you to select them when needed.
  4. Restart Codex or start a fresh Codex session to load the registered MCP server and ESD Skills.
  5. Ask Codex:
    • "List the available ESD widgets."
    • "Inspect my ESD project and explain its page relationships."
    • "Help me create an editable ESD car dashboard."
    • "Check my project's resource bindings and connections."

Requirements: Windows x64, VS Code 1.102.0 or later, for MCP modes a local native Codex executable and an installed EVE Screen Designer data directory containing Libraries, Examples and Examples/Advanced. The extension first looks for ESD data under the current Public Documents EVE Screen Designer directory. Codex authentication is managed separately by Codex.

Usage Examples

  • Explore ESD — ask Codex to list example projects, widgets and components, inspect widget properties, or explain how a native ESD widget works.
  • Inspect a project — ask Codex to review an .esdp project, its pages, source files, relationships and resources at an explicit project path under host/OS permissions.
  • Plan a user interface — describe the screen you want. The ESD Skills guide hardware configuration, requirements, implementation planning, widget selection and resource decisions.
  • Create or change an editable project — ask Codex to implement the agreed design in an approved project/output destination under host/OS permissions. Required hardware, design and resource decisions remain part of the workflow.
  • Validate project work — ask Codex to check implementation plans, project structure, component interfaces, connections and resource bindings. Static validation and native runtime verification are reported separately.
  • Use an approved template — ask Codex to list and inspect registered templates before creating a project from one. Template creation requires an approved, intact template and a safe destination under host/OS permissions; installed examples are not automatically approved templates.

You do not need to name an MCP tool or Skill in ordinary requests. Codex selects relevant Skills from their descriptions; starting a fresh session after setup helps it discover the installed Skills.

Project Folder Access

Project access uses VS Code/Codex and OS filesystem permissions. No separate MCP folder authorization or folder-selection step is required. Report actual environment access denials without silently elevating.

Opening a folder in VS Code does not authorize it automatically. Project creation remains disabled until a destination has been selected and approved. Source authoring does not require a template directory.

Optional VS Code Settings

Setting Purpose
bridgetek.esd.codexExecutable Override automatic discovery with the absolute path to a native Codex .exe.
bridgetek.esd.codexHome Override the Codex configuration directory. Otherwise uses CODEX_HOME or the current user's .codex directory.
bridgetek.esd.dataRoot Select the EVE Screen Designer data directory.
bridgetek.esd.skillWorkspace Select an explicit workspace for .agents/skills registration.
bridgetek.esd.projectDestinationRoots Select existing local project/output directories for approval through setup.
bridgetek.esd.templateDirectory Select a local approved-template registry directory containing templates.json.
bridgetek.esd.automaticSetup Enable or disable the startup setup offer and approved integration checks.
bridgetek.esd.diagnostics.enabled Control detailed local redacted MCP tracing. Run setup again and restart Codex to apply changes.

Status and Troubleshooting

  • Bridgetek ESD: Show ESD Integration Status — inspect the registered integration.
  • Bridgetek ESD: Diagnose ESD Integration — check discovery and configuration; review the Bridgetek ESD output channel for details.
  • If Codex cannot see the tools or Skills, complete setup and start a fresh Codex session.
  • If discovery fails, select the native Codex executable or ESD data directory explicitly.
  • If setup reports modified files or conflicting ownership, preserve the indicated files and receipts for review.

The current development documentation records outstanding clean-machine GUI installation and authenticated end-to-end Skill execution qualification. Successful setup or static validation alone does not verify simulation or hardware behavior.

Updating and Uninstalling

After installing an updated VSIX, use Bridgetek ESD: Complete ESD MCP and Skill Setup to update the owned MCP registration and Skills together, then restart Codex.

Before uninstalling, run Bridgetek ESD: Reset Owned ESD MCP and Skills Before Uninstall and approve the displayed scope. Then uninstall the extension normally. Reset removes verified owned integration and preserves unrelated files and audit backups. If already uninstalled, reinstall the extension to run the reset command.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft