Skip to content
EditorBrainDocsEspañolOpen EditorBrain ↗

Account and help

Fix problems

Diagnose first and continue without duplicating work.

Download Markdown ↗

Start with a narrow check:

Terminal
editorbrain version
editorbrain status
editorbrain doctor --dir ./my-videos

To review local files only: editorbrain doctor --dir ./my-videos --offline. It does not repair or install tools automatically. Its blocks, warnings and next steps say what is missing for that specific task.

Common problems

What happensWhat to checkWhat to avoid
Expired session / 401Reauthorize the connection that failed: CLI or MCPPasting cookies or keys into the chat
My brand does not appearThe workspace from status or workspace_info, team permissions and the IDPicking the first brand because it looks similar
action_required while installingThe pending MCP step or project selectionRepeating the whole setup
I changed preferences and the agent uses the old onesworkflow check, local sync and a chat with the updated skillOverwriting documents to hide the conflict
Review or conflict 409Read the current version, reapply the intent and send a new revisionBumping expectedRevision blindly
Push partial / exit 2Read skipped and next; update the API and retry the pending documentsClaiming everything is synced, or deleting what was skipped
CHECKPOINT_UNSUPPORTEDUpdate the API so it accepts checkpoint v2; keep the local copyReducing it to v1 or deleting continuity fields
Invalid cursorDrop the cursor when filters change and use nextCursor intactDecoding it, inventing one or reusing it on another query
Animation not foundID, scene version and installed versionSubstituting another one without saying so
Preview does not loadAsk for an authorized link again; check format and networkSaving temporary links as permanent ones
Tool turned offstudio catalog and the integrations that are actually availableClaiming that installing the CLI turns it on
Not enough creditsQuote, balance and the route you choseMixing an external balance with EditorBrain
Search limitThe workspace search allowanceBuying credits on the assumption they add searches
429Wait for Retry-After and reduce concurrencyAn immediate retry loop
Uncertain job / timeoutLook up the same ID and historyStarting another generation and duplicating the spend
Local HTML on a phoneAsk for a web review copySharing localhost as a public link
My MCP does not show Studio or a new toolReload the connector and check tools/list and get_editing_guide; check plan and versionInstalling the CLI as a universal requirement
My skills keep personal changesReview attention_required, backups and the updater's destinationsDeleting .claude or .agents to install from scratch
Studio says the proposal is not appliedCopy it into the chat and confirm the scope before savingAssuming that editing the card changed the brand
preview_expired / 410Check the final, the history and retention; recover only an existing authorized copyRepeating a render or deleting the project without checking
Presenter cutout is not availableproduction matte-engines and the system's capabilitiesAssuming Apple Vision exists on Windows or Linux

Updates and known errors

CLI 0.45.1 separates recognized type or schema rejections from other HTTP 400 and 422 responses. Those others are still validation or request errors; review the document named with editorbrain validate. Authentication, conflicts, unsafe input, server and network stop the push and keep the writes that were confirmed. push --dry-run does not test whether the API accepts each schema.

A version's help can announce an option whose fix is still under review. See Versions and availability, especially the limits of update --dry-run and update --all in 0.39.1.

Talk to support

Open Support in your account to read the guides, talk and follow your case. Automatic assistance identifies itself as AI: it can explain the product, read the context of your own account and prepare a help request. Its answers rely on public documentation; the links let you check the source.

You can ask for a person at any time. When a person takes the case, the AI stops replying until the team explicitly returns it to automatic assistance. The case and its messages stay when you close the page. A submitted request does not guarantee a response time and does not confirm that a change is already done.

The support chat does not spend creative credits. Asking for help does not authorize a generation, another purchase, a plan change or a refund. Support AI does not run those operations. For prices, balance and subscriptions, also see Plan and credits; a help text does not replace the current state of your account.

If you cannot sign in, the chat is unavailable or you prefer email, write to soporte@editorbrain.com. If you already have a case, include its ID so the context stays together.

What to send to support

Include the CLI version, the error code, the project or job ID and the steps to reproduce it. Say what you expected and what happened. For screenshots, hide other people's personal data.

Do not send API keys, cookies, OAuth tokens, .env files or card data. Keep the ID of an uncertain attempt before you repeat it, so you do not duplicate jobs or charges. A problem with one video does not require deleting the brand, the whole cache or your original files.

Next in account and helpVersions and availability →