Edit Videos with AI

Edit a talking-head video using transcript edits, style analysis, and feedback.

Introduction

30 Second Summary

A phone video can have a strong idea while long pauses still slow it down. The pace of a creator you admire can feel obvious until you try to identify each edit behind it.

In this project, you will turn one talking-head clip into a styled short video with cooked. You will direct the final result through a saved style plus hands-on revision.

What You'll Build

You can play one finished talking-head video whose pacing plus visuals reflect the reference format you chose.

By the end of this project, you'll have:

A named editing style that opens to show the caption, zoom, cut, card, plus sound choices measured from six matching references.
A transcript-controlled cut that you can reshape by cutting or restoring spoken words.
A downloaded final video that shows visible fixes from timestamped feedback before you approve it.
Secret Mission: Turn useful notes from this edit into reusable rules for your saved style.

Are there any prerequisites?

You need a Mac, Windows, or Linux laptop with internet access. You also need a Claude account with a paid plan or API key, one MP4 or MOV talking-head clip, plus six short-video links that share one editing format.

Before We Start

Before any setup begins, this is your moment to commit to the clip and editing format you want to create. Choosing one source clip, six matching references, and a one-sentence target gives every later editing decision a clear direction.

Set Up cooked.

Your source clip is ready. Your six references already point towards one editing format.

This step installs Claude Code with the cooked. plugin. The setup prepares your laptop to analyse those references and edit your video.

In this step, get ready to:

Get Claude Code running in an authenticated terminal.
Get cooked. running from a dedicated Desktop library with its local tools ready.
Store or skip the optional Gemini and ElevenLabs API keys.

Install and open Claude Code

A terminal is a text window where you give your computer commands. Claude Code runs in this window while cooked. opens its visual editor in your browser.

macOS

Press Cmd+Space to open Spotlight.
Type Terminal into Spotlight.
Press Enter to open Terminal.

Install Claude Code with its native installer by running this command:

curl -fsSL https://claude.ai/install.sh | bash

What does this command do?

This command downloads the official Claude Code installer. The installer adds the Claude Code command to your laptop.

Verify the installation by running this command:

claude --version

What does the check prove?

This command asks the installed Claude Code application for its version. A version number confirms that your terminal can find it.

You should see a Claude Code version number in Terminal.

Windows

Press the Windows key to open Windows Search.
Type PowerShell into Windows Search.
Press Enter to open PowerShell.

Install Claude Code with its native installer by running this command:

irm https://claude.ai/install.ps1 | iex

What does this command do?

This command downloads the official Claude Code installer. The installer adds the Claude Code command to your laptop.

Verify the installation by running this command:

claude --version

What does the check prove?

This command asks the installed Claude Code application for its version. A version number confirms that PowerShell can find it.

You should see a Claude Code version number in PowerShell.

Linux

Open your application launcher.
Select your terminal application.

Install Claude Code with its native installer by running this command:

curl -fsSL https://claude.ai/install.sh | bash

What does this command do?

This command downloads the official Claude Code installer. The installer adds the Claude Code command to your laptop.

Verify the installation by running this command:

claude --version

What does the check prove?

This command asks the installed Claude Code application for its version. A version number confirms that your terminal can find it.

You should see a Claude Code version number in your terminal.

Good progress. Claude Code now answers from your terminal.

Claude Code not responding?

Close your terminal after the installer finishes. Reopen it before trying the version check again.

Confirm that your account has Pro, Max, Team, Enterprise, or Console access. The free Claude plan does not include Claude Code access.

Help me troubleshoot my Claude Code installation.

Claude Code uses the directory where you start it as its working context. Your first session also opens a browser so you can connect the terminal application to your Claude account.

macOS

Create the cooked video library directory on your Desktop and enter it by running these commands:

cd ~/Desktop
mkdir -p "cooked video library"
cd "cooked video library"
pwd

You should see a path ending with Desktop/cooked video library in the Terminal output.

Windows

Create the cooked video library directory on your Desktop and enter it by running these commands:

