product-help

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ChatCut Product Help

ChatCut 产品帮助

If
track_export
is not loaded yet, load it with
ToolSearch
before calling it, so you use its real parameters instead of guessing.
For a ChatCut product question, the first substantive action is to search the exact topic within
https://chatcut.io/docs
and open the most relevant official page. Do not answer from memory, a search snippet, or an unopened result. Use the host's native search and page-reading capabilities; this Skill defines retrieval and decision rules, not a second copy of product facts.
如果尚未加载
track_export
,请先使用
ToolSearch
加载它,然后再调用,以便使用其实际参数,而不必猜测。
对于 ChatCut 产品问题,第一个实质性操作是在
https://chatcut.io/docs
中搜索准确主题,并打开最相关的官方页面。不要凭记忆、搜索摘要或尚未打开的搜索结果作答。使用宿主提供的原生搜索和页面读取能力;此 Skill 定义的是检索与决策规则,而不是产品事实的副本。

Route the question

问题路由

  • For live project, asset, timeline, item, account, or job state, use the matching ChatCut read tool. If the question is only about live state, no Docs lookup is needed.
  • For current behavior, visible UI labels, installation, credits, pricing, billing, and troubleshooting, use the owning product Docs page.
  • For availability, regressions, or version requirements, use Current versions and the Changelog in addition to the owning product Docs page.
  • For a mixed question, use tools for live state and Docs for what that state means or what the user should do next.
  • For where an export runs, where its progress shows, and where the file goes, use the export section below. It takes the place of the Docs lookup for those facts.
Treat this Skill only as stable routing guidance. Never answer a changeable product fact from remembered Skill content when current Docs can be checked. Do not use unofficial domains.
  • 对于项目、素材、时间线、条目、账户或任务的实时状态,使用对应的 ChatCut 读取工具。如果问题仅涉及实时状态,则无需查找 Docs。
  • 对于当前行为、可见 UI 标签、安装方式、credits、定价、账单和故障排查,使用负责该功能的产品 Docs 页面。
  • 对于可用性、回归问题或版本要求,除负责该功能的产品 Docs 页面外,还要使用 Current versions 和 Changelog。
  • 对于混合问题,使用工具查询实时状态,并通过 Docs 了解该状态的含义或用户接下来应执行的操作。
  • 对于导出在哪里运行、进度显示在哪里以及文件保存在哪里,使用下面的导出部分。对于这些事实,它取代 Docs 查询。
仅将此 Skill 视为稳定的路由指引。当可以查询当前 Docs 时,绝不要根据记忆中的 Skill 内容回答可变的产品事实。不要使用非官方域名。

Establish the relevant product surface

确定相关产品端

Before answering a surface- or version-dependent question, identify both the surface hosting this agent and the surface the user is asking about.
  • Prefer the explicit ChatCut runtime profile or the latest
    [chatcut-runtime]
    envelope. Map
    chatcut-web-editor
    to Web,
    chatcut-desktop
    to Desktop, and
    chatcut-workbench-client
    or
    chatcut-chat-connector
    to Agent Plugin.
  • When Agent Plugin is hosted by ChatCut Desktop, treat its bundled Skills as part of the Desktop installation. A Desktop update updates that Plugin surface too; never ask the user to update the Plugin separately in this runtime.
  • A user can ask an Agent Plugin about Desktop, or ask Desktop about a Web project. When the user names a target surface, answer for that target instead of assuming it is the same as the agent's host surface.
  • Use an app URL, client name, or version supplied by runtime context as supporting evidence. Do not infer the current surface merely because the user mentions a product in an example.
  • If no reliable signal exists and the surface changes the answer, ask which of Web, Desktop, or Agent Plugin they are using. If the answer is surface-independent, proceed without an unnecessary question.
