Kinocut
Guarded local video editing for agents, with a CLI, Python client and MCP server. Kinocut uses FFmpeg and ffprobe for media inspection, editing, subtitles, audio and quality checks. Optional workflows include Hyperframes, Revideo and model-assisted analysis.
Install and inspect
Requires Python 3.11 or newer, plus FFmpeg and ffprobe on PATH.
pip install kinocut
kino doctor
kino info input.mp4
Agent plugins launch a specific published version through uv. Follow the
plugin instructions
for the host you use. Kinocut also provides from kinocut import Client; the
older mcp_video import remains supported.
Output safety
Prefer new output paths. Replacing an existing output requires explicit
overwrite=true (CLI --overwrite). Existing non-media artifacts also require
evidence that the same durable job created them. Agent configuration homes are
protected. Use one writer per output, check the result, and require human
visual/audio review before publishing.
Optional model calls and network use
Ordinary local FFmpeg editing and color grading need no account, model SDK or
API key. Kinocut's optional vision calls default to KINOCUT_VISION_MODE=off.
For observations with your chosen provider, prepare local images through
Kinocut and inspect them with the host agent's image tools, including local
models. Kinocut does not automatically inherit the host's model configuration.
Kinocut's own optional product-description adapter requires an Anthropic-compatible endpoint and explicit local or remote configuration. The separate sampled-frame Anthropic QC path also requires explicit remote permission and configuration. A local/custom product route cannot activate it.
Installing packages downloads dependencies. URL inputs download requested media;
font and model-weight features may fetch assets from GitHub. Explicit Revideo
installation runs npm ci and may download renderer/browser dependencies.
Revideo telemetry defaults off. Hyperframes is a separately installed CLI:
Kinocut sets telemetry opt-outs, skips passive update checks and disables
implicit capture/snapshot model analysis. Docker rendering and browser previews
without a verified opt-out require explicit telemetry consent.
These controls are not a network sandbox. Inspect executable scenes and project assets before use. See the vision and network policy for configuration, supported preview versions and limits.
Metadata
Release files for kinocut 1.16.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| kinocut-1.16.4.tar.gz | 1.5 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinocut-1.16.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 MB
Release files / kinocut-1.16.4.tar.gz
| Download URL | kinocut-1.16.4.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2424a9a148f5f0046ed29d9db98f10961b97fda102aac0d85c36812fe14777a
|
|
BLAKE2b-256 checksum How to use checksums |
a5928964e923d78dc1d0cdc5dbb338aba509c3a2ce9ad66564d30d6029510d8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / kinocut-1.16.4-py3-none-any.whl
| Download URL | kinocut-1.16.4-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93674b38d1e616a1d69714fbb99f10b2d339f69df7ba796f54690afd83d2c189
|
|
BLAKE2b-256 checksum How to use checksums |
109b9f3b3e0c7a9c776dcbb178a5b8b72c3cce725d07e5f81536ba61a96a3903
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for kinocut 1.16.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for kinocut-1.16.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.