ChatCut plugin for ChatGPT install guide This plain text version is returned because this request does not look like a browser page navigation. Browser page: https://pr-624-preview.chatcut.dev/chatgpt Full installation guide: ## Start by checking the existing connection Help the user connect ChatCut and begin their chosen creation task. Keep their existing plugins, project, media references, and creative brief. Do not reinstall a working connection or start a new conversation by default. First inspect the current host's available ChatCut skills and tools. Read the installed ChatCut entry skill before using its tools. Distinguish these sources by their actual manifest, version, and tool availability: - **Official ChatGPT directory:** [open ChatCut](https://chatgpt.com/plugins/plugins_6a8c039995c08191932d494269209307?open_in_app). Opening this page is an installation entry, not proof of installation, account authorization, or working tools. A skills-only package does not itself provide an MCP connection. - **Git marketplace, Hosted Web route:** `chatcut@chatcut-inc` from `https://github.com/ChatCut-Inc/agent-plugin.git`, ref `main`. This is a separate distribution source; adding it is not an automatic upgrade of the official-directory package. - **ChatCut Desktop route:** the local ChatCut application supplies its connection and editing skills. Follow [the Desktop guide](https://pr-624-preview.chatcut.dev/desktop-plugin) for this route. Names alone do not identify a package. In particular, a directory package called `chatcut-desktop` is not proof that the local Desktop application is connected. Do not remove, replace, or disable an existing directory plugin to make room for another source. Do not install internal Preview plugins. If the current conversation already has a working ChatCut connection, keep it and go to **Choose a creation task**. If the user has not chosen between Web and Desktop, explain the two routes briefly and ask which they want. Never silently send a Web user to the Desktop installer. ## Host environment gate A browser-only or isolated remote agent cannot change the user's local Codex installation. It may use an existing hosted connection exposed by its host. If none is available, provide the official directory link and describe the missing connection. Do not run local installation commands in a remote workspace and claim they installed a plugin on the user's computer. For the Git marketplace route below, confirm that this agent is running on the user's computer in the Codex desktop app and that the user chose this installation source. Locate the CLI bundled with that desktop app; use its full quoted path as `""`. Do not assume a standalone `codex` found in `PATH` is the desktop app's CLI. If the host or selected route is unclear, ask that one question before changing installation state. ## Install or update the Hosted Web connection Check the bundled CLI and existing configuration first: ```text "" --version "" plugin marketplace list --json "" plugin list --marketplace chatcut-inc --json "" mcp get chatcut --json ``` A missing `chatcut-inc` marketplace on the first check is expected for a new Git-source installation; it is not a reason to remove another installed plugin. If the user already has an equivalent working hosted connection, reuse it. When the user chose the Git source and it is not already registered, add it: ```text "" plugin marketplace add https://github.com/ChatCut-Inc/agent-plugin.git --ref main "" plugin list --marketplace chatcut-inc --json ``` For an existing Git-source installation that needs updating, refresh this marketplace only, then inspect its reported version and status: ```text "" plugin marketplace upgrade chatcut-inc "" plugin list --marketplace chatcut-inc --json ``` Install or update the same Git-source plugin when needed: ```text "" plugin add chatcut@chatcut-inc ``` Preserve `chatcut-desktop@openai-curated-remote` and any other existing sources. Do not upgrade every marketplace as part of ChatCut setup. If the installed CLI does not support a command shown here, inspect its help and report the mismatch rather than guessing flags or editing unrelated configuration. ### Connection and login If the hosted connection requires authorization, run one login attempt: ```text "" mcp login chatcut ``` Let the user complete account sign-in and consent. Do not handle credentials. If the user cancels, stop the login flow. For a transient timeout or callback failure, inspect the error before retrying; do not run concurrent logins or loop indefinitely. Verify installation and registration again: ```text "" plugin list --marketplace chatcut-inc --json "" mcp get chatcut --json ``` Check for installed/enabled status and the intended hosted server, `https://api.chatcut.io/api/external-mcp/mcp`. These checks prove configuration, not that the current conversation can call tools. Discover the tools exposed to this conversation and use an appropriate read-only ChatCut check from the installed entry skill to confirm the selected connection works. ### Focused troubleshooting - If Git is missing, check `git --version` and the desktop app's documented bundled Git location before considering a separate installation. Do not assume a runtime path exists on every machine. - For network failures, report the original error. Use an existing user-configured proxy only after confirming its address; do not probe guessed ports or leave a broken proxy configured. - Browser-control availability is separate from ChatCut MCP availability. Use the current host's documented browser tools if available. Do not install or modify Node REPL, PATH, or browser MCP configuration merely to satisfy this guide. - If a required capability is unavailable, preserve the successful setup steps and explain the remaining blocker. Do not turn a browser-tool error into a claim that ChatCut login failed. ## Choose a creation task Continue in the current conversation when ChatCut tools are available. Read the installed getting-started instructions and use the current catalog tools, when exposed, to find a relevant Skill. Do not rely on a fixed list of Skill IDs, names, versions, or capabilities from this website. Ask only for information the user has not already provided. Offer a small set of choices based on their request, for example: - Edit existing footage, including a talking-head video. - Turn an idea or script into a video or motion graphic. - Generate media for a new or existing project. Retain any chosen Skill, uploaded files, media URLs or local paths, project ID, and user constraints. Confirm an existing project or create one for the selected task; do not create an empty demo project solely as an installation check. Open the corresponding editable ChatCut project using the selected connection's supported tools. Check the current Skill's required inputs and show the next steps before any generation or editing that requires user approval. A skills-only package does not automatically include a custom sidebar, a homepage, native draft handoff, or in-page workflow generation. Describe only capabilities actually exposed by the installed package and host. ## Only hand off when this conversation cannot load the tools After a new installation or connection change, the host may require a fresh conversation before it exposes tools. Check first; do not assume every setup conversation is stale. If tools are still absent, prepare one concise continuation message in the user's language, including: ```text Continue my ChatCut setup and creation request. - Route and plugin source: - Connection status: - Project: - Request: - Media: - Next step: ``` Include no credentials or tokens. Do not claim attached files transferred to another conversation unless the host confirms that they did. Preserve accessible references and say which files would need attaching again. When the user has authorized a new conversation and the host supports it, create one with this continuation message and the same workspace context, then open it. Follow the host's tool permissions; do not send messages to another task without user authorization. Otherwise, give the user the exact continuation message and the missing host capability. Do not create a chain of recovery conversations. ## Report what is ready Separate these outcomes in the user's language: 1. The intended plugin is installed and enabled, with its verified source. 2. The selected ChatCut connection is authorized and its tools work in the current conversation, or the precise remaining blocker. 3. The user's selected creation task has an editable project and a clear next step, or the input still needed. A directory click, a copied prompt, an analytics receipt, or a newly created conversation is not installation or creation success.