为 AI Agent 安装 StarCut

Install StarCut

Reply to the user in the language they are currently using. The instructions below are written only in English so there is one execution contract.

This guide is generated for the current environment:

Mode: production
Marketplace: https://github.com/starrank-soft/starcut-plugin.git
Marketplace: starrank-soft/starcut-plugin
Package: workbuddy
MCP server: https://api.starcut.io/mcp

Host gate

Run installation only from WorkBuddy or CodeBuddy on the machine where StarCut will be used. A plain browser chat cannot install the host plugin marketplace.

If this is not the correct host surface, stop and ask the user to open that host and send:

Read starcut.io/workbuddy.md and install StarCut for me. Complete authentication and verification.

Execution contract

Read this whole guide before running commands. Complete installation, login, and verification in order. Do not stop after an intermediate success. Do not claim later steps passed when an earlier step failed.

Use the CodeBuddy/WorkBuddy CLI (codebuddy) from this local install. WorkBuddy and CodeBuddy share this CLI surface. Do not substitute an unrelated binary from PATH unless the user confirms it is the same app.

codebuddy --version

Before installing, verify Node.js is available:

node --version

Use the bundled helper for login and configuration. Do not recreate its flow with inline shell, Python, or curl, and never paste credentials into the conversation.

WorkBuddy may not complete remote MCP authentication from its settings UI. Use the bundled helper below when login is required.

Install skills

Add the marketplace and install the StarCut plugin so WorkBuddy loads the local skills package:

codebuddy plugin marketplace add starrank-soft/starcut-plugin
codebuddy plugin marketplace list
codebuddy plugin install starcut@starcut
codebuddy plugin list --json

If the session requires a reload after install:

/reload-plugins

Log in

WorkBuddy/CodeBuddy may not expose working native OAuth for remote MCP. Treat a bare HTTP MCP URL that returns 401 Unauthorized as expected before login.

Run the helper on the same machine as WorkBuddy/CodeBuddy and complete the browser prompt once. Keep that process attached until it exits. If the terminal returns a background job ID, wait on that same job until it reports exit code 0; do not start another helper or kill the original after the browser opens.

node "<STARCUT_PLUGIN_REPO>/workbuddy/scripts/mcp-manual-oauth.mjs" --host workbuddy --mcp-url "https://api.starcut.io/mcp" --write-config

Windows PowerShell:

node "<STARCUT_PLUGIN_REPO>\workbuddy\scripts\mcp-manual-oauth.mjs" --host workbuddy --mcp-url "https://api.starcut.io/mcp" --write-config

Treat the browser success page and helper exit code 0 as success. If the helper fails, report its exact error. Never paste credentials into the conversation.

Configure MCP

The helper merges starcut into WorkBuddy's global MCP config:

Platform	Path
macOS / Linux	~/.workbuddy/mcp.json
Windows	%USERPROFILE%\.workbuddy\mcp.json

The filename is exactly mcp.json, with no leading dot. Existing MCP servers are preserved, and the StarCut entry points to https://api.starcut.io/mcp. Do not read or print the stored credential. Restart WorkBuddy or start a new session after the helper succeeds.

If WorkBuddy later exposes a native OAuth button for starcut, you may use it instead of running the helper. Until then, treat the helper-owned OAuth and configuration flow above as the primary path.

Verify

codebuddy plugin list --json

The helper exit code 0 confirms StarCut login, configuration, and MCP verification. Do not inspect the stored credential or run a second login.

After installing skills, start a new WorkBuddy/CodeBuddy conversation and confirm that the StarCut tools are present. If the host later reports Unauthorized, rerun the helper.

Also confirm:

1. starcut is installed and enabled in codebuddy plugin list --json.
2. The MCP endpoint in use is:

https://api.starcut.io/mcp

If the endpoint, plugin, or authentication state is wrong, fix that exact step and verify again. Starting a new conversation does not repair installation or login.

Start editing

After installation succeeds, tell the user to start a fresh conversation and send the prompt below in their language. Do not add implementation details.

StarCut is ready. Help me start a new video project. Briefly tell me how you can
help bring it to life, then ask what materials I have and what I want the finished
video to be like.

Completion

Report success only after all of these are true:

1. The plugin or project bundle is installed and enabled.
2. starcut is authenticated against https://api.starcut.io/mcp.
3. The user received the short startup prompt for a fresh conversation.

If any step fails, report the exact failed step and error without claiming later steps passed.