Set-Location "$HOME\Desktop"
New-Item -ItemType Directory -Force -Name "cooked video library"
Set-Location "cooked video library"
Get-Location

You should see a path ending with Desktop\cooked video library in the PowerShell output.

Linux

Create the cooked video library directory on your Desktop and enter it by running these commands:

cd ~/Desktop
mkdir -p "cooked video library"
cd "cooked video library"
pwd

You should see a path ending with Desktop/cooked video library in the terminal output.

Start Claude Code inside the cooked video library directory by running this command:

claude

What does this command do?

This command starts an interactive Claude Code session. Your first session opens the browser login flow.

Complete the Claude account login in the browser window.
Return to your terminal after the browser confirms your login.

You should see the Claude Code prompt in your terminal. This confirms that the installation is authenticated.

Browser login not completing?

Keep the original terminal session open while you finish the browser login. Closing that session can interrupt authentication.

Check that you used the same eligible Claude account in the browser. Return to the terminal after the browser confirms access.

Help me complete Claude Code authentication.

Install the plugin and finish local setup

The cooked. plugin gives Claude Code the instructions and tools that run the video editor. Installing it from the NextWork marketplace keeps the editor available in future Claude Code sessions.

Install the released plugin

Choose this route if you want to use cooked. without changing its source code.

Add the cooked. marketplace to Claude Code by entering this command:

/plugin marketplace add nextwork-projects/ai-video-editor-cooked

Install the cooked. plugin from the marketplace by entering this command:

/plugin install ai-editor@nextwork

Select Install for you (user scope) when Claude Code asks where to install the plugin.

What do these commands do?

The first command adds the cooked. marketplace to Claude Code.
The second command installs cooked. Claude Code identifies this plugin as ai-editor@nextwork.

Claude Code should confirm that the marketplace was added. It should also confirm that the plugin was installed.

Keep cooked. up to date

Cooked. is the editor's product name. Claude Code lists it under the technical plugin identifier ai-editor@nextwork. The NextWork marketplace is external to Anthropic, so automatic updates start turned off.

Open the plugin manager by entering this command:

/plugin

Select Marketplaces.
Select nextwork.
Select Enable auto-update.

You should see auto-update enabled for the nextwork marketplace. Claude Code can now refresh cooked. in future sessions.

Refresh the nextwork marketplace to fetch its latest plugin listing by entering this command:

/plugin marketplace update nextwork

Update cooked. to the latest version in that marketplace by entering this command:

/plugin update ai-editor@nextwork

Claude Code should confirm that cooked. was updated. If you already have the newest release, it should confirm that ai-editor@nextwork is at the latest version.

Reload cooked. after an installation or update by entering this command:

/reload-plugins

Fork and customise cooked.

Choose this route if you want to change cooked.'s source code. A fork gives you a GitHub copy that you control.

Choose one marketplace source

Claude Code registers one source for each marketplace name. Use either the released NextWork marketplace or your fork for the nextwork marketplace.

Open the cooked. repository in your browser.
Select Fork at the top of the repository.
Sign in to GitHub if prompted.
Select Create fork.

GitHub creates a copy of cooked. under your account. That copy becomes the source for your custom editor.

Record the username shown in your fork's URL: your GitHub username.

Add your fork as the cooked. marketplace by entering this command:

/plugin marketplace add [[GITHUB_USERNAME="your GitHub username"]]/ai-video-editor-cooked

Install cooked. from your fork by entering this command:

/plugin install ai-editor@nextwork

Claude Code should confirm that your fork was added as the marketplace source. It should also confirm that the plugin was installed.

Load the installed plugin by entering this command:

/reload-plugins

Installing the fork lets Claude Code run cooked. Cloning it puts the source files on your laptop so you can edit them.

Move to your Desktop by running this command:

cd ~/Desktop

Clone your fork to the Desktop by running this command:

git clone https://github.com/[[GITHUB_USERNAME="your GitHub username"]]/ai-video-editor-cooked.git

