Projects and workspaces

A project holds a graph and its work. A workspace groups projects, for example by client, series or campaign. Each project belongs to one workspace; a new project without a specified workspace goes into your default workspace. The studio supports personal workspaces and shared workspaces with one owner and read-only members.

Find the right project

list_projects returns the projects available to the account behind your MCP key. Each entry includes its name, ID and workspace ID. A browser URL is included when the project has one.

Pass that returned URL or ID to read_project_graph. The tool returns the graph and its revision: the version you have just read. When you later make graph changes, based_on_revision lets the studio reject an edit if someone has changed the project in the meantime.

A regular project link requires an account with access to the project. Possessing that URL does not add someone to a workspace or grant editing permission.

To verify an agent’s project reference, read it through MCP. A browser page loading at a correctly shaped studio URL does not prove that the key can read or change that project. A viewing invitation does not grant another account’s MCP key or editing permissions.

Organize your projects

Open All projects… from the studio menu to create, open, rename or delete your own projects, or copy one as a clean template. Use ＋ Workspace to create a workspace. The compact workspace switcher is available from the first workspace so you can open Members immediately. With two or more workspaces, the project manager also shows a workspace rail.

The studio remembers the last open project in each workspace. The project manager can move a project to another workspace. Deleting a workspace moves its projects to another workspace rather than deleting them; the last workspace cannot be deleted.

Your personal collection stays private. The workspace library contains materials used by its projects and materials the owner explicitly adds to that workspace. Adding a material shares a reference to it; it does not create a separate copy.

Invite your team

Open Members (Участники) beside the project name or in All projects…. Members are available in your first workspace too. The list shows real names, the owner and viewers; these avatars do not indicate who is online.

Only the owner can create an invitation, revoke a pending invitation or remove a member. Invite someone creates a single-use link valid for seven days. Send it to the intended person. That person signs in through the existing Google or Telegram login and explicitly chooses Join workspace. Opening the link or signing in does not add membership by itself. If a link has expired, was revoked or was accepted by someone else, ask the owner for a new one.

A member can open every project and the Library of that workspace. The studio uses the same canvas, node inspector and library tabs, with a View only label. Viewers can move around the canvas, read full user prompts and inspect results and media. Only the owner can change projects, upload or add materials, run a generation, use paid actions or manage sharing. Membership does not share a wallet or grant an MCP key editing permission.

The shared library includes images, video, audio, documents, elements, prompts, styles, generators, voices and skills that belong to the workspace scope. Owners can add or remove an explicit link to one of their materials from the existing library after confirming who will see it. A material still used by a workspace project remains visible even when its explicit library link is removed.

Removing a member closes future requests. An open viewer checks access again on focus and periodically while visible; on rejection it clears the graph, details and media. Data someone already received cannot be recalled from their device.

Show one project by link

Choose Share project (Поделиться проектом) at the right end of the studio toolbar or in its project-manager row. Link access starts off. Turn it on to create a public Shared Project link: anyone with the link can inspect that one project in the same studio canvas without signing in.

The public view includes the canvas, user prompts and results and media needed by that project. It does not open other projects, the workspace library, members, account data or protected internal instructions. It cannot edit or run the project.

Allow the download button is a separate option and starts off. Hiding that button is not copy protection: a browser has already received displayed media. Replace link invalidates the previous link; turning link access off closes it. A public view that detects revocation clears its project content.

Press ▶ on a ready video in the canvas to play it; press it again to stop. Select a node to see Download result in its node toolbar when downloads are allowed. Playback remains available when the download button is off; nodes without a result have no ready file.

While a project opens

A thin line below the studio header shows that the project is opening. Once its graph appears, Previews X of Y counts unique image and video previews. You can already move around the canvas, select nodes and play a ready clip while the remaining previews load. An ungenerated clip or audio without a visual preview is not counted as a pending preview.

The line disappears when all previews are ready. If a preview fails, the status shows how many could not load; Retry retries those previews. Project connection or access errors use their own message and retry control. Loading status does not grant editing or execution permission.

Keep background information in the right place

Project lore is background information for one project. Shared workspace lore supplies documents to the text nodes of projects in that workspace: for example, a series bible, brand facts or a recurring voice.