在回答依赖于产品端或版本的问题之前,先确定承载当前 Agent 的产品端,以及用户所询问的产品端。
  • 优先使用明确的 ChatCut runtime profile 或最新的
    [chatcut-runtime]
    envelope。将
    chatcut-web-editor
    映射到 Web,将
    chatcut-desktop
    映射到 Desktop,将
    chatcut-workbench-client
    或
    chatcut-chat-connector
    映射到 Agent Plugin。
  • 当 Agent Plugin 由 ChatCut Desktop 承载时,将其 bundled Skills 视为 Desktop 安装的一部分。Desktop 更新也会更新该 Plugin 所在的产品端;在当前 runtime 下,不要让用户单独更新 Plugin。
  • 用户可能通过 Agent Plugin 询问 Desktop,或通过 Desktop 询问 Web 项目。当用户指定目标产品端时,应针对该目标回答,不要默认它与 Agent 的宿主产品端相同。
  • 使用 runtime context 提供的应用 URL、客户端名称或版本作为辅助证据。不要仅仅因为用户在示例中提到某个产品,就推断当前产品端。
  • 如果没有可靠信号,且不同产品端会改变答案,应询问用户使用的是 Web、Desktop 还是 Agent Plugin。如果答案与产品端无关,则无需提出不必要的问题。

Find the smallest useful source

查找最小必要信息来源

  1. Extract the feature name, visible UI label, error text, product surface, and version from the user's question or runtime context when available.
  2. Search the exact topic with a concise query containing only its essential terms. Prefer the most specific official result and open the smallest set of pages that establishes the answer.
  3. For ordinary usage questions, start with the owning feature or troubleshooting page. For availability, regression, update, or version questions, directly open
    https://chatcut.io/docs/releases
    and
    https://chatcut.io/docs/changelog
    , then open the matching Changelog entry.
  4. For one user question, issue at most two search queries total: the exact topic, then one narrower query if needed. After that, stop searching and use
    https://chatcut.io/docs/llms.txt
    only as an index, then open the target page. If the canonical pages and index are unavailable or still do not identify a supporting page, stop retrieval and state the uncertainty; do not keep trying broader keywords. Do not load the full Docs corpus or treat the index itself as the answer.
  5. Treat search snippets as discovery only. Base claims on opened page content and cite the exact official page supporting each consequential claim about product behavior, platform support, price, credit cost, or version. Prefer a detail page over the Docs home or a Changelog listing page.
  6. Do not infer an unsupported feature or version from a similar entry. If official pages do not establish the answer, state the uncertainty.
  1. 在可用的情况下,从用户问题或 runtime context 中提取功能名称、可见 UI 标签、错误文本、产品端和版本。
  2. 使用仅包含必要术语的简洁查询搜索准确主题。优先选择最具体的官方结果,并打开足以确定答案的最小页面集合。
  3. 对于常规使用问题,从负责该功能或故障排查的页面开始。对于可用性、回归、更新或版本问题,直接打开
    https://chatcut.io/docs/releases
    和
    https://chatcut.io/docs/changelog
    ,然后打开对应的 Changelog 条目。
  4. 针对一个用户问题,总共最多发起两次搜索查询:先搜索准确主题;如有需要,再进行一次更窄的查询。此后停止搜索,只将
    https://chatcut.io/docs/llms.txt
    用作索引,然后打开目标页面。如果规范页面和索引均无法访问,或仍无法确定能够提供依据的页面,则停止检索并说明不确定性;不要继续尝试更宽泛的关键词。不要加载完整的 Docs 语料库,也不要把索引本身当作答案。
  5. 仅将搜索摘要用于发现页面。应以已打开的页面内容为依据,并引用能够支持每项有关产品行为、平台支持、价格、credits 成本或版本的重要结论的确切官方页面。优先使用详情页,而不是 Docs 首页或 Changelog 列表页。
  6. 不要根据相似条目推断不受支持的功能或版本。如果官方页面无法确定答案,应说明不确定性。

Decide whether the user must update

