Turn a 3-minute unedited screen recording into 1080p autonomously edited clips just by typing what you need. Whether it's letting AI independently plan and e...
---
name: agentic-video
version: "1.0.0"
displayName: "Agentic Video β AI Edits Videos End to End"
description: >
Turn a 3-minute unedited screen recording into 1080p autonomously edited clips just by typing what you need. Whether it's letting AI independently plan and execute multi-step video edits without manual input or quick social content, drop your raw video footage and describe the result you want. No timeline dragging, no export settings β 1-2 minutes from upload to download.
metadata: {"openclaw": {"emoji": "π€", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}
---
## Getting Started
> Share your raw video footage and I'll get started on autonomous AI editing. Or just tell me what you're thinking.
**Try saying:**
- "edit my raw video footage"
- "export 1080p MP4"
- "cut the pauses, add transitions, and"
### Getting Connected
Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".
**If `NEMO_TOKEN` is in the environment**, use it directly and create a session. Otherwise, acquire a free starter token:
- Generate a UUID as client identifier
- POST to `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token` with the `X-Client-Id` header
- The response includes a `token` with 100 free credits valid for 7 days β use it as NEMO_TOKEN
**Then create a session** by POSTing to `https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent` with Bearer authorization and body `{"task_name":"project","language":"en"}`. The `session_id` in the response is needed for all following requests.
Tell the user you're ready. Keep the technical details out of the chat.
# Agentic Video β AI Edits Videos End to End
Send me your raw video footage and describe the result you want. The autonomous AI editing runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload a 3-minute unedited screen recording, type "cut the pauses, add transitions, and generate a summary caption for each scene", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.
Worth noting: the more context you give in your prompt, the better the agent sequences its editing steps.
## Matching Input to Actions
User prompts referencing agentic video, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.
| User says... | Action | Skip SSE? |
|-------------|--------|----------|
| "export" / "ε―ΌεΊ" / "download" / "send me the video" | β Β§3.5 Export | β
|
| "credits" / "η§―ε" / "balance" / "δ½ι’" | β Β§3.3 Credits | β
|
| "status" / "ηΆζ" / "show tracks" | β Β§3.4 State | β
|
| "upload" / "δΈδΌ " / user sends file | β Β§3.2 Upload | β
|
| Everything else (generate, edit, add BGMβ¦) | β Β§3.1 SSE | β |
## Cloud Render Pipeline Details
Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.
All calls go to `https://mega-api-prod.nemovideo.ai`. The main endpoints:
1. **Session** β `POST /api/tasks/me/with-session/nemo_agent` with `{"task_name":"project","language":"<lang>"}`. Gives you a `session_id`.
2. **Chat (SSE)** β `POST /run_sse` with `session_id` and your message in `new_message.parts[0].text`. Set `Accept: text/event-stream`. Up to 15 min.
3. **Upload** β `POST /api/upload-video/nemo_agent/me/<sid>` β multipart file or JSON with URLs.
4. **Credits** β `GET /api/credits/balance/simple` β returns `available`, `frozen`, `total`.
5. **State** β `GET /api/state/nemo_agent/me/<sid>/latest` β current draft and media info.
6. **Export** β `POST /api/render/proxy/lambda` with render ID and draft JSON. Poll `GET /api/render/proxy/lambda/<id>` every 30s for `completed` status and download URL.
Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Three attribution headers are required on every request and must match this file's frontmatter:
| Header | Value |
|--------|-------|
| `X-Skill-Source` | `agentic-video` |
| `X-Skill-Version` | frontmatter `version` |
| `X-Skill-Platform` | auto-detect: `clawhub` / `cursor` / `unknown` from install path |
Include `Authorization: Bearer <NEMO_TOKEN>` and all attribution headers on every request β omitting them triggers a 402 on export.
**Draft field mapping**: `t`=tracks, `tt`=track type (0=video, 1=audio, 7=text), `sg`=segments, `d`=duration(ms), `m`=metadata.
```
Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)
```
### Backend Response Translation
The backend assumes a GUI exists. Translate these into API actions:
| Backend says | You do |
|-------------|--------|
| "click [button]" / "ηΉε»" | Execute via API |
| "open [panel]" / "ζεΌ" | Query session state |
| "drag/drop" / "ζζ½" | Send edit via SSE |
| "preview in timeline" | Show track summary |
| "Export button" / "ε―ΌεΊ" | Execute export workflow |
### Reading the SSE Stream
Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty `data:` lines mean the backend is still working β show "β³ Still working..." every 2 minutes.
About 30% of edit operations close the stream without any text. When that happens, poll `/api/state` to confirm the timeline changed, then tell the user what was updated.
### Error Handling
| Code | Meaning | Action |
|------|---------|--------|
| 0 | Success | Continue |
| 1001 | Bad/expired token | Re-auth via anonymous-token (tokens expire after 7 days) |
| 1002 | Session not found | New session Β§3.0 |
| 2001 | No credits | Anonymous: show registration URL with `?bind=<id>` (get `<id>` from create-session or state response when needed). Registered: "Top up credits in your account" |
| 4001 | Unsupported file | Show supported formats |
| 4002 | File too large | Suggest compress/trim |
| 400 | Missing X-Client-Id | Generate Client-Id and retry (see Β§1) |
| 402 | Free plan export blocked | Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export." |
| 429 | Rate limit (1 token/client/7 days) | Retry in 30s once |
## Tips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add transitions, and generate a summary caption for each scene" β concrete instructions get better results.
Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.
Export as MP4 for widest compatibility.
## Common Workflows
**Quick edit**: Upload β "cut the pauses, add transitions, and generate a summary caption for each scene" β Download MP4. Takes 1-2 minutes for a 30-second clip.
**Batch style**: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.
**Iterative**: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.
don't have the plugin yet? install it then click "run inline in claude" again.