Two ways to extend Yaazh
No-code plugins
Built in Yaazh's Plugins tab, by hand or with your AI assistant. A plugin is a recipe: the fields you fill in each run and steps that run in order on the open project, such as export, copy to a folder, add a row to Excel or a Google Sheet, or call a webhook.
No-code pluginsDeveloper plugins
A web service you host. Its manifest lists actions; Yaazh sends each action's JSON input to your endpoint and shows the JSON you return. People run actions from the Plugins panel, and connected AI assistants run them through plugin_tool.
Working on Yaazh's editor itself rather than a plugin? Read the editor developer docs. Using Yaazh? The user guide shows every feature step by step.
Quick start
The developer kit is a dependency-free Node.js starter: an example service, the manifest validator and HTTP contract tests. It needs Node.js 20 or newer.
Save the kit
In Yaazh, open Plugins › Developer kit & test lab › Save developer kit to a folder.
Test, validate and start it
From that folder run the commands below. The service listens only on
http://127.0.0.1:4319/actions; stop it with Ctrl+C. It never runs shell commands or reads Yaazh project files.Try an action without installing
In the test lab, paste your manifest and some JSON input, pick an action and click Test action (no installation). You see the raw JSON result and how long it took. Nothing is installed, no project access is granted and no media is imported.
Try it with your AI assistant
Choose Install / update from a file, pick
manifest.json, select Development plugin, review and install. Development mode accepts onlyhttp://127.0.0.1endpoints, and development plugins are clearly labelled.
npm test
npm run validate
npm start| File | What it is |
|---|---|
manifest.json | The plugin's identity, endpoint and actions. Start here. |
server.mjs | The example action service, with no dependencies. |
catalog.json | Example media catalog. Empty until you add media you own. |
validate.mjs | Checks a manifest. Add --production before you publish. |
test.mjs | Real HTTP tests of the action contract (npm test). |
README.md | The full guide, also summarised on this page. |
The manifest
A manifest is a small JSON file that tells Yaazh who made the plugin, where its service lives and what it can do. People review it before they install, and assistants read its action descriptions to know what to send.
{
"schemaVersion": 1,
"id": "yourstudio.caption-check",
"name": "Caption Check",
"version": "1.0.0",
"author": "Your Studio",
"description": "Count caption characters and hashtags before publishing.",
"endpoint": "https://example.com/focal/actions",
"actions": [
{
"id": "check",
"title": "Check caption",
"description": "Input: {caption: string}. Returns character and hashtag counts."
}
]
}| Field | Type | Rules |
|---|---|---|
schemaVersion | number | Always 1. |
id | string | Unique; lowercase letters, numbers, dots, underscores or hyphens. focal.* is reserved. |
name, version, author, description | string | Shown to the user before they install. |
endpoint | URL | Public HTTPS on port 443, with no credentials, query or fragment. While developing: http://127.0.0.1 in development mode. |
actions | array | 1–30 unique { id, title, description }. Describe the exact JSON input and what comes back. |
mediaHosts | array, optional | Up to 20 exact lowercase domains that your media links come from. No wildcards, IP addresses, paths or ports. Leave it out for action-only plugins. |
The action protocol
When an action runs, Yaazh sends one HTTPS POST to your endpoint with Content-Type: application/json:
{
"protocolVersion": 1,
"pluginId": "yourstudio.caption-check",
"action": "check",
"input": { "caption": "A new video #reels" }
}Answer with HTTP 2xx and a JSON body. Use a 4xx or 5xx status for errors.
{ "characters": 18, "hashtags": 1 }| Limit | Value |
|---|---|
| Input sent to your action | up to 256 KB |
| Your response | up to 1 MB |
| Time per action | 60 seconds |
| Redirects | never followed |
| Project context | none: only the input you described |
Long-running work
If a job takes longer than a minute, return a job ID straight away and add a separate status action. Assistants are told to poll that action, not to report the job as finished.
A complete service
Any language and any host will do. This is the whole caption checker in Node.js, with no dependencies:
import { createServer } from 'node:http';
function check(input) {
if (typeof input?.caption !== 'string') throw new Error('Expected input.caption');
const caption = input.caption;
return {
characters: [...caption].length,
hashtags: (caption.match(/#[\p{L}\p{M}\p{N}_]+/gu) ?? []).length,
};
}
createServer(async (req, res) => {
if (req.method !== 'POST' || req.url !== '/focal/actions') return res.writeHead(404).end();
try {
let body = '';
for await (const chunk of req) {
body += chunk;
if (body.length > 256 * 1024) throw new Error('Input too large');
}
const call = JSON.parse(body);
if (call.protocolVersion !== 1 || call.action !== 'check') throw new Error('Unknown action');
res.writeHead(200, { 'Content-Type': 'application/json' }).end(JSON.stringify(check(call.input)));
} catch (error) {
res.writeHead(400, { 'Content-Type': 'application/json' }).end(JSON.stringify({ error: error.message }));
}
}).listen(8080, '127.0.0.1');Returning media
A plugin that finds footage, images or music returns direct links in this shape, and the user (or their assistant) chooses what to import:
{
"media": [
{
"name": "Studio b-roll, desk",
"kind": "video",
"url": "https://media.example.com/desk.mp4",
"sourceUrl": "https://example.com/library/desk",
"credit": "Your Studio",
"license": "Owned by Your Studio"
}
]
}- Yaazh never downloads on its own. The user clicks Import, or an assistant calls
plugin_toolwithdownload. - The link's host must be one of the manifest's
mediaHosts. - Each file can be up to 256 MB and must arrive within 180 seconds. Accepted types are PNG, JPEG and WebP images, MP4 and WebM video, and MP3 and WAV audio. HTML, other binaries, redirects and private addresses are refused.
- Images are parsed and audio and video are probed before they reach the project's library. Nothing is placed on the timeline automatically.
Plugins and AI assistants
Yaazh's MCP connection gives Claude Code, Claude Desktop, Cursor, Antigravity and other MCP clients one tool for plugins: plugin_tool. A plugin installed once in Yaazh can be used by every connected assistant, with no separate copy for each.
{ "action": "list" }{
"action": "run",
"pluginId": "yourstudio.caption-check",
"pluginAction": "check",
"input": { "caption": "A new video #reels" }
}{
"action": "download",
"pluginId": "yourstudio.media-library",
"url": "https://media.example.com/desk.mp4"
}- Results come back as
untrustedResult. Assistants treat them as data, never as instructions. - Imported media returns asset IDs, which the assistant places with Yaazh's editing tools and then saves.
- Assistants can list and run enabled actions. Only the user can install, update, enable or remove a plugin.
What a plugin can and can't do
A plugin can
- Receive the JSON input of the action being run
- Return JSON, shown to the user and the assistant as text
- Offer media links on the hosts its manifest declares
A plugin can't
- Read project files or anything else on the PC
- See Google sign-ins, browser cookies or Yaazh's tokens
- Run code, shell commands or custom UI inside Yaazh
- Reach private network addresses or follow redirects
- Change its endpoint, actions or hosts without the user reviewing it
Yaazh checks that your endpoint's address is public and pins it, and blocks redirects. If your service needs a sign-in, design your own connection flow and describe it in the plugin's description. v1 has no sign-in broker for third-party plugins, and tokens never belong in a manifest.
Update, disable and remove
| What happens | |
|---|---|
| Update | Raise version and import the manifest again with the same id. Yaazh shows the old and new endpoint, actions and media hosts for review. Updates are never fetched automatically. |
| Disable | Blocks the plugin's actions for the user and for assistants. It can still be inspected, updated or removed. |
| Remove | Deletes its registration and permissions. Your service and source code, and media the user already imported, stay where they are. |
You can change the service behind your actions at any time, as long as it keeps doing what the reviewed actions describe. New endpoints, actions or media hosts need a new manifest version.
Publish your plugin
Deploy
Put the service behind public HTTPS. Point
endpointandmediaHostsat your real domains and raiseversion.Validate
Run the production check and the contract tests (below).
Test in Yaazh
Install, update, disable and remove it. Try a denied host, the service offline and a malformed result, plus media imports and switching projects.
Share it
Publish the manifest with your source, README, licence and a privacy note saying what your service does with action input. Users install it with Install a developer plugin, review it, then click Install and enable.
node validate.mjs manifest.json --production
npm testNo-code plugins
Open the Plugins tab (the puzzle piece on the editor's left rail) and choose Make with AI, Build it myself or a template: Folder + Excel log, Google Drive + Sheet, or Send to a webhook. You decide what to fill in on each run (title, caption, hashtags, anything else) and which steps run, in order:
| Step | What it does |
|---|---|
| Export the video | MP4 at 720p to 4K, 24 to 60 fps. An unchanged edit is not rendered twice in a session. |
| Copy to a folder | Into a folder on the PC. A Google Drive, Dropbox or OneDrive desktop folder uploads it. Never overwrites a file; it adds (2) instead. |
| Add a row to Excel | A row in a tab of an .xlsx workbook, made if missing. Columns are matched by heading, and missing ones are added. A backup is kept beside it. |
| Add a row to a Google Sheet | The same in a Google Sheet tab, using the Google sign-in from Google Publishing. |
| Upload to Google Drive | Into a Drive folder, once per video. |
| Send to a webhook | POSTs JSON (every field and link, or only the values you pick) to a Zapier, Make, n8n, Slack, Discord or Apps Script link. |
Anything a step writes can use placeholders: your fields ({{title}}), Yaazh's own ({{project}}, {{projectId}}, {{date}}, {{time}}, {{duration}}, {{plugin}}) and what earlier steps made ({{file}}, {{fileName}}, {{copiedPath}}, {{driveUrl}}). A row step can update the row that already has the same value in one column, such as {{projectId}}, instead of adding a new one. Values are written as plain text, never as formulas.
Save file writes a plugin as JSON to share, and Install from a file reads one back. Webhook links are kept in Windows Credential Manager, never in the plugin or its shared file. A plugin drafted by an assistant or opened from a file is shown for review first (what each step does and where it sends things), and only the user's click installs it.

