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 Plugin In messages to the user, call the app just ChatCut, in their language, for example "安装 ChatCut". Names such as ChatCut Desktop, CLI commands or MCP are for you; keep them out of what you tell the user. ## 1. Check the execution environment 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 The npm commands below require Node.js 22+. If it is available, choose the install or update branch based on whether ChatCut Desktop is installed. If Node.js/npm is unavailable, or the npm install/update cannot complete, use the official installer fallback below. Do not install Node.js just to install ChatCut Desktop. These commands check the app's signature and whether ChatCut is running, which an agent sandbox blocks: inside the Codex sandbox on macOS they fail with `gatekeeper_assessment_failed` or a process-list error even though the app is fine. Run them outside the sandbox from the start, requesting escalated permissions where the agent needs the user's approval. ### If ChatCut Desktop is not installed Install the latest public release and open it: ```sh npx --yes --prefer-online @chatcut/cli@latest app --json ``` ### If ChatCut Desktop is already installed Save ongoing work and quit ChatCut normally if it is running. Update the Desktop app to the latest public release: ```sh npx --yes --prefer-online @chatcut/cli@latest update --json ``` Confirm that the command succeeds with `updated` or `up_to_date`, then open ChatCut: ```sh npx --yes --prefer-online @chatcut/cli@latest app --json ``` An update failure does not mean the app is current. If a system-wide Windows installation returns `app_updater_required`, follow the returned updater or official installer instructions. ### Fallback: install without npm If Node.js 22+ or npm is unavailable, or the npm install/update fails, download the current official installer for the user's platform: - [macOS Apple Silicon](https://api.chatcut.io/desktop/download/macos) - [macOS Intel](https://api.chatcut.io/desktop/download/macos-x64) - [Windows x64](https://api.chatcut.io/desktop/download/windows) 1. If updating an existing installation, ask the user to save their work and quit ChatCut normally first. Keep their projects, settings and account data. 2. On macOS, open the downloaded disk image and drag **ChatCut** to **Applications**, confirming replacement when updating. On Windows, run the downloaded installer and complete its prompts. Handle any required operating-system confirmation with the user. 3. Launch the installed **ChatCut** app from **Applications** on macOS or the **Start menu** on Windows. Confirm that its actual app window opens, then continue with step 3 below. Downloading the installer alone does not complete setup. ## 3. Verify the app and sign in For both the npm and official installer flows, 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. Using the official installer leads to the same sign-in and agent-connection steps below. 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. ### For Codex or Claude Code with Node.js 22+ Run the matching command to register or repair this host's connection and synchronize the core Skills shipped with the installed Desktop version: ```sh # Local Codex: npx --yes --prefer-online @chatcut/cli@latest connect --client codex --json # Local Claude Code: npx --yes --prefer-online @chatcut/cli@latest connect --client claude-code --json ``` The connect command opens Desktop, asks it to configure the selected integration and sync its managed Skills, then verifies the connection with a separate MCP client that lists tools and calls `get_active_project`. Tools are provided through MCP; Skills are synchronized into the host's Skill directories. Check the selected integration's status, Skill checks and MCP read result in the JSON. An opted-out or unavailable integration can be informational even when `ok` is true; report that state and the remaining action. If a check or repair fails, report its original error. Connect does not check for newer Desktop releases; installation and updating are handled in step 2. ### Fallback: connect without npm If npm is unavailable or the npm connection command fails, 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 this agent, and click **Connect**, **Reconnect**, or **Retry** as shown. Desktop manages the MCP registration and bundled Skills. Respect an explicitly disabled integration. For another supported MCP host, use **Connect any agent** and its setup prompt. If native setup still needs manual repair, check whether this host already has the correct `chatcut_desktop` registration. Use its documented configuration command or file to register a STDIO MCP server with the launcher supplied by Desktop. The standard production launcher is `~/Library/Application Support/ChatCut/chatcut-mcp` on macOS or `%APPDATA%\ChatCut\chatcut-mcp.cmd` on Windows. Resolve the actual user's path and confirm the launcher exists; prefer `desktop.launcherPath` when an earlier command returned it. Do not guess another installation's path or replace unrelated MCP configuration. Use the host's supported Skill installation flow for any required Skills. Then continue with step 5 to check access in the current conversation and handle any host reload it requires. A successful diagnostic client does not establish that this conversation has loaded the tools or Skills. ## 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, arrange how to continue 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. When setup is complete but the host has not loaded the tools or required Skills, use its diagnostics or current documentation to choose the action appropriate for that host and version: - **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:** If the host requires a new conversation or cannot resume the existing one, prepare the continuation prompt described below now. 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. 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. ```