判断用户是否必须更新

  • Web changes are deployed server-side. If Current versions or the Changelog says the Web release is live, do not tell the user to install an update.
  • For Desktop or a standalone Agent Plugin, compare the user's current version only with the minimum version on the relevant individual change. A release header's current Desktop or Plugin version is not automatically every change's minimum. If the current version is older, actively recommend updating and use the official installation/update page for the steps.
  • Treat a capability available on Web as available through Agent Plugin unless the official Docs or Changelog explicitly says otherwise. Web UI, service, and tool changes are inherited server-side and do not require a Plugin update. Require a newer standalone Plugin version only when the individual change explicitly names a Plugin minimum because its bundled Skill changed.
  • When a capability is explicitly Desktop-only, tell a Web user that it requires Desktop and link the Desktop download instructions. Do not infer Desktop-only merely because a release also lists a Desktop version.
  • If the user's product or version is unknown and it changes the recommendation, ask for it or show how to check it instead of guessing.
  • Web 更改在服务器端部署。如果 Current versions 或 Changelog 说明 Web 版本已经上线,则不要让用户安装更新。
  • 对于 Desktop 或独立 Agent Plugin,仅将用户的当前版本与相关单项变更所列的最低版本进行比较。发布条目标头中的当前 Desktop 或 Plugin 版本不能自动视为每项变更的最低版本。如果当前版本较旧,应明确建议更新,并使用官方安装或更新页面中的步骤。
  • 除非官方 Docs 或 Changelog 明确另有说明,否则将 Web 上可用的功能视为可通过 Agent Plugin 使用。Web UI、服务和工具的更改会由服务器端继承,不需要更新 Plugin。只有当单项变更因 bundled Skill 发生变化而明确给出 Plugin 最低版本时,才要求更新独立 Plugin。
  • 当某项功能明确仅支持 Desktop 时,应告知 Web 用户该功能需要 Desktop,并提供 Desktop 下载说明。不要仅仅因为某个发布条目同时列出了 Desktop 版本,就推断该功能仅支持 Desktop。
  • 如果用户使用的产品或版本未知,且这会影响建议,应询问用户或说明如何检查,而不要猜测。

Export location, progress, and stuck exports

导出位置、进度与卡住的导出

These are stable UI facts, not changeable product facts, so answer directly instead of routing to Docs first; still check
/docs/exporting
and
/docs/web-export-limits
for anything version- or plan-specific.
  • Where to export: the Export button in the editor's top toolbar, on both Web and Desktop.
  • Where progress shows: an "Export queue" icon appears immediately to the right of the Export button (Desktop calls it "Task queue" while a link import is also active). It only renders once that specific browser tab (Web) or app window (Desktop) has an export to show; a tab/window that has not started or observed one shows no icon at all. If the user says the icon is not there, that can be correct — do not assume it is a bug. Before guessing at an unrelated cause (browser settings, hardware acceleration, downloads being blocked), use a tool to check the real status (on Web,
    track_export
    reads cloud renders and exports rendering in an open browser tab alike; on Desktop,
    track_progress
    with
    target="export"
    reads the video/audio/motion_graphic renders of the open project, including ones started from the Export button, and takes the
    taskId
    local_export
    returned to read one of them). A Web browser export can only be read while the tab rendering it is open and connected; when the tool says it cannot read one, tell the user to check the editor tabs they have open for the project.
  • What "queued" means: a Web browser-local export queues per tab (capped at a small number of concurrent/waiting exports in that tab); a cloud render queues on the backend and is not tied to any tab. Desktop native exports run in the desktop app itself. None of these need the export to be visible in the UI to keep progressing.
  • Where the finished file goes: a Web export downloads through the browser's normal download location automatically once it finishes — no manual step. A Desktop
    local_export
    writes to the
    outputPath
    it returned (the OS Videos/ChatCut folder by default, or wherever the user chose to save).
