Pireel Studio: an open-source AI video editor you drive from the timeline or from an agent

Who Pireel Studio is for, and the editing problem it targets

Pireel Studio is a browser-native video editor built for two kinds of users at once: a person working directly on a canvas and timeline, and an AI agent that edits the same project through chat or a plugin. The README frames the goal as keeping AI in a real editing workspace rather than a text box that produces a finished file. You stay in control of the canvas, timeline, captions, graphics, audio, and export.

The projects it names are concrete. Talking-head videos with cleaner pacing and readable captions. Short clips cut from longer recordings. Product demos, tutorials, explainers and marketing videos. Multi-source edits that mix video, images, audio and graphics. Multiple versions for different platforms. The package description adds a second angle: multi-source projects and independently editable outputs, meaning one project can fan out into several deliverables rather than one master file.

That combination is the reason the project exists. Most editors assume a single human operator and a single output. Pireel assumes a project that several inputs feed and several outputs consume, and it exposes that project to an agent. If your work is a single clip trimmed once, the extra structure buys you little.

How the project is put together: a pnpm workspace with a studio shell

The repository is a pnpm workspace. The top level holds apps/, packages/, pnpm-workspace.yaml, pnpm-lock.yaml, tsconfig.json and the usual licence and notice files. The root package.json is private and pins [email protected] through the packageManager field. Every script delegates to one workspace package, @pireel/studio-oss-shell: dev, build and preview all run pnpm --filter @pireel/studio-oss-shell followed by the matching command. Tests run through vitest run at the root.

So the editable surface is the shell package under apps/, and the packages/ directory carries the shared code. The dependency list tells you what happens inside that shell. React 19 and Vite 8 for the UI, Tailwind 4 for styling, mediabunny for media handling, and onnxruntime-web plus @mediapipe/tasks-vision and @jitsi/rnnoise-wasm for in-browser model work such as vision tasks and noise suppression. Audio time-stretching comes from signalsmith-stretch. The AI side uses the ai and @ai-sdk/react packages, and fast-json-patch and jsondiffpatch sit alongside them, which points at a project state that is patched and diffed rather than rewritten wholesale.

That last detail is the architectural claim worth noting. A timeline that an agent edits needs a state representation an agent can change surgically, and a diff-and-patch pair is one way to get there. The README does not document the state schema, so the exact shape of the patch stream is not something the repository states.

Installing Pireel Studio locally and making a first edit

The README gives the open-source path in four commands. Corepack enables the pinned package manager, pnpm install resolves the workspace, and pnpm dev starts the shell.

corepack enable
pnpm install
pnpm dev

Open the URL the terminal prints and import your media. That is the whole documented first run: no environment file, no API key, no database step appears in the README.

The README also states that the open-source edition focuses on local editing. Built-in Chat and connected services belong to the hosted experience at pireel.com, so a local run gives you the canvas and timeline rather than the chat surface. Expect the first meaningful step to be importing a clip and trimming it on the timeline.

To bring an agent in, the README installs a separate public plugin rather than a package inside this repository:

npx skills add pireel/pireel-agent

After that, the README says to ask your agent to set up Pireel, and points at the connection guide at pireel.com/connect-agent.md for the list of supported agents. The plugin lives in its own repository, pireel/pireel-agent, and the README states it is licensed separately under Apache-2.0.

What the open-source edition does not give you

The clearest limitation is stated by the project itself. The README separates the local edition from the hosted one: built-in Chat and connected services are part of pireel.com, not the repository you clone. If your reason for picking Pireel is the chat-driven editing shown in the hero image, the open-source checkout is not that product. You get the editor shell and you supply the agent.

The agent path is similarly indirect. The plugin is not a workspace package here; it installs through npx skills add pireel/pireel-agent and connects over MCP, and the README defers supported agents to an external guide. Nothing in the repository states which agents are verified, what the plugin exposes as tools, or what happens when an agent patches a timeline in a way the editor rejects. The diff and patch dependencies suggest conflicts are representable, but rollback behaviour is not documented in the README.

There is also a runtime cost that follows from the dependency list. onnxruntime-web, MediaPipe tasks and an RNNoise WASM build all execute in the browser. That is what keeps editing local, and it is also why a low-powered machine or a browser without the needed capabilities will feel the difference. The repository does not publish hardware requirements, so treat that as something to measure on your own hardware before standardising on it.

How Pireel Studio differs from CapCut and from script-first AI editors

The README positions Pireel as the open-source alternative to CapCut and ChatCut, and the difference is not the feature list. CapCut is a closed desktop and mobile application: you install a binary, your project lives in its format, and automation happens only through whatever the vendor exposes. Pireel is a TypeScript workspace you build and run yourself, with an AGPL-3.0-only licence, and the project state is reachable by an agent through MCP rather than through a vendor API.

Against script-first AI editors, the split is where the edit lives. Those tools take a prompt or a transcript and hand back a rendered file. Pireel keeps a canvas, a timeline, captions, graphics and audio as first-class objects, and the README describes AI as helping with the first cut while you keep control of the rest. The practical consequence: you can intervene at any point instead of regenerating from a prompt and hoping the second take is closer.

That flexibility is also the cost. A script-first tool needs a prompt. Pireel needs a running web app, a package manager, and an agent you have configured. If your team has no front-end build pipeline, the barrier is real.

Licence, upgrade cost, and what a fork actually commits to

Pireel Studio is AGPL-3.0-only, declared both in the README badge and in the licence field of the root package.json. The AGPL is the network-copyleft variant, so the obligation is not limited to shipping binaries: if you run a modified version as a network service, the licence's terms reach that service. Whether your deployment triggers that is a question for your own counsel, not something this article can settle. What the repository does state plainly is that the agent plugin is separate and Apache-2.0, so the two halves of the stack carry different terms.

THIRD_PARTY_NOTICES.md sits at the top level, which is where the bundled dependencies and their licences are recorded. Anyone redistributing a build should read it rather than assume the dependency tree is uniformly permissive.

Upgrade cost is shaped by the workspace. The root pins [email protected], and the lockfile is committed, so dependency drift is at least visible in diffs. There are no retrieved releases, and the root package version is 0.1.0, so there is no published changelog to plan around. The last push to the default branch was on 2026-09-08. Upgrading means reading commits and lockfile changes yourself rather than following release notes.

Editorial conclusion

Adopt Pireel Studio if you want an AGPL-3.0 editing surface that a local model or an agent can drive, and you are willing to run a pnpm workspace yourself. Skip it if you need a hosted editor with built-in Chat, or if AGPL-3.0 obligations do not fit how you distribute your product. Before committing, run the four install commands, confirm the dev server serves the shell package, and read THIRD_PARTY_NOTICES.md for the licences bundled alongside AGPL-3.0-only.

Frequently asked questions

Official sources

1. Issues
2. License: AGPL-3.0
3. pireel/pireel on GitHub
4. Project website
5. README