Use project lore for the particular episode or brief. Use shared lore for information that should follow every project in that workspace. Moving a project also changes which workspace lore it reads.

The interface calls project lore Project lore… / Лор проекта…. It opens from ⋮ → Project and from the book button Project lore / Лор проекта in the canvas dock at the bottom, next to the library. MCP provides get_workspace_lore and put_workspace_lore for shared documents, and lore_standard and write_lore for the lore wizard below; these are separate from reading the project graph.

Build shared lore with the wizard

The Lore wizard (Мастер лора) builds the shared lore of a workspace step by step. Open Project lore… and, in its shared lore part, choose Build step by step (Собрать по шагам). The wizard writes only to the shared lore of the open project’s workspace, so its documents reach every project in that workspace.

Document	What it holds	Steps
World (Мир)	One document for all videos of the workspace.	Premise of the world★, Audience★, Characters and how they relate★, Places, Rules of the world and taboos★, Tone and language★
Format: ‹kind› (Формат: ‹вид›)	The rules of one kind of video. Add one Format per kind, or none.	Kind of video★, Length and number of scenes, How an episode is built, Must-have devices and what to avoid, Production: music, captions, who speaks, Ideas for future episodes
Episode log (Журнал выпусков)	Optional: the videos that are already out.	Episodes: one line per episode — title · what it is about · how it ended · devices

★ marks a required step. While a required step is empty, Write to the shared lore stays unavailable and names the first missing step. Do not describe characters’ looks here: the Element and its character sheet hold them.

The kind of video is one of five: a story (an episode of a series, a sketch, a short film), a music video for a song, a product ad, an explainer or tutorial, or other. For “other”, name the kind in your own words. Each Format document starts with a scope line that the studio writes, not you: the rules apply only to videos of this kind, and when the brief asks for another kind of video they are not to be applied. You cannot forget or mistype this line.

Start from a text

from a text (из текста) sorts a ready document, such as a series bible, a brand book or a long note, into the steps. Pick a document of the shared lore, paste a text or upload a .md or .txt file, then press Sort into steps (Разложить по шагам). Sorting is one paid call to a text model, charged at the rate of a text call; the button shows the price before you press it. It replaces everything already entered in the steps, and the wizard says so beforehand.

Every line of the source ends up in one of the steps or in Not sorted — N lines (Не разложено). Lines left there go into the World document as a separate section called “Not sorted”; move them to the right steps or leave them. Review the steps after sorting: the model chooses where a line goes, so a line can land in the wrong step. Every sort, including Sort again for the same text, is a new paid attempt at the shown price; an earlier answer is not reused.

Preview and write

The preview shows each document in full, as it will be stored and sent to the reading nodes, with its size, the total shared lore against its limit and the documents that will be turned off. The same summary stays next to the write button on every step.

Write to the shared lore is free: it saves the documents and calls no model. The wizard’s documents go first and enabled, and the other documents of the shared lore stay as they were. Writing again replaces the wizard’s own documents rather than adding copies; a Format removed from the draft is turned off, not deleted. After sorting a document of the shared lore, writing turns that source document off; it is not deleted. Before you write, the wizard names the nodes of this project that will become stale, and nothing runs by itself. Writing is unavailable while a run is in progress. When you open the wizard again, it reads its documents back into the steps.

Let Vini lead

In Ask Vini, the copilot can take you through the same steps one question at a time and then offer a card with Open the wizard (Открыть мастер). The wizard opens with Vini’s answers laid over the current shared lore. Check them and press Write to the shared lore yourself: Vini proposes lore but does not write it. For a ready document already in the shared lore, Vini offers to open the wizard from a text, where you press Sort into steps. Opening the wizard from the card costs nothing. See working with Vini.

An external agent follows the same standard through MCP; see libraries and lore.

Start with inspection

The first-read walkthrough covers finding and reading an existing project. If the account has no projects, it stops there. Creating or moving projects belongs to the building workflow and needs the corresponding key permission.

Continue with libraries and lore for shared documents, or graph editing for revision-aware changes.

Last checked: 24 October 2026. Team sharing extends the existing studio canvas and library; the earlier separate viewer interface is removed.