Videohub README

The project's README from github.com/TensaikunYT/Videohub. As one markdown file: README.md.

VideoHub

A local review studio and render queue for videos that Claude Code or OpenCode writes as code. Ask your agent for a video. It builds a film as a web page that draws every frame in code. VideoHub plays the film straight from its code, so you can watch it, step through frames, draw and leave notes before rendering. Send the notes back to your agent, review the fixes in the reloading preview, then render when you are ready. The queue keeps the computer usable and can re-render only the seconds that changed.

Windows 10/11, Linux and macOS; Claude Code or OpenCode. Linux and macOS are new, not yet tested on real machines. See platform support for feature limits and the remaining hardware checks.

Live preview with a note on a frame

Features

Projects

Render protection and speed

Built into the Node server, with no compiled helper:

Renders

Requirements

All platforms need Node.js 22+, ffmpeg on PATH, a native Chrome/Chromium/Edge browser for headless rendering, and Claude Code or OpenCode for making and fixing films. No native modules or compiled render-protection helper are required.

Platform Install missing tools Notes
Windows 10/11 winget install -e --id OpenJS.NodeJS.LTS; winget install -e --id Gyan.FFmpeg Edge or Chrome; setup retains the existing Windows paths
Linux desktop Your distribution's Node 22+ package; sudo apt install ffmpeg, sudo dnf install ffmpeg, or sudo pacman -S ffmpeg Install a native browser; Snap/Flatpak browser wrappers are unsupported. Optional taskset, zenity/kdialog, notify-send
macOS With Homebrew: brew install node ffmpeg; brew install --cask google-chrome, or Chrome from its download page Chrome / Edge / Chromium in /Applications or ~/Applications; Apple Silicon and Intel code paths need hardware verification

A graphical desktop session is needed for windows, folder dialogs, desktop notifications and file-manager actions. A compatible graphics encoder is optional.

Install

Download the ZIP and unpack it, or clone the repository into a folder you want to keep. Open that folder in Claude Code or OpenCode and ask it to install VideoHub, or run the installer yourself. Setup asks about the workspace, discovered video folders, graphics encoding, agents, review rule, shortcut, login startup and example film. Re-runs keep existing answers, folders and settings.

Windows

Double-click SETUP.cmd. It runs the shared Node installer directly. Preview the steps with node scripts/install.mjs setup --dry-run; --yes accepts recommended answers. Examples: --workspace "D:/Videos/VideoHub" and --agents claude,opencode. The same answer flags shown below work on every platform.

The .ps1 setup/update/uninstall files are compatibility forwarders and respect PowerShell's existing policy. If that policy blocks one, use the Node command or .cmd entry point; no policy change is needed.

Open VideoHub from its Desktop shortcut or open.cmd. The shortcut starts the installed Node.js executable directly; a console window may appear briefly. open.cmd and login startup may also show a short console window. The current launch path uses neither VBScript nor hidden PowerShell. Update migrates owned shortcut/startup entries and recycles the old open.vbs / open.ps1 only when those references are safe; custom, unreadable or failed migrations retain the files and show a warning. Start a new session in your selected agent to load hub_* tools.

Linux and macOS

Run chmod +x setup.sh update.sh uninstall.sh open.sh, then ./setup.sh. Preview first with ./setup.sh --dry-run --agents opencode. Setup prints missing-system-tool instructions instead of silently installing system packages.

Flags: --yes, --workspace PATH, --agents claude,opencode, and --watch-found, --gpu-encoder, --global-rule, --shortcut, --startup, --example with yes or no. Launch with ./open.sh. Linux also installs an application desktop entry and can add a Desktop copy.

On macOS the optional Desktop launcher is VideoHub.command, which briefly opens Terminal. There is no unsigned .app bundle. If macOS blocks the downloaded launcher, attempt to open it, then go to System Settings → Privacy & Security → Open Anyway, confirm, and open it again. You can also launch with ./open.sh from the installed folder.

Claude Code and OpenCode