You should see Git download the repository and create an ai-video-editor-cooked folder on your Desktop.

Open the cloned fork in Claude Code by running these commands:

cd ai-video-editor-cooked
claude

You should see Claude Code open inside your fork. Changes you make in this session apply to your copy of cooked.

Bring in future releases

Your fork follows its own commits. When an upstream release arrives, ask cooked. to merge it into your fork with this prompt:

update the editor

Cooked. creates a backup branch before merging the update. It runs its checks and returns to the backup if they fail.

Start the cooked. workflow by entering this prompt in Claude Code:

edit my video

What does this prompt do?

The plugin recognises this request as the start of the cooked. workflow. Claude Code responds with an option that opens the editor's Home window.

Choose Open the home page when Claude Code presents the option.
Select Set up in the first-run flow.

You'll see setup progress for Python, FFmpeg, Node, a transcription model, and the renderer. The renderer turns the edit plan into the final video file.

The first setup downloads about 1.5 GB. Keep your laptop online while the progress card advances through each dependency.

Choose Yes, and don't ask again when Claude requests permission to run one of cooked.'s own commands.
Copy the command Claude provides if setup requests your laptop password.
Switch to your own terminal if a password-protected command is required.
Paste the provided command into that terminal.
Keep cooked. open until every required setup check finishes.

The setup view should mark Python, FFmpeg, Node, the transcription model, and the renderer as ready. Your laptop now has the complete local editing toolchain.

Setup stopped on one dependency?

Read the active setup row to identify which dependency needs attention. Claude provides a command when it needs help from your own terminal.

Allow each required cooked. command before retrying the unfinished check. Keep the editor open during the retry.

Help me finish cooked. setup.

The Home window keeps your editing work in one place. Its sidebar provides access to videos, styles, folders, active jobs, and Settings.

Confirm that the sidebar includes + New video, Home, Your videos, My styles, and Settings.
Find the current job card in the sidebar.
Use the current step and clock to identify what the job is doing.
Select Settings in the sidebar.
Compare the installed version with the latest version shown in Settings.

How does progress appear?

Finished items turn green. Active work shows a spinner with the current step and a clock.

The sidebar can fold into a narrow icon rail. Your videos, styles, keys, and settings remain stored when the editor closes.

Your Claude Code session now uses the library directory as its working context. Cooked. should store its clips, styles, edits, and renders in that same place.

Return to cooked. and select Settings in the sidebar.
Find the path showing the current library directory.
Use its directory control to select the cooked video library directory on your Desktop.

The library path in Settings should now end with Desktop/cooked video library on macOS or Linux. On Windows, it should end with Desktop\cooked video library.

Add or skip the optional keys

An API key is a private code that lets one application use another service. Keys belong only in cooked. Settings.

Gemini can inspect fonts, colours, and graphics. ElevenLabs can improve the detection of ums and retakes.

These credentials deserve careful handling. Never paste either key into Claude chat or include one in a screenshot.

Choose whether to add or skip Gemini through Google AI Studio.

Skip Gemini

Leave the Gemini key field empty in cooked. Settings.

cooked. uses its Claude-backed fallback for the visual analysis work.

Add Gemini

Open the Google AI Studio setup guide in your browser.
Sign in to Google AI Studio.
Check whether Google AI Studio created a project and key automatically.
Select Create API key if no suitable key is listed.
Copy the new key without sharing it.
Switch back to cooked. Settings.
Paste the key into the Gemini key field.

The saved field should hide the key value. Keep that value out of screenshots and Claude chat.

Choose whether to add or skip ElevenLabs.

Skip ElevenLabs

Leave the ElevenLabs key field empty in cooked. Settings.

cooked. uses its local Whisper transcription fallback.

Add ElevenLabs

Open the ElevenLabs API key guide in your browser.
Sign in to your ElevenLabs account.
Select Developers in the left sidebar.
Select the API Keys tab.

ElevenLabs keys start with restricted access. This lets you limit the key to the one feature cooked. needs.

