EditorBrain

Editorial references, brand context and portable video projects for Claude Code and Codex. Requires Node.js 22+.

Inspect the CLI without configuring your agent:

npx [email protected] help

For a persistent installation:

npm install -g [email protected]
editorbrain login --url https://api.editorbrain.com
editorbrain status --url https://api.editorbrain.com
editorbrain projects list
editorbrain pull --project YOUR_PROJECT_ID --dir ./my-videos --url https://api.editorbrain.com
editorbrain skill install --dir ./my-videos --agent both

Create an account and follow connection instructions at https://editorbrain.com/app/settings. Login requires browser consent. Pull downloads only the selected project and its brand/style context, remembers the selection, and leaves reference evidence remote. Use documents list/get for additional saved documents; pull --all is an explicit full-workspace operation. Skills install locally: editorbrain handles context and library access; editorbrain-motion is loaded only for animation work; editorbrain-formats only for the selected editorial structure. All inherit the project identity and preferences. MCP authentication is configured separately. Preserve existing customized instructions and inspect installation conflicts. The package contains the CLI, skill documentation and an optional local DeepFilterNet3 helper, not private library content, customer credentials or the external model/runtime. The helper runs only when explicitly invoked; installation does not download or execute it. Editing and rendering use your agent's external tools.

Local production checks (0.12+)

Optional local commands inventory media, extract selected frames and check a render with separately installed FFprobe/FFmpeg on PATH. They do not install tools, upload media or call models. Output is compact by default; full reports can stay under .editorbrain-local/, outside document sync. Technical checks do not certify creative quality. Read the installed skill’s references/local-production.md only when needed.

Installation and permissions

• No install/postinstall hooks, runtime package dependencies, native binaries or background services. Installing the package does not register MCP servers or modify agent instructions.
• Configuration happens only when you run a command. skill install writes the selected project's skill files and instruction pointers; existing customizations are preserved and conflicts reported.
• login uses browser consent and stores the CLI credential in ~/.config/editorbrain/config.json (owner-only permissions on POSIX systems). This is a local credential file, not an OS keychain. Never share it or commit it.
• Remote commands contact the selected API endpoint. Use the official https://api.editorbrain.com endpoint. Commands such as push and media upload transfer the selected documents or assets; npm installation and help do not upload your projects.
• MCP uses separate OAuth consent in the browser. Do not paste secrets into chats or project files.
• Updates are explicit. Pin a version for reproducibility; do not bypass agent permission prompts or use sudo/--force to resolve installation conflicts.

Distribution is proprietary (UNLICENSED); publication on npm does not make the private service or library open source.

Documentation

Spanish guides: Getting started, CLI, API, MCP, and version availability. The web documentation requires the matching web deployment.

Updating EditorBrain

Run editorbrain update to update the npm CLI, current-project skills and existing global skills together. Check your installed help and the version guide before using advanced flags. Use update --dry-run to preview changes on current versions; consult the version guide for older installations. For a selected project, use an exact npm version followed by skill install --dir ./my-videos --agent both. Custom instructions are preserved; official replacements are backed up. Inspect conflicts and reload your agent's instructions afterward. Updates never change your brand or media.

skill install --global --agent both installs global skills without home-level AGENTS.md/CLAUDE.md. skill list lists registered destinations. skill pin protects the current project's instructions on this machine; use the returned exact-version npx command to preserve the CLI too. After the edit, skill unpin allows updates. No automatic updates run during editing.

Visual onboarding from Claude Code or Codex

For a new local brand, your agent can run these commands inside a dedicated project folder:

editorbrain onboarding create --brand my-brand --project my-first-video --dir ./my-videos
editorbrain onboarding serve --session <returned-session> --dir ./my-videos
editorbrain onboarding apply --session <returned-session> --file <saved-answers> --dir ./my-videos --dry-run
editorbrain onboarding apply --session <returned-session> --file <saved-answers> --dir ./my-videos
editorbrain skill install --dir ./my-videos --agent both

The form records your choices; it does not generate media or contact paid providers. The local server is temporary and loopback-only. The static HTML also supports downloading an answers file. Existing cloud brands should first pull their current project context; an empty local folder does not mean an empty account. Apply preserves notes and rejects stale files. After explicit login, use onboarding sync to send only that brand and starter context. Optional brain prepare proposes additional direction; review it before brain accept --reviewed. Read the installed skill's references/onboarding.md for the complete progressive workflow.