Getting started with Webentor Studio

Invited by somebody? The invitation link signs you in and joins you to their team in one step; their projects are on your projects page afterwards.

Some deployments ask an operator to approve a new address first. If yours does, the sign-in page says so, and you are emailed once you are let in.

Choose the template Empty — I already have a repository to push, then push to the Git address on the project page (your email as the username, an API token as the password). The first push of the live branch finishes the setup: webentor.cloud.json sets the stack version, the content is indexed, and the first build starts. A push to the live branch is a publish, so that site goes online; a project made from a template waits until you press Publish.

studio connect does the same from a self-hosted project, and works with any Studio: yours, a partner’s, or Webentor Cloud. Give it the address you sign in at, and it asks the Studio where its API is.

Create branch on the project page makes the other kind of line: named, shared with everyone on the project, and kept until you delete it. Use one for a redesign or a campaign you will come back to over weeks. A branch can start from the live site or from a line you already have, and Merge on its page moves its work into the live branch or another line without publishing it.

A session nobody opens for a month is tidied away (archived, so its history stays), and you are told a week before. With a read-only role the button says View in editor and the editor opens without its controls.

From the keyboard: the outline of blocks is one tab stop. The arrow keys move through it, Enter selects, and Shift F10 or the menu key opens a block’s menu. Enter on a row of the Add tab inserts that block, and a block’s Drag block grip moves it with Space, the arrow keys and Space again.

When a block cannot show, the rest of the page stays. A block this project no longer has is a labelled placeholder you can select and delete, a block that fails says Block failed to render in its place, and a side panel that cannot show something offers Try again. Your unsaved changes are untouched.

Two people in one document see each other and where they are; undo takes back your change, not theirs. If the connection drops, Save waits (it reads Reconnecting…) and nothing typed on either side is lost. On a document nobody else is in, a save never overwrites a change made since you opened it: the editor merges the two and saves, and where you both changed the same thing it asks you to choose, with Keep mine or Take theirs. A reload does not throw away what you have not saved: the room keeps it until somebody saves or undoes it. If somebody merges or discards the draft you are in while you have unsaved changes, the page stays open and says so, so you can copy them first.

A tester is the smallest role: they open previews of their projects, read what changed and leave notes, but cannot open the editor or the repository, or publish. It is the role for a client who is checking.

While a build runs, the address says Preparing your preview and refreshes itself. Before anything is built on a line it says whether a build is on its way, or who has to ask for one. If the newest build fails, the address keeps showing the previous version, with a notice at the top of every page, until a build succeeds. The line’s page says why it failed.

An older version opens the same way: Preview this version shows it at its own permanent address without disturbing what is live.

Settings → Previews puts a passphrase over every preview of a project: the pages, the images and the still-building screen alike.

The assistant works on a line of its own, so your live site and your drafts are untouched. It hands you a preview link and a link to finish in the editor; the draft page leads with Continue in the editor. To bring one onto a draft you are already in, the draft page has Invite an assistant onto this draft. For a single project, its Connect an assistant button opens Settings → AI assistants. While its line is in review or scheduled, and once it is published or discarded, the assistant can no longer change it, so what you read is what goes live, and it starts a new line for anything further.

A content assistant edits pages, media and blocks, on every project you can open or the ones you tick, read-only or read & write, for as long as you choose (Create an assistant token on the AI assistants tab). A project assistant runs projects instead: it creates, configures, builds and deploys them, attaches domains and, only if you tick it, deletes them, at https://api.studio.webikon.eu/mcp. Claude Code, Claude and ChatGPT sign in to it with the lines above, and every other client takes a project assistant token from the same tab.

A block it makes is code, so a person publishes it. With Blocks & code an assistant can make or change the site’s block types on its own line, and it never publishes them, even on a project that lets assistants publish. The draft page shows that code file by file, with what the block checks said about each block (passed, failed with the first problem, removed, or not checked yet). Publish it from there once you have read it: the editor refuses to publish a line carrying an assistant’s code and sends you to the draft page, and until then it adds no raw HTML or script to that line either. A block the live site or another open draft still uses cannot be deleted, and the refusal names the pages.

Anything beyond a day of content, media and previews asks you to confirm who you are first. A client that signs in renews its own access and stays the same assistant (its project, its line and its budgets carry over) until the time you approved runs out. Every assistant has budgets (tool calls a minute, writes an hour, preview builds and generated blocks a day), and one that runs out is told when it can go on. An agent with several projects asks list_projects and picks one with use_project; to keep a client on one project, connect it to /mcp?project=team/project. Connected to one project, Cursor, VS Code, Gemini CLI and Codex name the server webentor-<project>, so a second project gets an entry of its own instead of replacing the first.

Revoke a token, or let it expire, and nothing can add to the lines it opened. They are tidied away a month later, and you are told a week before, so there is time to merge one or press Keep for longer on the project page. A pasted token that expires is told so when it next calls, and Reconnect for a day beside it on the AI assistants tab gives it a new secret to paste; its line carries on.

Then just ask: “What blocks can this site use?” · “Rewrite the pricing page on a fork so I can compare”. Claude Code also offers ready-made prompts as slash commands: /new_page, /edit_page, /try_on_a_fork, /review_draft and more.

Every row is written in the same transaction as the thing it describes and carries a hash of the row before it, so removing or changing one shows. Verify the record on a team’s Activity page walks the whole chain; a daily check does the same. Rows are kept for two years, and those about access and credentials for three. If platform staff ever open your account, that is a row in your record too.

Inside the editor, Activity beside the avatars shows the same rows for the line you have open.

An update moves only the packages the project already has, each to the version its release was proved with, and adds nothing new. The lockfile is regenerated in a build of its own; if it would not install exactly the release, that build fails and says why. Notifications tell you when a newer release is available, or when a security or data advisory names yours. This Studio’s operator may have opened the draft already; it is called Upgrade to Webentor ….

Configuration files that came from the template, such as astro.config.ts and its neighbours, are offered, never taken: nothing is ticked, and each shows the difference its tick would write. An older template copy is a clean update. A file marked customised is your own work, which the tick replaces wholesale, so it asks for a second tick beside the warning. Your content types (src/content-types.ts) and hosting settings are never on the list, and pnpm-workspace.yaml is merged. A project already on this Studio’s release can take the files alone, with Take these files.

A package moved off the project’s release by hand shows on its page as a custom package, by name; the update puts it back, in a draft called Reset to Webentor …. A fix reaches a site only in a release, so when a newer one is out than this Studio offers, the update page says it arrives once this Studio is updated.

A project that keeps a yarn or bun lockfile can be updated too, though this Studio does not regenerate that file: the draft moves the pins where yarn or bun reads them, and sets an install line that reads the lockfile if the build’s own line ignores it. A project that cannot be updated from here, such as one whose build installs with --frozen-lockfile from a lockfile this Studio cannot regenerate, says why on its update page.