Model or dataset
pireel/pireel avatar
pireel/pireel

pireel: the open-source edition has no Chat in it

The open-source alternative to CapCut and ChatCut. Drivable by any AI agent over MCP.

1,381 stars118 forksTypeScriptAGPL-3.0

At a glance

What is it?
pireel is a browser-native video editor built to be driven by a person, a chat interface, or an AI agent over MCP. Two of those three modes ship in the open-source edition, and the licensing is split across two repositories with different terms.
Who is it for?
pireel suits someone who wants to run a video editor locally, in a browser tab, with an agent able to drive it, and who is prepared to accept that the chat interface lives in the hosted product rather than in the repository. Two things to settle first.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • pireel/pireel1,381 ★ · +199
Star history
Repository2026-09-112026-11-15
pireel/pireel1.2k1.4k

199 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two of the three editing modes ship, and the page names the missing one

The page lists three ways to work, and they are not equivalent in what you can install.

You can edit directly in the studio on the canvas and timeline. You can describe cuts, pacing, captions and layouts in a chat interface. And you can hand the project to an AI agent such as Codex or Claude Code.

Then there is the sentence that matters:

> The open-source edition focuses on local editing. For the complete hosted experience, including built-in Chat and connected services, visit pireel.com.

So Chat is named as one of the three modes and then identified as part of the hosted product. Cloning the repository gets you the canvas and the timeline. Getting an agent to drive it is the third mode, and that one is reachable, because the agent plugin is a public package installed with:

bash
npx skills add pireel/pireel-agent

The header frames the same split more gently, saying AI can help make the first cut while you stay in control of the canvas, timeline, captions, graphics, audio and final export. That is a fair description of what the open-source part does. What it does not do is let you talk to it.

Anyone evaluating this for a team should decide which of the three modes they actually need before installing anything.

Two repositories, two licences, and a hosted product with neither

The licence section is two sentences and they point in different directions.

The editor you clone is AGPL-3.0-only. The note is specific about the variant: only, not or-later, so there is no option for a downstream project to relicense under different terms.

The agent plugin is a separate repository, `pireel/pireel-agent`, and it is licensed under Apache-2.0.

So the two halves of the agent workflow, the editor the agent controls and the plugin the agent runs, carry different licences. Apache-2.0 for the plugin means a commercial user can take that piece without the copyleft reaching it. AGPL-3.0-only for the editor means network use of a modified version is a distribution trigger.

The repository also carries a third-party notices file alongside the licence, which is what you would expect from an editor that pulls in media decoding and machine learning libraries.

The hosted product at pireel.com sits outside both, and it is where Chat and the connected services live. So the practical arrangement is a copyleft core, a permissive client, and a commercial service that adds the missing interface. That is a coherent and common shape, and it is worth understanding before you decide whether to build on the core.

Corepack is mandatory because the package manager is pinned to one version

The development instructions are four lines, and the second one exists for a reason.

bash
git clone https://github.com/pireel/pireel.git
cd pireel
corepack enable
pnpm install
pnpm dev

`corepack enable` sits between the clone and the install, and the manifest pins the package manager to an exact version with `packageManager` set to pnpm at 9.12.0.

That field is what makes the ordering matter. Package manager pinning only takes effect when the shim that reads it is active, and Corepack is what provides that shim. Without the enable step, `pnpm install` either fails because pnpm is not installed at all, or succeeds with whatever version your machine already has and silently ignores the pin.

The second consequence is that this is a pnpm workspace rather than an npm one. There is a workspace definition and a pnpm lockfile at the root, and no npm lockfile. Every root script delegates to a single workspace package named `@pireel/studio-oss-shell`, filtered by name, so the runnable application is one package inside a monorepo.

After the install you open the URL printed in the terminal and import your media. There is no configuration step, no environment file and no account.

Every dependency runs in the browser, which is what local editing means here

The dependency list is the clearest statement of what the application is.

There is an ONNX runtime for the web, which is inference compiled to WebAssembly rather than running on a server. There is a MediaPipe vision package. There is a noise-suppression module compiled to WebAssembly from a different project. There is a library called signalsmith-stretch, which is an audio time-stretcher, and another called mediabunny for media handling.

Add React and Vite and a build that produces a static bundle, and the picture is complete: speech and media processing happen in the tab. That is why the open-source edition can describe itself as focusing on local editing without that being a limitation on what it can analyse. Media does not have to leave the machine.

Two more entries explain the interface. The Vercel AI SDK, as `ai` and `@ai-sdk/react`, plus `use-stick-to-bottom` for a chat log pinned to the newest message. And a markdown renderer, `streamdown`, with four plugins for CJK text, code blocks, mathematics and Mermaid diagrams, backed by Shiki for syntax highlighting and `use-intl` for translations.

Rendering mathematics and diagrams inside a chat transcript is the kind of detail that tells you the model output is expected to be technical, which fits a tool aimed at product demos, tutorials and explainers.

Two component libraries and two JSON patch libraries in one manifest

Four dependencies overlap with each other, which is unusual enough to name.

