Skip to content

Open source CapCut alternative.

TypeScript

docs: the ChatGPT card's stripped chrome is deliberate

David Le0b7dc10332d7
diff --git a/AGENTS.md b/AGENTS.md
index a7521bca..d3a087d5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -39,7 +39,7 @@ Every Cut change has to hold on every surface, and the plan for it says how:
- **Headed and headless.** Whatever the tab can do, the Bun engine and the worker runner can do: chat tools, rendering, media reads. Headless installs browser primitives — canvas, decoders, Web Audio, fonts — behind narrow seams (`lib/raster.ts`, the frame sink in `lib/mediaRead.ts`, the font installer in `lib/fontAssets.ts`, the kit's `surface.ts`) so one implementation serves both; reach for those seams before writing a second path.
- Allocate canvases and decode images through the raster seam. Direct `document`, `window`, `FileReader`, `createImageBitmap`, or `FontFace` use in `site/src/cut/lib/` or `packages/effects-kit/` breaks a job.
- When a surface genuinely cannot carry a feature, give it a fallback and say so in the summary and the guide.
-- **ChatGPT is a client too.** The MCP adapter under `site/src/clients/chatgpt/` runs the same project tool catalog as headless worker jobs, so a tool or schema change has to hold there as well. `docs/guides/chatgpt-app.md` is the guide.
+- **ChatGPT is a client too.** The MCP adapter under `site/src/clients/chatgpt/` runs the same project tool catalog as headless worker jobs, so a tool or schema change has to hold there as well. `docs/guides/chatgpt-app.md` is the guide. Every `embed=chatgpt` gate in the editor is deliberate — the card hides the generation tabs, Donkey's own chat, Share, Record and the credit pills, so leave them out of the frame.
- **The AI chat drives it too.** A functional change ships with its chat surface: a tool the assistant can call, and descriptions/system-prompt lines that teach the new capability. Derive tool schemas and prompt text from the same exported constants the UI uses (style id lists, model registries) so the catalog updates itself; check the tool files beside the component (`*.tools.ts`) and `site/src/cut/server/ai/catalog.ts`.
- The chat surface is kept true, both directions. Removing or reshaping a feature means deleting its tool and its prompt/skill mentions in the same change — grep the catalog, the `*.tools.ts` files, the skills library, and `lib/aiTools.ts` for the old names, ids, and parameters. A tool that describes behavior the code no longer has, offers an option that no longer exists, or is missing a setting the UI gained is a bug: the model calls what the catalog teaches.
diff --git a/CLAUDE.md b/CLAUDE.md
index a7521bca..d3a087d5 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -39,7 +39,7 @@ Every Cut change has to hold on every surface, and the plan for it says how:
- **Headed and headless.** Whatever the tab can do, the Bun engine and the worker runner can do: chat tools, rendering, media reads. Headless installs browser primitives — canvas, decoders, Web Audio, fonts — behind narrow seams (`lib/raster.ts`, the frame sink in `lib/mediaRead.ts`, the font installer in `lib/fontAssets.ts`, the kit's `surface.ts`) so one implementation serves both; reach for those seams before writing a second path.
- Allocate canvases and decode images through the raster seam. Direct `document`, `window`, `FileReader`, `createImageBitmap`, or `FontFace` use in `site/src/cut/lib/` or `packages/effects-kit/` breaks a job.
- When a surface genuinely cannot carry a feature, give it a fallback and say so in the summary and the guide.
-- **ChatGPT is a client too.** The MCP adapter under `site/src/clients/chatgpt/` runs the same project tool catalog as headless worker jobs, so a tool or schema change has to hold there as well. `docs/guides/chatgpt-app.md` is the guide.
+- **ChatGPT is a client too.** The MCP adapter under `site/src/clients/chatgpt/` runs the same project tool catalog as headless worker jobs, so a tool or schema change has to hold there as well. `docs/guides/chatgpt-app.md` is the guide. Every `embed=chatgpt` gate in the editor is deliberate — the card hides the generation tabs, Donkey's own chat, Share, Record and the credit pills, so leave them out of the frame.
- **The AI chat drives it too.** A functional change ships with its chat surface: a tool the assistant can call, and descriptions/system-prompt lines that teach the new capability. Derive tool schemas and prompt text from the same exported constants the UI uses (style id lists, model registries) so the catalog updates itself; check the tool files beside the component (`*.tools.ts`) and `site/src/cut/server/ai/catalog.ts`.
- The chat surface is kept true, both directions. Removing or reshaping a feature means deleting its tool and its prompt/skill mentions in the same change — grep the catalog, the `*.tools.ts` files, the skills library, and `lib/aiTools.ts` for the old names, ids, and parameters. A tool that describes behavior the code no longer has, offers an option that no longer exists, or is missing a setting the UI gained is a bug: the model calls what the catalog teaches.