A small setup.
A familiar timeline.

Check your setup.

• CapCut Desktop with an existing local draft. Mobile and web projects are not supported.
• Claude Code with your own access, or another agent harness supporting the Agent Skills convention. Both included installers support Claude Code and Codex.
• Python 3.10+ with virtual-environment support.
• FFmpeg and ffprobe available on your PATH.
• Enough space for Python dependencies, any local transcription model, and complete draft backups. First-time installation downloads can take several minutes.

v2.2.0 validation scope

Script regression checks use macOS 27, Python 3.11.9, and a CapCut Desktop 9.4.1 draft. They verify saved data and timing. This run does not establish Windows execution or final playback and export in CapCut. The seller-reported environments below are separate.

Seller-reported test environments

Reported September 16, 2026. Exact CapCut and Claude Code build numbers were not recorded. “Latest” describes the seller’s test report, not a guarantee for every future release. CapCut’s local draft format can change. If your setup differs, ask before buying.

Install once.

Download the ZIP from your purchase confirmation or delivery email. Extract it into a folder you can find again. Keep the installers, requirements.txt, and capcut-ai-editor folder together.

macOS

Install Python and FFmpeg first. If you use Homebrew, brew install python ffmpeg installs both. From the folder containing your downloaded ZIP:

unzip capcut-ai-editor-v2.2.0.zip
cd capcut-ai-editor-v2.2.0
bash ./install.sh

Windows 11 · PowerShell

Install Python 3.10+ with PATH enabled and install FFmpeg from its official distribution. Confirm python --version and ffmpeg -version work, then run:

Expand-Archive capcut-ai-editor-v2.2.0.zip -DestinationPath .
cd capcut-ai-editor-v2.2.0
.\install.ps1

If PowerShell blocks a downloaded script, inspect it first, then use Unblock-File .\install.ps1 and rerun it. Do not disable system-wide execution safeguards.

Using Codex or both agents?

On macOS, run bash ./install.sh --target codex or --target both. On Windows, run .\install.ps1 -Target codex or -Target both. The default is Claude Code. Codex installs use ~/.codex/skills/capcut-ai-editor.

What the installer does

Copies the skill to ~/.claude/skills/capcut-ai-editor on macOS, or %USERPROFILE%\.claude\skills\capcut-ai-editor on Windows. It creates a private Python environment inside the skill folder and installs dependencies there. It asks before replacing an existing skill installation.

Read the installation output: a missing Python environment or dependency failure needs fixing even if the installer exits. Restart your agent after installing.

Make the first edit small.

1. Open a short test project in CapCut Desktop. Generate auto-captions and save it. Keep a separate backup of important work.
2. Fully quit CapCut. The scripts refuse to edit while the app is running to avoid an autosave conflict.
3. Open Claude Code and ask it to inspect the project before changing anything:

“Use capcut-ai-editor to inspect my CapCut project ‘my_video’. Show me its caption tracks. Don’t change anything yet.”

Once the project and track are correct (regrouping needs single-word entries; otherwise use a word-timed transcript):

“Regroup the existing single-word captions in ‘my_video’ into readable 3–4-word phrases. White text, black outline, modest size, normal English spaces. No moving highlight or pop animation. Back up the project, preserve other tracks, and verify the result.”

Reopen the project in CapCut. Check spelling, timing, caption placement, and the rest of the timeline before exporting.

Other starting prompts

• “Detect silence in source.mp4 and show me the keep-segment list before making cuts.”
• “Add a title reading ‘Chapter 1’ at 0 seconds for 3 seconds.”
• “Add this prepared transparent overlay to my existing project.”

The cut command applies the edit list to one normal-speed, unsplit video clip before captions or overlays are added. Captioning then reads the saved timeline with --time-map auto. Multi-source or retimed arrangements need manual review. Export from CapCut after checking the result.

Know what comes with it.

The package edits existing projects. Background removal and asset sourcing are delegated to other tools when available. Local draft editing does not mean the agent provider runs offline.

Get back to your previous draft.

Write operations create a timestamped sibling backup folder before applying changes. Keep your own copy of anything irreplaceable.

1. Fully quit CapCut before touching draft files.
2. Locate the project and its project_backup_… sibling in the draft directory.
3. Copy both the current project and chosen backup somewhere safe, outside CapCut’s draft directory.
4. Move the current project folder outside the draft directory. Copy the contents of the chosen backup into a folder with the original project folder name at its original path. Do not merge the old and new contents.
5. Reopen CapCut and verify the restored project and media links. If it does not appear correctly, stop and contact support with the folder names and versions.

Default macOS location: ~/Movies/CapCut/User Data/Projects/com.lveditor.draft/

Default Windows location: %LOCALAPPDATA%\CapCut\User Data\Projects\com.lveditor.draft\

Your installation may use a relocated library. The skill supports an explicit draft root. Do not manually overwrite a single JSON file: CapCut can keep multiple draft mirrors.

When something gets in the way.

“CapCut is still running”

Quit CapCut completely and check for background CapCut or JianYing processes. Do not force a write simply to bypass the protection.

“Cannot determine whether CapCut is closed”

Process inspection was blocked or failed. Allow the agent to read the process list and retry. Unknown process state blocks writes; do not use a force flag to hide the failure.

Caption size or wrapping needs adjusting

v2.2.0 defaults to white, outlined text at font size 9 with no pop animation. Each phrase is one editable segment. Review long words and placement in CapCut; adjust the text size there or ask the agent for a smaller --font-size.

Project not found

Confirm this is a local desktop project and that the project name and draft root are correct. Ask the agent to list drafts before editing.

Missing Python package or FFmpeg

Confirm the installer finished successfully. The agent should use the skill’s private environment: venv/bin/python3 on macOS or venv\Scripts\python.exe on Windows. Check FFmpeg and ffprobe are on PATH.

Captions drift after a cut

Caption timestamps must be mapped from the original audio onto the trimmed timeline. Use --time-map auto with source timestamps. For timestamps already on the edited timeline, use --input-timebase timeline without a time map. v2.2.0 rejects missing maps on shifted timelines and captions beyond the project duration.

Draft will not open or a recent update breaks editing

Restore the backup. Send your software versions and the error to support. Do not repeatedly apply edits to a failing draft. Unsupported or unreadable draft formats require investigation.

Download link expired

Reply to your delivery email with the order reference. Replacement links are available for verified, non-refunded purchases.

Optional: let your agent review video.

The separate /watch skill by bradautomates extracts sampled frames and transcripts from a video for agent review. It can help discuss an existing clip or your exported result. It is not bundled, required, or part of the $49 package.

Follow its own installation guide. Sampled images use agent context and tokens. Its optional cloud transcription sends audio to the selected provider and may add usage costs. Sampling can miss a brief caption glitch, so still play through the final edit in CapCut.

A person on the other end.

Email phurip2006@gmail.com with your order reference, OS, CapCut and agent versions, and the exact error. Redact API keys and private project content. Installation help is included; custom editing work is not.

If a documented supported setup still fails after email help, request a compatibility refund within 7 days of purchase. Read the refund terms.