Build on OX from VS Code — connect your eShop store's code, keep it in sync with the builder, preview it live, and give Claude Code and Copilot the OX tools.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Build on OX from VS Code. Connect your eShop store's code, keep it in sync with the builder while you
work, see the store live beside your code, and let Claude Code or Copilot build with the OX tools.
eShop is the first OX product in OX Developer; more join it here, in the same extension.
Get started in a minute
In the builder, open your store → Code → Connect → Open in VS Code.
VS Code opens (and installs OX Developer if it isn't there yet) and asks you to confirm the store.
Approve this computer in the builder tab that opens — check the code it shows matches the one in VS Code.
Done. The code is in ~/eShop/<your-store>, the folder opens, and syncing starts.
Nothing secret is copied or pasted. You can also start from VS Code: open the OX side bar and click
Connect a store (or run OX: Connect an eShop store… from the Command Palette, ⇧⌘P / Ctrl+Shift+P).
Type your company's name — the first part of your OX dashboard address, like beautiful777 — and click the
store in the browser tab that opens. Stores already on this computer are listed first, one click each.
While you work
Your saves reach the builder; the builder's changes reach this folder. The status bar shows where things
stand — ✓ OX · my-store in sync · ☁ OX · my-store 2 changes waiting · ⚠ OX · my-store 1 conflict.
Hover it for the details and one-click actions.
The OX side bar shows the same at a glance, lists conflicting files (click to open one) and keeps the
everyday actions one click away: the live preview, the builder, sync now.
Live preview — runs on your computer and opens beside your code; it refreshes as you save.
Your AI agent gets the OX tools on its own. Claude Code reads the folder's .mcp.json and CLAUDE.md;
VS Code's agent (Copilot) gets the same tools through VS Code. Ask for a page or a section in your own words —
the agent creates pages, checks its work and pushes it.
Publishing stays in the builder. Your changes land in the store's draft; publish there when it looks right.
Requirements
VS Code 1.101 or newer — or Cursor / Windsurf (installed from Open VSX).
An OX eShop store you can edit code in.
Nothing else: OX Developer runs its tools on VS Code's own Node.
Commands
Command
What it does
OX: Connect an eShop store…
Connect a store's code to this computer
OX: eShop: Open the live preview
Your store, live, beside the code
OX: eShop: Open in the builder
The store in the builder — publish from there
OX: eShop: Sync now
Send and fetch changes right away
OX: eShop: Disconnect this computer
Stop syncing and revoke this computer's access
OX: Get Started
The walkthrough
Security and privacy
You approve each computer in the builder (PKCE sign-in). The access token never appears on screen or on a
command line, and it reaches only this store's code — nothing else in your account.
Syncing starts only in a trusted folder: an untrusted folder could carry someone else's project link.
Disconnect stops syncing and revokes the access; you can also revoke any computer in the builder.
OX Developer talks only to your store's own server. It sends no telemetry.
Using a terminal instead
The same sync runs from a terminal with the eshop-code CLI — the builder's Code → Connect → Terminal tab
has the one command. The CLI and this extension never sync one folder at the same time: whichever started first
syncs, the other waits.