Create a new key from the API Keys tab.
Enable Speech to Text access.
Leave unrelated features at No access.
Set a credit limit that fits your optional use.
Copy the restricted key without sharing it.
Return to cooked. Settings.
Paste the key into the ElevenLabs key field.

The saved field should hide the key value. The key now has only the access cooked. needs.

Your optional-service choice is now explicit. Each added key stays private in cooked. Settings.

Bookmark the cooked. browser address for quick access later.

Before you run the launcher, what do you expect to see when cooked. reopens?

Reopen cooked. from your terminal by running this command:

nextwork-editor

How can I reopen cooked.?

The nextwork-editor launcher opens cooked. from a regular terminal and starts Claude Code inside the selected library folder. Inside Claude Code, /ai-editor:start opens the same editor from that folder.

The browser should open the cooked. Home window. The setup checks should remain complete.

Check that the Home window still shows access to your videos, styles, jobs, and Settings.

You should see the cooked. Home window with its sidebar ready. This confirms that Claude Code is authenticated and the cooked. plugin is loaded.

That's the setup handled. Next, you'll use your six matching references to measure and save an editing style.

Analyse and Save a Style

Your cooked. setup is ready. Next, you will turn your six reference videos into a measured editing style.

Six matching references give cooked. one clear format to measure. A mixed set would blur the result.

In this step, get ready to:

Confirm that the six references share one editing format.
Analyse the six links as a measured style.
Inspect the saved style across its five settings areas.

Choose one consistent reference set

Your references can come from different creators. Their editing format must stay consistent.

Return to the six reference links from Step 0.
Play each reference from start to finish.
Compare the caption treatment across all six videos.
Compare how cards appear across all six videos.
Compare the pace across all six videos.
Compare how often zooms appear across all six videos.
Replace any video that follows a different format.
Confirm every link opens an individual short video.

You should now be able to describe one repeated choice in each area: captions, pacing, cards, and zooms.

Analyse the reference set

Style analysis turns patterns in the six videos into settings that cooked. can reuse. The saved result gives your first edit a measurable starting point.

Select My styles in the cooked. sidebar.
Select + New style.
Select Analyse a format.
Paste the six reference links into the analysis form.
Confirm each link appears in the form.

Before you start the analysis, which repeated choice do you expect cooked. to measure most clearly?

Select Analyse this format.

This analysis can take a few minutes while cooked. processes all six videos. The progress screen confirms that the work is still moving.

Keep the cooked. browser tab active while the analysis runs.
Watch the progress view until the resulting style card appears.

What is cooked. measuring?

Transcription reveals the spoken pace across the references.
Cut measurements reveal how quickly the format moves.
Zoom measurements reveal how often the framing changes.
Caption and card measurements reveal the repeated visual treatment.

Good progress. Your six examples now exist as one measured style card.

Style card not appearing?

Confirm that each reference link opens without requiring private access.
Confirm that every link points to an individual video.
Replace any unavailable link with another video that follows the same format.

Help me troubleshoot a cooked. style analysis that is not producing a style card.

Rename and inspect the style

A saved style is a reusable set of measured editing choices. Its source links show which examples shaped those choices.

Select the resulting style card in My styles.
Compare its source links with your six selected references.
Use the style name control to rename it to your recognizable style name.
Pause until the new name appears on the style card.

What should you inspect?

Captions control the repeated text treatment.
Zooms control how often the framing changes.
Cut controls the pacing of the edit.
Cards control the supporting visual inserts.
Sound controls the repeated audio treatment.

Inspect Captions for the repeated text treatment.
Inspect Zooms for the measured framing changes.
Inspect Cut for the measured pacing.
Inspect Cards for the supporting visual pattern.
Inspect Sound for the measured audio treatment.
Compare the full settings set with your one-sentence editing target.
Correct any available setting that conflicts with your target.

Your corrections save as you make them. The style page should now reflect the format you intended to capture.

Style does not resemble the references?

Correct an isolated mismatch on the relevant settings area.
Replace a reference that uses a different caption treatment or pace.
Analyse the tighter set again when several measured choices feel inconsistent.

