Bridgetek ESD for CodexBridgetek 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 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
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 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:
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 ( 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 ( 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 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
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 Usage Examples
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 AccessProject 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
Status and Troubleshooting
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 UninstallingAfter 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. |