# Versions and availability

This guide was reviewed on **November 18, 2026**. Latest checked CLI release: **0.55.0**. npm and the API are verified; this guide uses the same checked package and skills. Check each channel before you update:

| Channel | Check | Result |
| --- | --- | --- |
| npm | `npm view editorbrain@0.55.0 version` and `npm view editorbrain version` | `0.55.0` available and latest |
| Public API | `GET https://api.editorbrain.com/health` | `0.55.0` verified; also check the tools your connection is allowed to use |
| Task guides and continuity | CLI/skills 0.55.0 and a compatible API/MCP | Start with the current task, prepare project context and keep valid approvals and scoped feedback |
| Context and corrections | CLI/skills 0.54.1 and a compatible API/MCP | Reads by task, compact context and comparison with the previous workflow; keeps authorizations and final review |
| Onboarding and teams | CLI/skills 0.53.0 and a compatible API/MCP | Adaptive start, personal integrations and storage instructions, editor limits and client review |
| Memory and delivery | CLI/skills 0.51.0 and a compatible API/MCP | Corrections captured as suggestions, scope confirmed by the user, and delivery that follows preferences and evidence |
| Resources and Tempo | CLI/skills 0.51.0 and a compatible API/MCP | Personal library with upload checks and brand vocabulary for transcription |
| Shared templates | CLI/skills, API/MCP and web 0.50.0 | Revocable link, chosen resources and an independent copy; sharing does not change projects or preferences |
| Guides and connection | CLI/skills 0.50.0 and updated MCP | Help by task and independent MCP/CLI paths; instructions are read when they are needed |
| Search and diagnosis | CLI 0.49.3 | Includes the 0.49.2 candidate improvements without changing its files |
| Atelier reviewer and help | CLI 0.49.1 | Look → Change → Send and the optional "How it works" guide; keeps notes, approvals and direct mode |
| Visual evidence and continuity | Requires CLI 0.49.0 and a compatible API | Published: delivery by artifact and context, review state and pending sync; keeps approvals and direct mode |
| Discovery by task | CLI/API/MCP 0.48.0 | Help by task, optional suggestions and an explicit summary; keeps the full context by default and creative decisions |
| Adaptive styles and captions v2 | CLI/API 0.47.1 | Published: preferred/required rules, per-project decisions, v1/v2 pins and local captions |
| Parallel work per project | CLI/API 0.46.0 | Push limited to the project, styles pinned by version and explicit conflict recovery |
| Private sample delivery | CLI/API 0.46.0 | `production submit`, retries with a receipt and a review tied to the exact context |
| Onboarding persistence | Requires CLI 0.45.2; matching web and API | Draft recovery, partial preferences and editorial confirmation after every piece of data is saved |
| Continuity compatibility | CLI 0.45.1; API contract kept | Explicit registered references, local search by folder and a partial push when documents are unsupported |
| Project discovery and continuity | Requires CLI/API 0.45.0; web 0.45.0 | Search by ID/name/topic, brand and activity, resume, v2 checkpoints and continuity of reviews and jobs |
| Vox voice catalog | CLI/API and web 0.44.2 | 12 voices with filters and samples; selection by brand on the web and by brand or project in the API, CLI and MCP |
| Transcription preference | CLI/API and web 0.44.0 | Tempo, your own AssemblyAI and Whisper online/local; editing with your own tools does not require EditorBrain credits |
| Team collaboration | CLI/API and web 0.44.0 | Web editing per project and permission changes with revision control |
| Optional voice cleanup | Skill 0.44.0 | Local DeepFilterNet3; its engine and model are installed separately |
| Chosen cloud review | Skill 0.44.0 | Respects the requested review surface and delivers playable samples |
| Local visual review | CLI 0.41.2: `production review-artifact` + `production review-open` | Light HTML, a separate video and a temporary local server |
| Adaptive getting-started guide | Included in CLI 0.41.0 | Update the installed skills |
| CLI authorization by account and several workspaces | CLI/API 0.50.0; migration 0162 applied | Discover your workspaces and keep each folder's link; an old credential may need you to reconnect |
| Favorites for animations, references and SFX | Personal taste signals in the context | The agent compares the relevant favorites without forcing them or ignoring exclusions; a new automatic ranking is not promised |
| Personal styles with resources and components | CLI/API 0.42.0 | Read `help` before you use [the new commands](https://editorbrain.com/en/docs/estilos-propios) |
| Cut review, karaoke, variants and disk diagnosis | CLI 0.43.0 | Technical help; creative quality still needs review |
| Image references in Prism Premium | API 0.43.0 | Check capabilities and authorize the job |
| Advanced update options | Routing of `--dry-run` and `--all` fixed in the current code | Use an updated version |

This page is a dated snapshot, not a live monitor. The API can evolve without bumping the version field for every adjustment; the field alone does not prove which flags, providers or charges are active.

## CLI and skills 0.55.0

**0.55.0 is published and verified on npm and the API.** The agent uses the guide for the current request: start, correct, resume, deliver or configure. These routes keep existing decisions and approvals instead of requiring every stage again.

Edit preparation brings together compact project context and continuity. Your corrections can be saved as feedback and suggested memory; confirmation still requires your choice of scope. Update the CLI and its skills between edits, keep local customizations and reload the agent instructions.

## CLI and skills 0.54.1

**0.54.1 is published and verified on npm and the API.** The agent's guides start from the task and read the references they need, instead of loading all of the documentation or repeating context reads by routine.

- Compact context avoids repeating identical information and keeps the complete editorial snapshot. Different data stays present.
- `workflow check --previous-context` accepts a previous workflow response to compare changes. Always check the current state: it is not a cache and it does not carry approvals to another version.
- When it corrects, the agent identifies the real scope and dependencies, keeps direction and evidence that are still valid, and checks what changed. A full audiovisual review of the final delivery and approval of that version are still required.

It does not change your preferences and it does not remove permission, spend, artifact or approval controls. The agent keeps creative freedom to adapt each video. These improvements are not yet a measured percentage of token or time savings: that comparison needs a separate benchmark.

To get the new guides, [update the CLI and its skills](https://editorbrain.com/en/docs/actualizar) between edits and reload the agent's instructions. MCP receives its guides from the service; it does not need a local skill install. Historical packages keep their original bytes.

## CLI and skills 0.53.0

**0.53.0 is published and verified on npm and the API.** It updates the adaptive start with resumable drafts, preferences and instructions for using the integrations available in the agent's environment. Personal connections keep their permissions and do not authorize spend by themselves.

It also includes the guides for [Storage](https://editorbrain.com/en/docs/material) and [Team](https://editorbrain.com/en/docs/proyectos-equipos): places by plan, monthly editor limits and client review of a specific version. Installing the CLI does not change the plan, the permissions or the workspace limits. Update the local skills and reload the agent's instructions; customizations and previous bundles are kept.

## Web/API news and CLI 0.52.0

The web already includes Welcome before onboarding, the redesigns of Home, Projects, My footage, Your brand, How you edit, Memory, My styles, Connect AI and AI tools; also an initial light theme, an optional dark theme and navigation with a presentation cache. This does not require an npm update.

The new [Studio](https://editorbrain.com/en/docs/revision), with comments by range or point, comparison and preference proposals, is already available through the API and MCP. **0.52.0 is published and verified on npm and the API**: it includes that local Studio, `preferences open`, updated skills, cleanup after approval and compact workflow by default. Also update the skills and reload the agent's instructions. Previous bundles are kept.

[Update CLI/MCP/skills](https://editorbrain.com/en/docs/actualizar) explains what updates on each path. Publishing a client does not enable quotas or billing by itself.

## Memory and delivery in 0.51.0

Real corrections can be captured as feedback and suggested project memories. Pending ones include text and recognized conflicts; confirming or promoting them requires choosing the scope. Preferences do not change by themselves. Delivery is checked against the exact file and the requested destination. See [Memory](https://editorbrain.com/en/docs/memoria) and [Studio](https://editorbrain.com/en/docs/revision).

## Projects and samples in 0.46.0

`push --project ID` syncs only that project's documents, without uploading brands, shared styles or drafts from other projects. `--dry-run` shows the same scope. If another session holds the folder, wait and retry when it finishes; keep the conflicts the result reports.

`projects pin-style --project ID` pins the style version for that edit. Later downloads recover that version, even if the shared style changed. Resuming checks the context of reviews and approvals: an earlier approval is not applied automatically to new documents.

`production submit --project ID --file sample.mp4 --title "First sample"` prepares a private MP4 copy and registers a review. It saves a local receipt so interrupted sends can be recovered without duplicating the file or the review. You can register A/B samples of the same context without invalidating the other sample's approval. Delivering a sample does not approve it; review the result and resolve any pending recovery before you continue.

## Compatibility in 0.45.3

The CLI and the API share the updated job and capability schemas. Available functions depend on your connection's permissions and capabilities; updating does not grant access to private functions. Earlier projects and packages stay compatible.

## Onboarding and email verification in 0.45.2

The web keeps custom fonts, colors chosen separately and drafts when a save is interrupted. Switching brands during a send does not apply its result to the new brand. Partial changes from MCP keep the rest of the declared context.

`onboarding apply` saves confirmations at the end; `onboarding sync` reviews every document before upload and checks the data again before it publishes the confirmation. If there is a failure or an incompatibility, review the receipt before you retry: documents that were already accepted stay saved, but they do not mean the complete setup is confirmed.

Email verification lets you request another link without guaranteeing the provider delivered it. If you opened an invitation and confirm your email in another tab, go back to the original tab to sign in and accept it. The private invitation link stays there.

## Continuity fixes in 0.45.1

`--primary-artifact` and `--dependency` register and hash the explicit files without repeating `--artifact`; omitted references keep their hashes. `projects find --local --dir DIR` limits the search to the registered canonical workspace, with no network, folder walk or automatic registration.

On a recognized type or schema rejection, `push` keeps the local document, continues with the compatible ones and returns `status: "partial"`, `synced: false`, `uploaded`, `skipped`, `warnings` and `next`, with exit code 2. Update the API as the result says and retry; revisions that were already uploaded are not duplicated. Do not reduce v2 checkpoints to v1. Validation, permission, conflict, server or network errors still stop the operation. `--dry-run` reviews local validity and revisions; it does not test the server's write compatibility.

## Continuity in 0.45.0

`projects find "topic" --brand ID` finds projects; `projects list --sort recent` orders them by activity the server recorded. For "yesterday," convert your time-zone interval to UTC `--since` / `--before` dates. Keep filters while you page and resolve ambiguous matches before you choose the ID.

`resume ID` recovers context and the checkpoint, keeps local conflicts and checks files. In MCP, use `get_project_continuity` after you resolve the project and verify the workspace. Check existing reviews, feedback and jobs before you produce again. `checkpoint --expected-checkpoint HASH` saves the next milestone without overwriting another session; `completed` is not video approval. Text can be synced with `push`; resuming does not download media, run the saved command or authorize spend.

`projects find "topic" --local` queries only this computer's private registry. `projects link` / `unlink` and `where ID` manage and check locations; the registry and the cache are not synced. Archiving a conversation does not delete the project's documents. Older projects stay readable while their documents and permissions exist; this release does not add project archive/unarchive and does not recover local files that were never backed up. See the [commands and limits](https://editorbrain.com/en/docs/cli#resume-a-project-without-depending-on-the-chat).

## Voices in 0.44.2

In **AI tools → Narration** you can listen to the samples and save a voice for the active brand. The agent reads the same catalog with `studio voices` or `list_vox_voices`; `studio voice` reads or saves the choice by brand or project. Quotes that omit `voice` inherit that preference, while they respect the project's constraints.

Looking up voices, listening to samples and saving a choice does not generate audio and does not spend credits. It also does not change a preference to keep the original voice or to skip narration. Each sample's language can differ from the language that is compatible for generation. The accent describes the original voice in English; it does not guarantee a regional accent in Spanish. See the commands, permissions and save steps in [AI tools](https://editorbrain.com/en/docs/herramientas-ia#vox-choose-a-voice-for-the-brand-or-the-video).

## Availability by account

`studio catalog`, `billing status`, permissions and `tools/list` say what you can use. No new real generation or charge was run to write these guides. Do not announce every tool as active just because its schema exists.

## Catalog versions

Scenes, components and media recipes have different catalogs. Use the version of the selected result, especially for inherited scenes. A scene ID does not become a component ID. Updating the CLI can widen the catalog without changing the files of an edit that is already pinned.

## Skill updates

Updating npm only changes the executable or package. Skill copies that are already installed need the update flow or `skill install` with the version you chose. Customized instructions are not replaced automatically. Restart or reload the agent's conversation so it uses the changes.

**Caution in 0.39.1:** there is a routing bug in `update --dry-run` and `update --all`. Do not use that command's `--dry-run` as a guarantee that it will not write on that version. To install a specific version, use npm and then `skill install` on the chosen project, reviewing its conflicts. This warning does not affect the dry-run mode of `pull` / `push`.

## Compatibility

Published artifacts are not rewritten. Keep exact versions during an edit and update between sessions. An improvement merged on GitHub still needs publication and deployment to reach clients. This documentation does not perform those operations.

## Adaptive styles · published in 0.47.1

Optional adaptive rules, captions v2 with a highlighter, a local preview and SRT/ASS export; `styles rules inspect/decisions`, `get_project_style_policy`, Swift/Shell as inert sources, `resume --project` and correction with `--parent latest`. These PR #158 changes were published in 0.47.1 through PR #159; they are not in npm 0.46.0. Check `help` and `tools/list` before you automate. There are no new permissions, spend or implied visual certification.

## 0.48.0 published · contextual discovery

Adds help by task, `get_task_guide` and optional suggestions in workflow. `workflow check --summary` / `detail: "summary"` orients without replacing the full context. In 0.48.0 the complete JSON was the default; 0.52.0 adds a compact representation without duplicates. Your own tools, preferences and creative decisions are kept. npm and the API are published and verified; the install also checks the distributed map and keeps each agent's customized instructions.

## 0.49.0 published · visual evidence and continuity

`production present` and the MCP evidence tools record delivery of an artifact for its exact context. Workflow shows the production and delivery conditions, reuses current approvals and keeps direct mode. Checkpoints and sync distinguish saved, pending and unknown work; a local receipt is a statement, not remote proof of playback.

npm and the API are published and verified. Update the CLI and skills; an existing MCP connection may need to reconnect to discover the new tools. These conditions do not grant spending authorization and do not certify visual quality.

## 0.49.1 published · Atelier reviewer and contextual help

The local artifact uses EditorBrain's Atelier logo and identity. "How it works" opens a short guide for proposals, samples or final delivery. You can close it and continue without losing comments. Help by moment explains how to attach a note to a second or make it general.

Look → Change → Send are views of the review, not new project stages. Copying or downloading prepares the answer: you must paste it into the chat so your agent can continue. It does not send media and it does not record an approval automatically. Update the CLI and skills to generate new artifacts with this design; existing HTML keeps its presentation and its data.