Help me identify why my cooked. style does not resemble its reference videos.

Before you return to My styles, what should the card and style page now prove?

Return to My styles in the cooked. sidebar.
Find the card named your recognizable style name.
Select the renamed style card.
Confirm that its six source links remain attached.
Check that its Captions, Zooms, Cut, Cards, and Sound settings reflect your review.

You will see the recognizable name on the style card. Its page retains the source links and measured settings.

Strong work. Your first video now has a measured style to follow.

Your source clip and one-sentence target are still ready. Next, you will use this saved style to make the first cut.

Make the First Cut and Correct It

Your named cooked. style now captures the repeated choices from your six matching references.

Now you need a spoken-content cut worth styling. The first cut is a proposal that can keep a retake or remove a useful phrase.

You will hear the cut before using transcript editing to change it. You will send human feedback before approving the spoken content.

In this step, get ready to:

Create a new video project from your selected source clip using your saved style.
Correct the first cut through transcript changes.
Approve the rebuilt cut after a timestamped feedback round.

Start the video project

A video project combines your source clip with the measured style you saved earlier. Its orientation should match both the source recording and your target format.

Select + New video in the cooked. sidebar.
Drop your selected MP4 or MOV clip into the upload area.
Select Tall or Wide to match your source clip.
Paste your script into the script input if you have one.
Choose the recognizable saved style you created from the six references.

Your first video may ask a few preference questions before processing. Those answers can become defaults for later videos.

Answer any preference questions based on your one-sentence editing target.
Start the project by selecting Make my video.

You will see the video card and sidebar job card report the current processing stage. The first video has several stages, so ongoing progress confirms cooked. is still working.

Before you play the first result, what do you expect cooked. to have completed?

Play the first cut when its review page is ready.

You will see the message This is the cut. Captions, zooms and sound come next, once you approve it. This confirms the current round focuses on the spoken content.

Why Review the Cut First?

A clean cut isolates the spoken words and pauses. Correcting the timing now keeps later visual choices attached to approved speech.

Correct the transcript-led cut

The transcript turns individual words into edit controls. Playback highlights the current words while the video plays.

How to Read the Transcript

Highlighted words show the current playback position.
Struck words are removed from the cut.
Suggested cuts can show Filler, Retake, False start, or Pause as the reason.

Play the video while following the highlighted words in the transcript.
Keep a suggested cut by selecting its tick.
Bring a suggested cut back by selecting its cross.
Select the exact words you want to change.

The selected words reveal Restore, Copy, and Cut controls.

Change at least one word selection by choosing Restore or Cut.
Cut selected words with Backspace or Delete if you prefer the keyboard.
Reverse an unwanted transcript change by pressing Cmd+Z (macOS) or Ctrl+Z (Windows).
Hear your pending transcript changes by selecting Preview.

You will hear the pending version with your word-level change included. This gives you a quick check before rebuilding the cut.

Save the transcript changes by selecting Apply.

You will see cooked. rebuild the cut using your updated transcript. The refreshed playback retains the words you restored or removes the words you cut.

Transcript Change Missing?

Check that the intended words are selected before using Cut or Restore. Select Apply after previewing so cooked. rebuilds the saved cut.

If playback still uses the previous version, wait for the rebuild shown on the sidebar job card to finish.

Help me troubleshoot my transcript change.

Approve the cut after feedback

A timestamped note ties one request to the exact moment where the problem occurs. A specific note gives the next cut round a clear change to make.

Pause playback at the exact moment that needs a correction.
Enter a specific note such as keep this sentence.
Start another cut round by selecting Send notes.

Rebuilding can take some time because cooked. creates another cut round from your note. The sidebar job card keeps the current stage visible.

Wait for the next round by watching the current step on the sidebar job card.

Before you replay the marked moment, do you expect the rebuilt cut to reflect your note?

Replay the changed section in the next cut round.

You should hear the rebuilt version at the marked moment. Compare it with your note to confirm the requested speech or pacing change landed.

