CutWright

Work with an agent

Connect the project in your browser to Codex, Claude, or a compatible WebMCP agent. Keep using your agent’s own conversation, review its edits here, and disconnect whenever you want.

Before you connect

  1. Open the intended project and import the media the agent will need. See Import & manage media.
  2. Save your current work with Save or Ctrl + S. Keep your original media files.
  3. Open your agent app on the same computer. You use its own account and conversation. CutWright does not ask for a separate AI API key.
  4. Keep the editor tab open while connected. The agent works with the project currently open in that tab.

The Codex and Claude browser connections do not require the CutWright Windows app. You install their small connector once. You can edit and export without connecting any agent.

Open the connection settings

  1. Click Agent, the chain-link button at the bottom of the left navigation rail. The default shortcut is Ctrl + /; you can change it in Keyboard shortcuts.
  2. In the browser, choose Codex, Claude, or WebMCP. Only the selected method’s instructions appear.
  3. Expand Setup instructions when you need help. Full guide opens these detailed instructions. Recent actions stays collapsed until you open it.

Choosing another connection method disconnects the current one. Closing the dialog with its close icon keeps the current connection active and returns you to editing.

On a first connection, keep the browser in front and answer its local network permission prompt if one appears. CutWright allows up to 20 seconds for discovery. If you missed the prompt, allow access for app.cutwright.cc in the browser’s site settings, then click Connect again.

Connect the browser editor to Codex

One-time setup

  1. Open Agent → Codex, then click Set up Codex or expand Setup instructions.
  2. If Node.js 22 or newer is not installed, follow the Node.js 22 or newer link and install it. Reopen PowerShell or Terminal afterward.
  3. Click download the CutWright connector. Save it in your computer’s Downloads folder. Keep the filename shown in the dialog.
  4. Click the small copy icon on the right of the command. Open PowerShell on Windows, or Terminal on macOS or Linux. Paste the copied command and press Enter. If your browser saved the file elsewhere or added a suffix to its name, adjust the path in the command to that exact file.
  5. Wait for the message saying CutWright was added to Codex. The setup keeps the connector in a permanent location, so moving the original download later does not remove the connection. It adds a server named cutwright-browser and preserves other Codex settings.
  6. Restart Codex, then open a new conversation. Check that cutwright-browser is enabled in Codex’s Settings → MCP servers.
  7. Return to the browser editor and click Connect. If your browser asks to find or connect to devices on the local network, allow it for CutWright.
  8. Wait for Connected to Codex. Close the dialog and ask Codex to inspect the current CutWright project.

If setup reports a configuration conflict, do not overwrite unrelated settings. Open Codex’s MCP settings, remove or rename the conflicting cutwright-browser entry, then run the displayed setup command again. If the command cannot find Node, install Node.js and reopen the terminal. The dialog always shows the command for its current release.

Later connections

  1. Open Codex with the connector enabled and open the intended project in browser CutWright.
  2. Open Agent → Codex and click Connect.
  3. Keep the tab open and continue in Codex’s own conversation. Approve tool requests in Codex when it asks.

Connect the browser editor to Claude

One-time setup

  1. Open Agent → Claude, then click Set up Claude or expand Setup instructions.
  2. Click Download the CutWright extension. Save the .mcpb file.
  3. In Claude Desktop, open Settings → Extensions → Advanced settings, choose Install Extension, and select that file. Follow Claude’s installation prompts and enable CutWright. Claude supplies the runtime; you do not need to install Node.js separately for this extension.
  4. Restart Claude if it asks, then open a conversation with the CutWright extension enabled.
  5. Return to Agent → Claude in the browser editor and click Connect. Allow CutWright’s local network access if your browser asks.
  6. Wait for Connected to Claude. Close the dialog and ask Claude to inspect the current CutWright project.

If your organization disables custom desktop extensions, ask its administrator to enable the CutWright extension. The website cannot override that setting.

Later connections

  1. Open Claude with CutWright enabled and open your browser project.
  2. Open Agent → Claude and click Connect.
  3. Keep this tab open and ask for edits in Claude’s conversation. Its tool approval controls still apply.

If several agent sessions appear

Several conversations can each start a connector. CutWright does not guess which one you intend to use.

  1. Ask the intended agent which CutWright session code it is using. If it tries to read the project before connecting, its connection message includes the code.
  2. In CutWright’s Agent connection dialog, choose that code in Agent session, then click Connect.
  3. A session marked (another tab) is already in use. Disconnect it in that other tab first, or choose a different agent session. Connecting never silently takes over another tab.

