VS Code Extension

The SpiderPublish extension brings your site into your editor. Pull your pages, posts, components, and templates to disk, edit them with full editor tooling, and push your changes back — with native diffs and the same preview-then-confirm safety as everywhere else.

Where to get it

The extension is published as SpiderIQ.spideriq-publish on both:

  • the VS Code Marketplace (for VS Code), and

  • Open VSX (for Cursor, Windsurf, VSCodium, and other compatible editors).

Search for "SpiderPublish" in your editor's extensions panel and install.

First run

  1. Sign in with your token (request one with spideriq auth request — see Authentication).

  2. Select your project — this binds the workspace, so the extension knows which site you are editing.

  3. Pull content — your pages, posts, components, and templates appear as files you can edit.

What it does

  • Tree view of changes — see at a glance what you have edited and what is not yet deployed.

  • Native diffs — review your changes against the live version using your editor's built-in diff viewer before pushing.

  • Push — stage changes, preview them, and confirm — the same safe flow as the dashboard.

  • Deploy — push your site to the edge without leaving the editor.

  • Link audit — check internal links before you push, and apply suggested redirects with a single action.

Why use the editor

If you live in VS Code or Cursor, the extension keeps you in flow: edit a template, diff it, push it, deploy — all without switching to a browser. And because it shares the same tools as the MCP server, AI agents in your editor can operate on the very content you have open.

Tips

  • One project per folder. The extension binds a folder to a project; keep separate sites in separate folders.

  • Diff before you push. The native diff is your last check that you are sending what you intend.

  • Audit links before launch. The link audit catches broken internal links before visitors do.

Next steps