以下内容属于稳定的 UI 事实,而不是可变的产品事实,因此可以直接回答,无需先路由到 Docs;但对于任何与版本或套餐相关的内容,仍需检查
/docs/exporting
和
/docs/web-export-limits
。
  • 在哪里导出: Web 和 Desktop 的编辑器顶部工具栏中都有 Export 按钮。
  • 在哪里查看进度: Export 按钮紧右侧会出现一个“Export queue”图标(Desktop 在链接导入同时处于活动状态时将其称为“Task queue”)。只有当特定浏览器标签页(Web)或应用窗口(Desktop)中存在需要显示的导出任务时,该图标才会呈现;未启动或未观察到导出任务的标签页或窗口完全不会显示该图标。如果用户表示图标不存在,这可能是正确情况,不要假定为故障。在猜测无关原因(浏览器设置、硬件加速、下载被阻止)之前,应使用工具检查真实状态:在 Web 上,
    track_export
    既可读取云端渲染,也可读取在打开的浏览器标签页中进行的导出;在 Desktop 上,带有
    target="export"
    的
    track_progress
    可读取当前项目的视频、音频和
    motion_graphic
    渲染,包括通过 Export 按钮启动的任务,并可使用返回的
    taskId
    local_export
    读取其中一项。只有当渲染 Web 导出的标签页处于打开且连接状态时,才能读取该导出;当工具提示无法读取时,应让用户检查当前为该项目打开的编辑器标签页。
  • “queued”的含义: Web 浏览器本地导出按标签页排队(每个标签页同时进行或等待的导出数量上限较小);云端渲染在后端排队,不与任何标签页绑定。Desktop 原生导出在桌面应用自身运行。即使导出未显示在 UI 中,这些导出也会继续进行。
  • 完成的文件保存在哪里: Web 导出完成后会自动通过浏览器的常规下载位置下载,无需手动操作。Desktop 的
    local_export
    会写入其返回的
    outputPath
    (默认为操作系统的 Videos/ChatCut 文件夹,或用户选择保存的位置)。

Answering and fallback rules

回答与回退规则

  • Try to complete supported editing actions with ChatCut tools first. Give manual UI steps only when the user asked for guidance or the action cannot be completed directly.
  • Use localized visible UI names verified in the current Docs. Do not invent routes, buttons, plan terms, prices, credit costs, platform support, or version numbers.
  • Current feature Docs describe present behavior. Changelog entries describe historical rollout and minimum versions. If wording appears inconsistent, use the current feature page for present behavior and the release entry only for the historical/version claim; state any unresolved ambiguity.
  • Do not claim access to live balances, ledgers, quotas, subscription state, or installation state unless a tool or runtime context actually provides it.
  • If official Docs cannot be reached or do not answer the question, say what could not be verified and avoid a confident guess. Offer the closest official Docs entry or the in-product Feedback path after giving all verified guidance.
  • Do not expose internal implementation details, release automation, review notes, or unpublished preview content to end users.
  • 首先尝试使用 ChatCut 工具完成受支持的编辑操作。只有当用户请求操作指导,或无法直接完成操作时,才提供手动 UI 步骤。
  • 使用经当前 Docs 验证的本地化可见 UI 名称。不要编造路径、按钮、套餐术语、价格、credits 成本、平台支持或版本号。
  • 当前功能 Docs 描述现有行为。Changelog 条目描述历史发布情况和最低版本。如果表述 seemingly 不一致,应使用当前功能页说明当前行为,仅使用发布条目说明历史或版本相关信息,并说明任何尚未解决的歧义。
  • 除非工具或 runtime context 实际提供相关信息,否则不要声称能够访问实时余额、账本、配额、订阅状态或安装状态。
  • 如果无法访问官方 Docs 或 Docs 无法回答问题,应说明哪些内容无法验证,避免作出有把握的猜测。在提供所有已验证的指导后,指向最接近的官方 Docs 条目或产品内 Feedback 路径。
  • 不要向最终用户披露内部实现细节、发布自动化、评审备注或未发布的预览内容。