Note Did Not Land?

Pause at the same moment again if the rebuilt cut missed your request. Use a concrete note that names the words to keep or remove.

Send the clearer note as another round before approving the cut.

Help me improve my cut-review note.

Approval locks the spoken words and pacing for the next review stage. Use it only after the rebuilt cut sounds right from start to finish.

Before you approve this cut, which review stage do you expect to open next?

Approve the spoken content by selecting Approve the cut and add captions.

You will see the review move from The cut to The edit. Your transcript changes and cut-review feedback are now retained in the cooked. library.

That is the core edit locked in. Your approved speech and pacing can now support the styled review.

Your spoken-content cut is approved. Next, you will inspect the styled render and send a realistic round of visual feedback.

Review, Revise, and Download the Styled Edit

Your spoken-content cut is approved. cooked. can now apply your saved style to the video.

A stills sheet can reveal layout problems. Full playback reveals caption timing, zoom movement, card accuracy, music balance, and other issues that only appear over time.

In this step, get ready to:

Reach a laptop-rendered first styled round after checking the stills.
Turn several timestamped notes into visible fixes.
Finish with an approved video downloaded to your laptop.

Approve the stills and render on your laptop

A render is the finished video file produced from your approved cut and style plan. The stills sheet gives you a final chance to catch visual problems before your laptop builds that file.

Review the stills sheet created from your styled edit.
Check the readability of every caption shown in the frames.
Check each card against the content it represents.
Check every logo or page capture for accuracy.
Check that important visuals sit inside the safe viewing area.
Request a visual correction for any still that looks wrong.
Approve the stills sheet once every frame is ready.
Compare the time and cost information cooked. shows for each render choice.

Choose your laptop as the render location.

Why render on your laptop?

Your laptop keeps this project's render free. For a short video, it is often the fastest choice.

Cloud rendering adds account and cost decisions. Local rendering keeps this first review focused on the edit.

Keep cooked. open while the laptop render runs.

Expect rendering to follow the estimate cooked. showed for your clip. The live progress state confirms that your laptop is still working.

You have moved from a clean spoken cut to a watchable styled video. The first styled round is ready for its timing test.

Send a realistic feedback round

Static frames cannot prove how an edit feels in motion. Full playback exposes timing problems in captions, cards, zooms, transitions, and sound.

Before you press play, consider which problem the stills sheet was most likely to have missed.

Watch the full first render from beginning to end.

The first playback exposes motion or sound issues that the stills could not show. That shortfall is the reason this review round exists.

What makes a useful note?

Useful feedback names one visible or audible change. These examples give cooked. a clear target at a specific moment.

captions too small.
move these captions higher.
this card is wrong, show the real page here.
fewer zooms after this point.
music is too loud under my voice.

Timestamped feedback can feel fiddly because every note needs to land where the problem is visible or audible.

Pause playback at each moment that needs a change.
Enter one specific note for the paused moment.
Repeat until the round contains several timestamped notes.
Select Send notes.

cooked. rebuilds the styled edit from your feedback. The next round shows resolved notes in green alongside Claude's replies.

Review each note marked as resolved in green.
Read Claude's reply for each resolved note.
Replay every changed moment.
Check the revised captions at the moments you flagged.
Check the revised cards at the moments you flagged.
Check the zoom frequency after the moment you flagged.
Listen to the voice and music balance at the moment you flagged.

You should see the requested fixes in the video. The notes panel should show the corresponding items as resolved in green.

A fix still misses your note?

Return the playhead to the exact moment where the issue remains.
Leave a new note that names the visible or audible problem.
Select Send notes to create another review round.

Avoid broad requests such as make it better.

Help me rewrite a video editing note so cooked. can act on it.

Approve and download the finished video

A final full playback protects you from approving a fix that caused a new problem elsewhere. Every resolved moment needs to hold up as part of the complete video.

Before the final playback, consider whether every requested change will remain correct from beginning to end.

Play the revised video from beginning to end.