First pair: `@base-ui/react` and `radix-ui`. Both are libraries of unstyled accessible component primitives for React. Having both means parts of the interface are built on one and parts on the other, or that one is a leftover from a migration.

Second pair: `fast-json-patch` and `jsondiffpatch`. Both compute structured changes to a JSON document, one as RFC 6902 patches and one as diffs with merge support. For a project that edits a project file, having two is defensible if one handles patches and the other handles merges, and it is exactly the kind of pair a reader cannot distinguish from an incomplete migration without reading the code.

Other entries in the same spirit: two animation and utility packages, `tw-animate-css` and `class-variance-authority`, alongside `tailwind-merge` and `clsx`, which is the standard Tailwind helper quartet. And two Streamdown-adjacent Markdown engines, since `@streamdown/cjk` and the other three plugins are on top of `streamdown` itself rather than replacing it.

None of this is a defect. It is a snapshot of a project at version 0.1.0 where dependencies accumulate faster than the abstractions around them, and it is the kind of thing a reader auditing the codebase should expect to find rather than be surprised by.

Four scripts, no lint command and no typecheck command

The root manifest has four scripts.

json
  "scripts": {
    "dev": "pnpm --filter @pireel/studio-oss-shell dev",
    "build": "pnpm --filter @pireel/studio-oss-shell build",
    "preview": "pnpm --filter @pireel/studio-oss-shell build",
    "test": "vitest run"
  }
}

Development, build, preview and a single test command. TypeScript is a dev dependency, and there is no script that runs it. There is no lint script either, and no formatter configuration in the root manifest.

So the two checks a TypeScript project normally runs before merging are not reachable from the root. They may exist inside one of the workspace packages, but a contributor working at the root has nothing to invoke.

The top-level file list is correspondingly small: a gitignore, the licence, the third-party notices, two readmes in English and Simplified Chinese, `apps/`, `packages/`, the two pnpm files, the manifest and a TypeScript configuration. There is no documentation directory, no continuous integration configuration and no tests directory at the root, even though a test runner is configured.

Combined with a version of 0.1.0, a `private` marker and no GitHub releases, the picture is a very early snapshot: enough to run locally and extend, not yet the shape of a project with a published release process.

The third combination of editing modes is written in the future tense

Three ways to work are offered, and the third entry in the list carries a different grammatical mood from the first two.

Directly in the studio is a thing you can do now. With chat is a thing the hosted product does. With an AI agent is a thing the plugin enables. The fourth line of that list is any combination of the three, and it is qualified with the phrase as the project develops.

So the matrix is honest but incomplete in a specific way. Two of the three modes exist in some form, and the combinations between them do not.

The rest of the page describes what the output is for, and it is a conventional list of video work: talking-head videos with readable captions, short clips cut from longer recordings, product demos and tutorials, multi-source edits combining video, images, audio and graphics, and multiple versions for different platforms.

One item is worth pulling out because it names a mechanism rather than an outcome. Videos shaped with reusable editing skills and visual frames. Those two nouns are the same idea applied to editing: a skill is a saved procedure and a frame is a reusable visual treatment, which is what lets a second video inherit the look of the first without being edited by hand.

For an agent-driven tool, having named, reusable units is the difference between an agent that can repeat a result and one that has to rediscover it each time.

Editorial conclusion

pireel suits someone who wants to run a video editor locally, in a browser tab, with an agent able to drive it, and who is prepared to accept that the chat interface lives in the hosted product rather than in the repository. Two things to settle first. The split between the AGPL editor and the Apache-licensed agent plugin means the two halves you install together have different terms, and the plugin is a separate repository fetched with a single command. And the open-source edition is version 0.1.0 with no releases at all, four npm scripts and no lint or typecheck command, so you are depending on a very early snapshot. The dependency list is entirely client side, which is the strongest thing here: media processing happens in the tab.

Frequently asked questions

What does the open-source edition of pireel include?

Local editing. The page states that the open-source edition focuses on local editing, and that the complete hosted experience including built-in Chat and connected services is at pireel.com.

How do I connect an AI agent to pireel?

Install the public agent plugin with `npx skills add pireel/pireel-agent`, then ask your agent to set up Pireel. The connection guide at pireel.com lists the supported agents, which include Codex and Claude Code.

What licence does pireel use?

The editor repository is AGPL-3.0-only, and the separate agent plugin repository is licensed under Apache-2.0. The repository also carries a third-party notices file.

How do I run the pireel editor locally?

Clone the repository, run `corepack enable`, then `pnpm install` and `pnpm dev`, and open the URL printed in the terminal. The package manager is pinned to pnpm 9.12.0, which is why Corepack has to be enabled first.

Does pireel upload media anywhere?

The open-source edition focuses on local editing, and the dependency list is client side, including an ONNX runtime for the web and WebAssembly media and audio modules. Media processing runs in the browser rather than on a server.

Official sources

  1. Issues
  2. License: AGPL-3.0
  3. pireel/pireel on GitHub
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pireel-pireel.svg)](https://hysenlabs.com/projects/pireel-pireel)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pireel-pireel.svg)](https://hysenlabs.com/projects/pireel-pireel)

Was this useful?