SpiderPublish

Edit your CMS like code. A headless CMS that lives in your IDE — VSCode, Cursor, and Antigravity.

Pull your tenant's pages, posts, components, and templates onto disk as files. Edit them. See exactly what changed with VSCode's native diff. Push with snapshot-bound preview→confirm. Deploy to the Cloudflare edge in seconds — without ever leaving your editor.

Most content platforms expect you to log into a dashboard and click around. SpiderPublish doesn't. It treats your content like source — version-controlled, diffable, file-based. Whether you're a developer, an AI agent, or an agency managing fifty client sites, the workflow is the same.

Install

VSCode (1.85+)

ext install SpiderIQ.spideriq-publish

Or: Cmd+Shift+X → search "SpiderPublish" → Install.

Cursor / Antigravity / VSCodium — available on Open VSX. Search "SpiderPublish" in the Extensions panel.

After install, run SpiderPublish: Sign In from the command palette and paste your SpiderIQ access token.

In one screen

$ spideriq auth request --email admin@your-company.com    # admin approves via email
$ cd ~/clients/acme-corp
$ spideriq use acme-corp                                  # binds folder ↔ tenant
$ code .                                                  # or cursor / antigravity

  Cmd+Shift+P → SpiderPublish: Pull
    pages/, posts/, components/, templates/  land on disk

  Edit pages/home.json
    Status bar:  📁 acme-corp · 1 changed · 0 undeployed
    Click the file in the Changes view → native VSCode diff opens

  Cmd+Shift+P → SpiderPublish: Push Content
    pre-push link audit  →  review panel  →  snapshot-bound confirm  →  live

  Cmd+Shift+P → SpiderPublish: Deploy Site
    readiness check → preview → confirm → Cloudflare edge in ~3s

That whole loop runs through a bundled @spideriq/mcp-publish MCP server (87 tools) — the same surface AI agents use in Cursor and Claude Code chat. Anything you can do here, an agent can do for you.

What's in 0.1.0

• Sign in with a SpiderIQ access token; multi-tenant project picker writes spideriq.json to bind a folder to one client.
• Pull parallel per-type GETs of pages, posts, components, templates with 3-way merge. Status bar reflects draft + undeployed counts.
• Stage / Unstage inline tree actions on the Changes view.
• Push Content in three phases: dry-run fan-out → consolidated review panel → confirm with paired tokens. Snapshot-bound confirm_tokens mean an agent can't accidentally delete your pricing page mid-review.
• Push Current File for tight-loop edits.
• Deploy Site runs readiness → preview → confirm → status polling.
• Pre-push link audit scans every published page and nav menu for broken internal links before the push fans out. Three-outcome modal: Review (focus Problems pane), Push anyway (log + continue), Cancel.
• Audit Links standalone command emits inline vscode.Diagnostic entries for registry-trackable broken links.
• "Accept redirect" Code Action appends the audit's proposed redirect to redirects.json. Idempotent.
• JSONPath → file:line diagnostics decode server validation errors at the exact JSON line where they happened.
• Native VSCode diffs via virtual URI providers — not a custom webview.

See the Changelog tab on this listing for full release notes.

Why this is different

Content as source, not a database. Every page, post, component, and template is a file on disk. git diff-clean. Reviewable in PRs. Reverted with one command.

Native VSCode diff for content. The actual VSCode diff editor, served through virtual URI providers (spiderpublish-baseline: for the last-pulled snapshot, spiderpublish-remote: for the live state). No custom webview.

Built for AI agents from the first commit. The extension delegates every backend call to a spawned @spideriq/mcp-publish subprocess. 87 tools, registered as Language Model Tools in Cursor / Antigravity, available in every agent chat.

Multi-tenant safe by default. spideriq.json per folder. The extension walks UP from the active editor's file (not the workspace root) to figure out which project you're editing — so an agency can keep fifty clients open in one window and never push to the wrong tenant.

Two-phase mutations, no surprises. Every destructive operation is preview-then-confirm. Snapshot-bound confirm_tokens pair the preview to the exact payload that requested it. The preview is what gets confirmed; nothing else.

Who this is for

• Agencies. Open one editor window, walk between client folders, push to whichever tenant is active. Per-folder spideriq.json keeps contexts isolated.
• Developers building AI-native content workflows. Bring your own agent (Cursor, Antigravity, Claude Code, Copilot) and it will already know how to use SpiderPublish.
• End-tenants who don't want to learn a CMS. Run the extension. Ask your agent to make the change. Hit Approve in the preview.

Documentation

• Public docs: docs.spideriq.ai/extension (install · commands · link-audit · troubleshooting)
• Agent guide (open-source): github.com/martinshein/SpideriQ-ai → SpiderPublish/AGENTS.md
• CLI counterpart: @spideriq/cli — same primitives, terminal-first

License

MIT — see the License tab on this listing, or the bundled LICENSE file.

Built where you work.