Edit videos with Hermes Agent

Hermes is Nous Research's autonomous agent. It runs as a CLI, a desktop app, and connects to 20+ messaging platforms. Register PandaStudio with one CLI command, then chat with Hermes from any of them to edit videos.

Install PandaStudio + Hermes Agent

PandaStudio from writepanda.ai. Launch it once so the local credentials file is written. Then install Hermes:

bash

curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash

Then run hermes setup --portal once to log in via the Nous portal, and verify with hermes --version.

Enable MCP support inside Hermes

Hermes ships MCP as an opt-in extra. Install it once:

bash

cd ~/.hermes/hermes-agent && uv pip install -e ".[mcp]"

Register PandaStudio with one command

No env var. No config file. No system Node install. PandaStudio ships its MCP server inside the app and exposes it on PATH as pandastudio-mcp — the server auto-discovers credentials at startup.

bash

hermes mcp add pandastudio --command pandastudio-mcp

On macOS, run sudo /Applications/PandaStudio.app/Contents/Resources/cli/install-cli-symlink-mac.sh once to drop pandastudio-mcp on PATH. The Windows installer handles PATH automatically.

Reload Hermes so the new server picks up:

bash

hermes mcp reload

In a Hermes chat, confirm it loaded: "Tell me which MCP-backed tools are available."

Drive PandaStudio from any Hermes surface

Talk to Hermes from the terminal, the desktop app, or any of its connected messaging platforms:

"Open my latest recording, transcribe it, remove filler words and silences, then export an MP4."
"Create a new 9:16 project, import the file at ~/Recordings/launch.mov, add bold captions, and preview it."
"List all my projects from this week and tell me which one is longest."

Hermes routes the request to its agent, which picks the right PandaStudio tools automatically. Because Hermes has memory + scheduling, you can also set up recurring jobs.

Troubleshooting

PandaStudio tools don't appear — make sure PandaStudio has been launched at least once on this machine. Without that, the local credentials file doesn't exist and the MCP server has nothing to discover.
Running Hermes on Windows via WSL2 — launch from a Windows-mounted path (/mnt/c/...) when Windows-side binaries are involved. Pure WSL stays inside the WSL filesystem.
Want to scope which tools Hermes can call? — edit ~/.hermes/config.yaml and add a tools.include array under the server block, e.g. [project_list, project_show, motion_generate], so Hermes can never call destructive verbs like project_delete.

Reference

CLI & MCP commands

Browse all 60+ verb-noun commands the agent can call.