Knowledge base

Editing your site's files in the browser

Open a full VS Code editor on your site from the dashboard, ask the built-in AI about your code, and get back a file you saved over by mistake.

You do not need FTP, SSH or anything installed on your computer to change a file on your site. The editor is three clicks away and it works on your real files.

Open it

  1. Go to Hosting → Your websites and click the site.
  2. Under the site's name there is a row of tools: **WordPress Admin · phpMyAdmin ·
  3. File manager · Web editor · Visit site**.

  4. Click Web editor.

A new tab opens with your site's files already there. It is real VS Code, running on the server — extensions, search across files, git and a terminal all work.

If nothing happens when you click, your browser blocked the popup. Allow popups for the dashboard and click again.

If it says the link has already been used, that is normal and not a fault. Each link works once and lasts three minutes, so nobody can reuse one from your browser history. Go back to the site page and click the button again. Once you are in, the session lasts eight hours.

If your site does not offer the button, it is hosted on a platform where we do not run the filesystem. The file manager still works.

Ask the AI about your code

Press F1 and type Zinn, or right-click inside a file. There are six things it can do:

| | | |---|---| | Ask Zinn about this file | any question. Ctrl-Alt-Z | | Explain this code | what it does, and anything risky in it | | Fix this code | you say what is wrong, it proposes a correction | | Refactor this code | same behaviour, easier to read | | Complete this code | finishes what you started | | Write code from a description | writes something new in the style of your file |

The first two answer in a document beside your file. The other four propose a change — and this is the important part:

Nothing the AI writes is ever applied without you approving it. You get a side-by-side diff — your file on the left, the suggestion on the right — and a dialog with Apply and Discard. There is no setting that changes this.

If a suggestion would leave part of your file out, we refuse it rather than offering it. Applying that would delete whatever it stood for.

What it costs, and which model

It runs on the same AI balance as everything else on your account: your own provider key if you have added one, your Zinn® credit if not. You can see every question on AI → Usage, listed as AI in the editor.

By default we pick the cheapest model that can do the job, and that follows our price list — so when a cheaper one appears you get it without changing anything. To choose your own, press F1 → Zinn: Choose the AI model. The list is cheapest first.

If you break something — getting a file back

Every time you save a file in the editor, we keep the version you saved over. Up to twenty of them per file.

  1. Open the file.
  2. F1 → Zinn: Earlier versions of this file.
  3. Pick the time you want.
  4. You get the same side-by-side diff, and the same Apply button.

This is an undo, not a backup. It only covers files you edited in the editor, it lives inside your own hosting account, and it knows nothing about your database. For anything more than that — a bad plugin update, a database problem, a site you want back as it was last Tuesday — use Backups and restore.

The terminal

Press `Ctrl- ` for a shell on your own site. wp, git and php are there (composer` is not installed on the server today — bring it into your site's own directory if you need it). It can only ever see your own site's files: every site on the server runs in its own isolated view, so there is nothing else for it to reach.

Who changed what

Opening the editor, saving a file, applying an AI suggestion, restoring a version and opening a terminal all appear on your Activity page with the name of the person who did it. If several people on your team have access to a site, that is how you tell who changed the theme.

Still stuck?

Support is included on every plan and answers in your own language.

Contact support All articles
Editing your site's files in the browser