Setup detects the installed agents. Select one or both with --agents claude,opencode on every platform; legacy Windows -Agents spelling remains accepted. Each receives its own local MCP registration, the shared skill and the optional marked review rule. Restart the selected agent after setup.

OpenCode's rules live in ~/.config/opencode/AGENTS.md (under $XDG_CONFIG_HOME if set). When that file exists OpenCode reads it instead of Claude's global compatibility rules. Setup prints this consequence and never copies unrelated personal rules between agents. Settings → Agent name controls the review button label.

Your first film

  1. If setup added the example film, its card is on the Projects page. Otherwise the page shows Welcome to VideoHub with your workspace and films folder (<workspace>\films): click ▶ Add the example film.
  2. Click its card: it opens in the live preview. Press Space, step with ← →, click on the video to leave a note.
  3. Press 🎬 Render → Full film: the queue renders 5 two-second chunks and saves hello-film_v1.mp4 with sound.
  4. Leave a note on a frame, change film.js (e.g. a colour), then 🎬 Render → Only the fixed parts: only the touched chunks are rendered again → hello-film_v2.mp4, and Watch only the changes plays them. What a film folder must contain for each feature: docs/PROJECT-CONTRACT.md. New films start from templates/new-film.

Working with your agent

  1. Ask Claude Code or OpenCode for a video. It builds the film from the template.
  2. Preview — when it plays, the agent calls hub_live, opens the film in VideoHub and stops for your review.
  3. Notes — watch, leave notes, press Send to Claude / OpenCode and paste the message into your chat.
  4. Fix — the agent reads hub_notes, edits the code and marks the fixes. The preview updates itself; repeat as needed.
  5. Render — when you ask, the agent calls hub_render, or you press Render. Later fixes can render only the changed chunks; use Watch only the changes and Check fixes to review them.

If MCP tools are not loaded, the same tools work through node <VideoHub>/server/cli.js <tool> "<json>".

Optional integrations

Feature Needs Without it
Ready-made sound effects a 3D studio engine with engine/audio/synth.js (studioDir in Settings) your own sound folder and files from disk
Scene editor / 2D layers in the preview the page includes the hooks from engine-hooks/ those editors are hidden
Snipp export status Snipp writing .renders\*.json in a watched folder not shown
Settings → Optional parts on this computer shows what was found.

Security

VideoHub is a local tool. The server listens on 127.0.0.1 only and refuses requests with a foreign Host, cross-site requests from other web pages and writes with a foreign Origin. Its render queue can run shell commands for your projects, so never expose port 7788 (no port forwarding, no tunnels, no 0.0.0.0 proxies). It only serves files inside your watched folders, the archive and its own folders.

Windows launch and security warnings

Windows setup, update and uninstall use the shared Node lifecycle commands listed in the security guide. SETUP.cmd and UPDATE.cmd call Node directly. Normal launch uses open.cmd → Node → scripts/install.mjs open; new Desktop shortcuts and login startup also use the installed Node executable. None of these paths changes PowerShell's execution policy or adds a policy override. Windows integrations still use transparent commands and installed Windows/.NET libraries where needed: the picker loads WinForms, and Trash uses the installed Recycle Bin API. Nothing compiles inline C# or custom P/Invoke helpers.

See Windows security guidance for the current behavior, exact-alert evidence and upgrading an older distributed copy.

These changes simplify the launch and system-integration paths. They do not establish that a security alert is a false positive or guarantee that a vendor will accept every downloaded version. Record the security product, exact warning or detection ID, affected file and VideoHub version before deciding what needs review. node scripts/windows-security.mjs prints local source fingerprints and retired-helper presence without reading antivirus history or uploading anything; it is not an antivirus scan.

Warning type What to distinguish
Antivirus malware detection A named threat/detection for a file needs investigation of that exact file and verdict. Keep the blocked item blocked during review.
SmartScreen / unknown publisher / reputation warning Publisher identity and download reputation are separate from a named malware detection. The exact message identifies which check was involved.
Smart App Control block This is an application-control trust decision. It is not interchangeable with an antivirus detection or a script-policy error.
PowerShell scripts disabled / unsigned-script error This is a script-policy restriction. Use the direct Node lifecycle command instead of the optional .ps1 compatibility entry; no policy setting needs to change. Other application-control restrictions still need the computer's approved deployment process.