You should see each resolved change remain in place throughout the full video. The captions, cards, zooms, transitions, and sound should support the approved spoken cut.

Approve the revised video after the full playback works.
Select Your videos in the cooked. sidebar.
Open the finished video's menu.
Select Download.

The final approval turns green. Your browser downloads the finished video while the complete project remains in the cooked. library.

Before you open the downloaded file, consider what should match the approved round in cooked.

Open the downloaded video file from your browser's downloads list.

You should see the approved final video play outside cooked. The original clip, transcript cut, review rounds, notes, and approved render remain available under Your videos.

Can't find the downloaded video?

Confirm that the final approval is green. Return to Your videos to check that the finished project is still listed.

Open your browser's downloads list to locate the downloaded copy.

Help me find my downloaded cooked. video.

That's the full review loop complete. Your downloaded video reflects decisions you tested across two styled rounds.

Secret mission

Teach the Saved Style

Your approved video contains feedback that can improve more than one edit. In this optional mission, you will turn the useful patterns from that feedback into reusable rules for future videos.

Clean Up Your Resources

Laptop rendering is free. Choose whether to keep your resources available, pause the open apps, or remove this video's library project plus temporary data.

Resources you used:

Temporary render data generated while producing and revising the styled video.
The cooked. talking-head video project in Your videos, including its original clip, transcript cut, review rounds, notes, and approved render.
The cooked-video-library folder on your Desktop, which stores your videos, styles, and edit history.

Keep everything running

Leave the current setup untouched if you plan to edit again soon. Keeping the local library does not add a laptop rendering charge.

Keep the cooked. browser tab open.
Keep Claude Code running in its terminal window.
Leave the approved video project in Your videos.
Leave the taught style in My styles for your next edit.

Pause - I'll come back to this later

Closing the active local windows frees memory while preserving every project item. Your video history and taught style remain ready for later.

Close the cooked. browser tab.
Close the terminal window running Claude Code.
Start a new terminal session when you are ready to return.
Reopen cooked. by running nextwork-editor.

Delete - I don't want to use this again

Use this option when you want the video project out of the active cooked. library. The first cleanup control preserves the work you approved.

Switch back to the cooked. browser window from earlier.
Select Settings in the sidebar.
Select Clear working files.

What Does Clear Working Files Remove?

Clear working files removes temporary render data. It keeps the source clip, transcript cut, approved final video, and notes inside the project.

Select Your videos in the sidebar.
Open the menu for the approved talking-head video.
Select Move to Trash.
Open Trash in cooked.

Nicely handled. Your temporary render data is cleared.

The video project now sits in Trash. The downloaded final video stays where you saved it.

Before you delete the library

Deleting the library removes every remaining local video, style, and edit inside it. Only continue when you no longer need those files.

macOS

Delete the cooked-video-library folder and everything inside it by running this command:

rm -rf ~/Desktop/cooked-video-library

You should no longer see cooked-video-library on your Desktop.

Windows

Delete the cooked-video-library folder and everything inside it by running this command:

cmd /c rmdir /s /q "%USERPROFILE%\Desktop\cooked-video-library"

You should no longer see cooked-video-library on your Desktop.

Linux

Delete the cooked-video-library folder and everything inside it by running this command:

rm -rf ~/Desktop/cooked-video-library

You should no longer see cooked-video-library on your Desktop.

Folder still visible?

Close cooked. and any Claude Code terminal using the library before trying again. Help me remove the Desktop library safely.

Nice Work!

You did it! Your phone clip is now an approved talking-head video shaped through your decisions in cooked.

You've learned how to:

Used style analysis to create a named editing style from six matching reference videos.
Used transcript editing to reshape the spoken-content cut at word level. Tested a timestamped note against a rebuilt round before approving the speech.
Turned several timestamped notes into visible fixes in the next render. Approved the result after a full playback. Downloaded the finished video.
Secret Mission: Taught the saved style to carry reusable feedback rules into future edits. Excluded one-off corrections.

Ready to quiz yourself?