ChatCut Desktop install guide

This plain text version is returned because this request does not look like a browser page navigation.
Browser page: https://chatcut.io/desktop

Full installation guide:

# Install ChatCut Desktop

## 1. Choose where to install

Continue in the agent that received this request. Identify the computer where this agent can run commands and ChatCut Desktop will run. This can be the user's computer or a connected cloud computer with a graphical desktop. Run setup on that same computer. If this session cannot execute commands there, explain how to continue in a supported execution environment, keeping the original request.

This guide currently supports macOS 13+ on Apple Silicon or Intel, and Windows x64. **Linux setup is not supported yet.** If the target computer runs Linux, explain this limitation and do not run the installation steps below.

## 2. Install or update, then open Desktop

Use the official installer command for this computer. It downloads the current release, verifies the publisher, installs or updates ChatCut, and opens the app. No Node.js or npm is required.

If updating, have the user save their work and quit ChatCut normally first. Keep their projects, settings and account data. Do not force-quit the app.

### macOS — run in Terminal

Supports macOS 13 or newer on Apple Silicon and Intel:

```sh
curl -fsSL https://chatcut.io/install.sh | sh
```

### Windows — run in PowerShell

Supports Windows 10 or newer on x64:

```powershell
irm https://chatcut.io/install.ps1 | iex
```

Run the matching command on the same computer as Desktop. The installers need access to the operating system's process list and signature checks. In an agent sandbox, use the host's supported permission flow to run outside that sandbox. Do not run as root or add sudo. Do not disable security checks to work around an error.

Wait for the command to finish successfully and confirm that ChatCut opens. If it reports an error, preserve the existing installation and report the actual error and required action. A failed install or update is not success.

## 3. Verify the app and sign in

Keep the operating system's signature and trust checks enabled:

- **macOS:** Keep Gatekeeper enabled. The app bundle identifier is `io.chatcut.desktop`, signed by ChatCut Inc. with Apple Team ID `7WK2VURFPK`.
- **Windows:** The app must have a valid Authenticode signature for ChatCut Inc.

Do not bypass OS trust failures. If installation or updating fails, report the actual error and remaining action.

Confirm that the actual ChatCut app window has opened before starting sign-in.

Check whether the user is already signed in to ChatCut Desktop. If so, continue with their existing account and projects.

### Sign in through your browser

**Use this only after ChatCut Desktop is installed and its app window is open. Keep Desktop running throughout sign-in.** This link does not install Desktop or replace the steps above.

If Desktop is not signed in:

1. Open [Sign in and open ChatCut Desktop](https://app.chatcut.io/authenticate?openDesktop=1) for the user on the same computer. Let them sign in with Google or email. An existing ChatCut browser session uses that account, so make sure it is the account they want in Desktop.
2. Allow the browser to open ChatCut Desktop when prompted. If the handoff does not start automatically, click **Retry** in the browser's **Open ChatCut Desktop** message. If Desktop has been closed, open it first and retry.
3. Return to the Desktop app and verify that it is signed in before continuing to agent connection setup. Opening the browser page alone does not confirm Desktop sign-in. If the browser handoff cannot complete, use the app's normal sign-in instead.

Never copy credentials from another profile or create a project just to test installation.

### If the user's request needs a paid feature

After sign-in, check the requested feature's current access and the account's membership. Use `chatcut_desktop.read_billing` when available, or inspect the signed-in account in Desktop. An unknown or failed billing read is not evidence that the user is on Free. Do not require a subscription for work the account can already do.

If the requested feature requires membership and the signed-in user is not a member, open `chatcut://billing` using this computer's URL-opening capability to show the Desktop billing popup. Prefer a more specific Desktop billing link if a tool returned one. The same popup is at **profile/account row at the bottom-left of the Desktop sidebar → Upgrade**. Use that UI path if the link cannot open; if this agent cannot operate the app, give those exact two clicks. Do not send them to the web editor's top-right avatar menu.

Explain which requested feature needs membership and let the user choose a plan and complete payment. Opening billing is not permission to purchase. After payment, recheck feature access before resuming the original request, preserving its media and instructions. If the user is already a member but lacks credits, open **Credits** in the same user menu (**Plan & credits** in Settings) and use its available credit-purchase options instead of asking them to subscribe again.

## 4. Connect this agent to Desktop

Connect the agent that received this request to the local STDIO MCP server named `chatcut_desktop` on the same computer. Preserve existing configuration and user-modified Skills, and respect an explicitly disabled integration.

Keep Desktop open and use its native integration controls. Click the agent icon at the top of the Desktop sidebar (**Agents on this computer**), find the agent that received this request, and click **Connect**, **Reconnect**, or **Retry** as shown. Desktop manages the MCP registration and bundled Skills. For another supported MCP host, use **Connect any agent** and its setup prompt.

If setup fails, report the integration's actual status and error. Preserve existing configuration and user-modified Skills; respect an explicitly disabled integration. Do not install a separate package or replace unrelated MCP configuration to repair it.

After connection setup, verify access in step 5 and continue in this conversation.



## 5. Continue in your agent and start creating

Guiding the user into creation is a required part of this installation flow. Complete the guidance below so they can continue their task or start creating with ChatCut. Stopping at installation success can interrupt the user's workflow.

### Check whether this conversation can use ChatCut

After connection changes, inspect the current conversation's actual tool and Skill catalogs. Tools and Skills can become available separately. Judge readiness from these catalogs and real tool-call results; diagnostic output alone does not establish whether this conversation can continue.

When the tools are available, verify access:

1. Perform an actual read with the local `chatcut_desktop` tools, using `get_active_project` or `list_projects`. An empty project selection or list is valid; a connection error or cached tool list is not a successful read.
2. When the workflow requires a Skill, confirm that this agent discovers it and load it through the agent's native Skill mechanism. If it still needs installation, follow its guide first. If this agent lacks the required Skill capability, explain the limitation and remaining step.

### If access is not ready, finish setup and refresh the connection

Identify what is missing. Complete unfinished installation, sign-in or connection setup, and diagnose any connection error returned by an exposed tool. Explain the specific remaining action and retain the setup already completed.

After completing installation, app launch, sign-in and connection, recheck the current tool and Skill catalogs. If the tools are available, continue the user's task here. If they are still missing, use the host's diagnostics or current documentation and try a supported connection refresh before falling back to another conversation:

- **Refresh the connection:** Use the host's supported refresh when available, then check access again.
- **Restart the host app and resume this conversation:** If the host requires a restart and can retain this conversation, ask the user to quit and reopen the host app, return to this conversation and tell you when it is ready. Preserve ongoing work and the task context.
- **Continue in a new conversation only as a fallback:** If setup is complete but the host still cannot load the required tools in this conversation or cannot resume it after a required restart, prepare the continuation prompt described below. Use supported conversation-creation and navigation tools when permitted; otherwise, give the user the prompt to copy and concrete instructions, including any required app restart. Do not assume a new conversation is required before checking actual tool availability.

After the required action, recheck the actual tool and Skill catalogs and verify access in the conversation that will continue. If it is still unavailable, explain the remaining blocker and next action based on the evidence.

### Carry the user's task forward

Choose the content below based on the user's request. If this conversation has verified access, act on it directly. If a new conversation is required, put it into a self-contained, ready-to-copy prompt now, in the user's voice and language. Include the verified setup, supplied media, selected workflow, project/workspace context and any remaining setup steps so the next agent can verify access and continue. Present the complete prompt in one fenced `text` code block so hosts with copy controls can offer one-click copying. Keep explanations outside the block. If code blocks are unsupported, use one clearly separated plain-text prompt.

**If the user already has a clear request,** continue it and ask only for information still missing. For a new conversation, carry that same request and the answers already provided into the prompt.

**If the user has no creative request yet,** use the creation brief below. Once ChatCut is available, follow it in the current conversation. If a new conversation is needed, give the user the complete brief as a single copyable prompt. Translate it into the user's language and adjust the opening to the verified installation and sign-in state. Tailor the capabilities to the tools and Skills available. Preserve the numbered three-part structure and the instructions that follow it. Deliver the full prompt rather than a shortened summary.

```text
ChatCut Desktop is installed and signed in on this computer. Please confirm that you can use ChatCut, then help me start creating.

Introduce how you can help me in these three areas:
1. Video editing.
2. Motion graphics creation.
3. Asset generation: images, videos, voiceovers, music and sound effects.

Ask what materials I have and what kind of video I want to make, then guide me step by step based on my answers. Also let me know that I can open ChatCut Desktop at any time to adjust the timeline, captions and motion graphics myself.
```