If an examined distributable still receives a malware detection, use that product vendor's official file-review process for the exact affected file. Review what the submission contains first; VideoHub does not upload files to scanners or vendors automatically. Disabling security protection, adding broad exclusions or bypassing download/script policies is not part of setup.

Update

Download the new version and unpack it separately. Windows: double-click UPDATE.cmd, or run node scripts/install.mjs update --target "C:/path/to/installed/VideoHub" --dry-run, then repeat without --dry-run. Linux/macOS: from the new copy run ./update.sh --target /path/to/installed/VideoHub --dry-run, then repeat without --dry-run.

The update backs up replaced code and keeps the workspace, settings, queue, films and notes. Use the existing launcher afterwards and restart your agent session. Downloaded or shared copies do not change automatically: distribute this version and explicitly update each installed copy that needs it.

Uninstall

Windows: from the installed folder run node scripts/install.mjs uninstall --dry-run, then repeat without --dry-run or use UNINSTALL.cmd. Linux/macOS: ./uninstall.sh --dry-run, then ./uninstall.sh from the installed folder.

Only integrations owned by this install are removed: MCP entry, skill, managed rule block, shortcut and login startup. Reversible removals use Trash / Recycle Bin. Films, notes, outputs, settings and the program folder remain.

Troubleshooting

Development

npm test runs the suites; see CLAUDE.md and docs/ARCHITECTURE.md.

License

MIT © 2026 VideoHub contributors.

Videohub (TensaikunYT/Videohub)

Searching Database…

What is this?A local review studio and render queue for videos that Claude Code or OpenCode write as code. You ask your agent for a video, it builds a film as a web page, and you preview, leave notes and render it on your own computer.
Is this a video editor, or something else?Not a traditional timeline editor. Each film is code: a web page that draws every frame. VideoHub previews it live, renders it to mp4, and you give feedback by leaving notes on frames that your agent then fixes in the code.
How do I get it running?Download the ZIP or clone the repository, then open the folder in Claude Code or OpenCode and ask it to install VideoHub. Or run SETUP.cmd on Windows, or ./setup.sh on Linux and macOS. Launch it with the Desktop shortcut or open.cmd / ./open.sh.
Do I need Node.js or ffmpeg first?Yes. You need Node.js 22+, ffmpeg on PATH, a native Chrome, Chromium or Edge browser for headless rendering, and Claude Code or OpenCode to make and fix films. No native modules are required.
Does it work on Linux and macOS as well as Windows?Windows 10/11 is the main tested platform. Linux and macOS are new and not yet tested on real machines. On macOS the render power and slow CPU sliders are hidden, because there is no supported CPU-core affinity API.
Can the hardware encoder speed up my renders?Yes, if your graphics card supports it: NVENC, AMF or QSV on Windows, NVENC, VAAPI or QSV on Linux, VideoToolbox on macOS. A short probe checks what works with your installed ffmpeg. x264 runs on the processor as a fallback.
What does a film look like under the hood?It is a web page exposing window.renderOut(t), which draws the frame at time t. The live preview and the final mp4 come from the same code, so the preview is frame-accurate.
How do I give feedback on one specific frame?Click or draw on any frame, or pick a frame range, and type what is wrong. Your agent then gets the time, frame, chunk and a close-up picture of your drawing through hubnotes.
What happens when the render queue runs low on RAM?When available RAM crosses a threshold the newest render slows down, and at critical RAM every render slows down. You can also slow, normalize or stop renders, and VideoHub never closes other programs that hold RAM.
Can I work with sound in the film?Yes. You can mute, solo or set levels per stem, remove the music, duck it under a range, and add sounds from your library or disk on the timeline. Renders use the rebuilt mix.
Size
2.3 MB
Stars
526
Age
7d
Commits · 90 Days