Connect through WebMCP

  1. Open the project in a WebMCP-compatible agent browser or a browser with a compatible agent integration.
  2. Open Agent → WebMCP. If available, the status says WebMCP available.
  3. Click Enable WebMCP. Wait for WebMCP enabled, then close the dialog and keep the tab open.
  4. Use that browser agent’s own chat to ask it to inspect the CutWright project, then request your edit. Approve tool use in that agent when requested.

WebMCP enabled means the project’s tools are available to a compatible browser agent. It does not mean Codex or Claude Desktop has automatically attached. To use those desktop apps, choose their tabs in the connection dialog.

If your browser requires a WebMCP testing option, follow its vendor’s setup instructions and restart it before enabling the connection again. Enabling a browser flag alone does not add an agent conversation. In Edge testing builds, the option is named WebMCP for testing under edge://flags/#enable-webmcp-testing. Availability varies by browser and version.

WebMCP unavailable in this browser disables this method’s enable button. Use a compatible agent browser, choose Codex or Claude instead, or continue editing by hand. Editing and export remain available.

Connect in the CutWright Windows app

  1. Open Agent and click Enable connection.
  2. Wait for Local MCP enabled. The MCP configuration appears.
  3. Use its small copy icon to copy the configuration. If copying is unavailable, select its text and copy it manually.
  4. Add the displayed command, arguments, and environment to your agent’s local MCP settings. In Codex, use Settings → MCP servers → Add server and choose STDIO. In Claude, use its local MCP configuration settings. Restart the agent if requested.
  5. Keep the Windows editor open and ask the agent to inspect its project. You do not need the separate browser connector for this Windows-app connection.

After restarting CutWright, enable the connection again. Reuse the same configuration for the same editor profile. A different profile has different connection settings.

Ask for a clear edit

  1. Ask the agent to inspect the current project before changing anything.
  2. Identify clips by displayed name, time, or track. Describe the result: “Add a marker at 12 seconds named First reveal,” “Make the selected title say A little story,” or “Lower the music under the opening dialogue.”
  3. Let the agent finish, then play through the affected section and check the picture, timing, and sound.
  4. Save when you are happy with the result. Use Undo or ask for a specific correction if necessary.

Import local media yourself before asking the agent to arrange it. A connection does not add editing features the editor lacks. The conversation and its model requests stay in your chosen agent app and follow that provider’s terms.

Review and undo agent actions

  1. Open Agent, then expand Recent actions. The newest action is first, with a time and description. Unsuccessful actions are marked as rejected.
  2. Close the dialog and inspect the affected edit.
  3. Click Undo above the timeline or use the default Ctrl + Z shortcut. One agent action can contain several related edits, undone together.
  4. Click Redo or use the default Ctrl + Shift + Z to restore it.

Undo changes the project. It does not delete a finished video already downloaded or saved. See Export your finished video for progress and cancellation.

Disconnect when you are done

  1. Open Agent and click Disconnect.
  2. Check that the enabled or connected status disappears. In the Windows app the configuration disappears too.
  3. Continue editing or save and close the project. Your existing edits remain. Use Undo to reverse an edit.

Closing or reloading the editor tab ends its access; it does not automatically reconnect on your next visit. Closing the popup alone keeps the connection. If a browser suspends the tab or the agent closes, reconnect before asking for more edits.

If the connection does not work

Connector not found.
Complete the selected agent’s setup, restart that app and open a conversation with CutWright enabled, then try Connect again. Both apps must run on the same computer. If local network permission was denied, allow it for app.cutwright.cc in the browser’s site settings. Some browsers or managed devices block this access; WebMCP is a separate alternative.
The agent is still disconnected after the website says it connected.
Check the agent session code. With several conversations open, select the code reported by the intended conversation and reconnect. A newly added Codex connector may require a new conversation or app restart.
The wrong project is open.
Stop the agent’s request. Open the intended project in the connected tab, ask the agent to inspect it again, then identify the clips clearly before requesting changes.
An edit is rejected after a manual change.
Ask the agent to read the current project again before retrying. Do not repeat an older change blindly.
Nothing appears under Recent actions.
Connecting alone does not make edits. Ask the agent to inspect and edit the project from its own conversation, then expand the list.
A connector update is needed.
Download the current connector from Setup instructions. For Codex, run its displayed setup command again and restart Codex. For Claude, install the current extension package and restart if requested.