Skip to content

How Xodia works, from your repo to your live site

Xodia opens your site's repo in a private cloud preview, lets you and your AI edit it visually, saves every change as a git commit and publishes through the host you already use. Your code stays in your repo the whole time: Xodia reads it and writes to it, and never moves it into a platform.

Free plan. 14-day Pro trial. No charge unless you choose a plan.

The ask box under the canvas: a request about the selected heading is typed, the Agent panel's Activity tab lists each step the AI takes, and the opening hours appear on the page.

Step 1: Bring your site

Connect GitHub or start from a template

Install Xodia's GitHub App on the repositories you choose and import one, or start a new site from the Xodia template on Vite, React Router and Tailwind v4.

  • The GitHub App only sees the repositories you pick, and you can change that on GitHub
  • Projects started in Xodia keep their code in Xodia's own code storage until you move them to GitHub
  • Or open a folder on your computer with local folder mode

The New project dialog: the agent step done, then Import from GitHub with the repositories the GitHub App may open, each with Import, beside Start from a template.

Step 2: Xodia reads the stack

Xodia detects your stack and how much is visual

When the preview starts, Xodia reads the framework, styling, package manager, content source and host, and says how far visual editing goes on that stack.

  • Full visual editing on Vite + React, React Router, Remix, Next.js, Astro, Gatsby and HTML sites on Vite with Tailwind
  • npm, pnpm, Yarn and Bun, and monorepos on npm, Yarn or pnpm workspaces
  • Your AI gets the same facts, and the skill packs for that stack

See every framework and what you can edit

Settings, General: Xodia detected a Next.js site with TypeScript, Tailwind 4 and shadcn/ui, pnpm, Sanity and Vercel, and marks it Full visual editing.

Step 3: Edit

Edit visually or ask your AI

Your site runs in its own preview with your dev server. Click to select and type, style in the panel, or select an element and ask the AI you connected.

  • The visual editor: canvas, Style panel, Navigator, Variables and more
  • Your AI over MCP, with Xodia's tools and skills
  • Every change waits as a draft, autosaved to a private copy, never to your branch

The Xodia editor with Edit on: a pointer clicks a bakery site's heading and double-clicks it, the formatting bar appears, new words replace the old ones in place and the change shows as 1 unsaved.

Step 4: Save and review

Save to a branch and review it

Save turns the draft into a commit on this branch, another one or a new one. Each save becomes a restore point you can return to at any time.

  • Branches and pull requests for review on GitHubStarter and up
  • Restore any version from git and publishing

The Save changes dialog in Xodia: one change saved with its message to a new branch named preview.

Step 5: Publish

Publish through your own host

Publish merges into your live branch. Your host builds and deploys it exactly as it did before Xodia, and Xodia shows the result.

  • Deploy status and build logs from Vercel, Netlify and CloudflareStarter and up
  • Then check search and speed with the SEO tab

Settings, Publishing: the live site on Vercel with its address, and a failed build on the branch spring-hours with its error and Fix with your agent.

How it fits together

Your AI, Xodia, the preview, your repo and your host

Five parts, each doing one job. Your AI and your host are the ones you already use.

  1. Your AIClaude Code, the Claude app, Cursor, Codex or any MCP app, on your own subscription
    MCP
  2. XodiaThe editor in your browser and the MCP server your AI signs in to with OAuth
    Edits
  3. Preview sandboxYour dev server in its own cloud container, or on your computer
    Commits
  4. Your repoSaves land as commits on your branch, on GitHub or in Xodia's code storage
    Deploys
  5. Your hostVercel, Netlify and Cloudflare build and deploy the live branch
Your AI talks to Xodia over MCP. Xodia edits the files in the preview, saves them to your repo as commits, and your host deploys the live branch.

Where things live

Your code, your AI, your host

What stays with you, and what Xodia keeps and how. Read about security.

  • Your code

    In your own repo. Projects started in Xodia live in Xodia's code storage until you connect GitHub.

  • Previews

    In an isolated cloud sandbox per project that sleeps when idle. Pro and Agency can run previews in their own Cloudflare account.

  • Unsaved work

    Autosaved to a private copy, never to your branch, until you save or discard it.

  • Secrets

    Host tokens and environment variables are encrypted at rest. Variables go only to your dev server, never to your AI.

  • Your AI's login

    Stays with your AI app. It connects to Xodia over MCP and signs in with OAuth.

  • Your live site

    On your host, deployed from your live branch as before. The editor and previews are kept out of search engines.

Keep exploring

Bring your repo. Keep your host.