Repository navigation
Releases
motlab 0.3.0
A player bar for full screen, notes you can move and resize, a phone layout for the viewer, Hermes Agent and Muse Code in setup, and two fixes: rendering as root, and WebM footage that came a frame late.
Install
npm install -g @motlab/cli
npx @motlab/cli setupTo update from 0.2.x:
npm install -g @motlab/cli@latest
motlab setup --updateThen run motlab restart if the viewer is running.
Added
- A player bar in full screen. A white card along the bottom with a scrub bar split into scenes, the notes' numbers above it, the time and scene on the left, previous, play and next in the middle and the exit button on the right. It stays hidden so it covers nothing, and comes up when the pointer is near the bottom edge, after Space or an arrow key, or with a tap near the bottom on a touch screen.
Fopens and closes full screen, and the arrows step a frame. - Move and resize a note's box. Open the note, then drag inside the box to move it or a corner or an edge to resize it. A point can be dragged too.
- Delete all done notes in one go, under the unfolded done notes.
- A phone layout. Held upright, the viewer is one column: the preview across the top, the toolbar, the timeline, then the notes, scenes and audio. Held sideways, the side panel starts closed. Menus open across the width, and the note card sits above the keyboard.
- Hermes Agent and Muse Code.
--skill hermesputs the skills in Hermes's own folder, and--skill musein~/.agents/skills, which Muse Code reads.
Fixed
- Rendering as root, in a container or on a VPS, failed at the first scene because Chrome refuses to start as root without
--no-sandbox. motlab now passes it when it runs as root, and only then. Thanks to @Rifkiend for #2. - Footage in WebM or MKV showed every third frame one frame late at 30 fps, because these containers store timestamps in whole milliseconds. Every frame is now right for VP9 in WebM and MP4 and for H.264 in MKV, MP4 and MOV, at 24 to 60 fps.
- In full screen, Space pressed the full-screen button again instead of playing.
Tested
On Windows 11: the test suite, the package packed and installed into a separate npm folder (setup for Hermes and Muse, the launcher, motlab update, a render of the example), the viewer in Chrome at desktop size, and a phone emulated in Chrome at 390, 360, 844 and 740 px wide. Rendering as root was checked on Ubuntu 24.04 by @Rifkiend and on a Linux VPS. Not tried: a real phone, Hermes and Muse loading the skills, and macOS.
The full list is in CHANGELOG.md.
motlab 0.2.2
Fixes for the npm install on macOS and Linux, scene transitions on machines without a GPU, and clearer messages from motlab doctor and the renderer.
Install
npm install -g @motlab/cli
npx @motlab/cli setupSetup installs the skills for Claude Code unless you name another agent: --skill agents for Codex, Cursor, OpenCode, GitHub Copilot, Gemini CLI, Amp and Windsurf, --skill antigravity for Antigravity, or several at once with commas. The README has the table.
To update from 0.2.0 or 0.2.1:
npm install -g @motlab/cli@latest
motlab setup --updateFixed
- Under nvm on macOS and Linux, setup thought npm's folder was off PATH and wrote an unneeded launcher. Only the folders npx adds in front of PATH are ignored now. Seven PATH cases are tested on Linux and Windows.
- A scene transition could fail with "transition fade: null" when Chrome lost its WebGL context, which happened on GPU-less Linux machines. The transition now builds a new context and draws the frame again.
- When mediabunny is not installed, as in a clone where
npm ciwas never run, the render says so and says where to runnpm ci, instead of "failed to fetch dynamically imported module". motlab doctorprints the full path to the Python requirements file, so the command works from an npm install.
Changed
- When Chrome is missing on Linux,
motlab doctorprints the commands that install Google Chrome on x64 Debian or Ubuntu. - The README lists the setup command for each agent.
Tested
On Windows 11 with nvm for Windows 2.0, and on a Linux VPS (Ubuntu, 2 cores, no GPU): install from npm, setup, doctor, a render of the example, and the test suite. CI runs the tests on Ubuntu and Windows. macOS has not been tried yet.
The full list is in CHANGELOG.md.
motlab 0.2.1
The npm install now works under nvm for Windows 2.0.
Fixed
- With nvm for Windows 2.0,
npm install -g @motlab/clileft no workingmotlabcommand, because nvm keeps npm's global folder off PATH. Setup now notices this and writes amotlablauncher to~/.local/bin, the same one the clone installer writes, and prints the line that adds that folder to PATH if it is missing. - Setup run from npx's cache without a global install stops and says to install first.
motlab doctorno longer reports mediabunny missing when npm puts it next to the engine folder.
Changed
- Setup runs as
npx @motlab/cli setup, which works before themotlabcommand is on PATH:
npm install -g @motlab/cli
npx @motlab/cli setupKnown problem
Under nvm on macOS and Linux, setup writes a launcher it does not need. 0.2.2 fixes this. Use 0.2.2.
The full list is in CHANGELOG.md.
motlab 0.2.0
motlab is on npm. The name motlab was already taken there by an unrelated package, so it is published as @motlab/cli in the npm organization motlab. The command is still motlab.
Install
npm install -g @motlab/cli
motlab setupmotlab setup is new: it copies the two skills to an agent's skill folder (Claude Code by default) and runs motlab doctor. It takes the installer's skill options, such as --skill agents or --skill antigravity. From an npm install, motlab update says which version is out and prints the npm commands that get it, and motlab uninstall points at npm uninstall -g @motlab/cli. Installing from a clone with node install.js works as before.
The package holds the engine, the skills, the example project and the docs (90 files, 943 kB). bench/, test/ and the README images stay in the repository.
Known problem
With nvm for Windows 2.0, npm's global folder is not on PATH, so motlab is not found after npm install -g. 0.2.1 fixes this. Use 0.2.2.
The full list is in CHANGELOG.md.
motlab 0.1.0
The first release of motlab: video as code, a review viewer, and two agent skills.
Every scene is a canvas page with one function, renderAt(t). motlab plays the pages in a web viewer and renders them to MP4 in headless Chrome, encoding the frames with WebCodecs inside the page. The motlab skill builds the scenes from your references and revises them from the notes you leave in the viewer; motlab-assets builds reusable asset kits (2D, rigged characters, transitions, 3D with PBR textures).
What is in it
motlab start,edit,stopandrestart: one viewer in the background on port 4173 for all your projects, with frame-by-frame review, notes on boxes, points and time ranges, versions, and Export at 720p to 4K.motlab render,stills,videoandeventson the command line.node install.jsinstalls the command and the skills for Claude Code, Codex, Cursor, OpenCode, Copilot, Gemini CLI, Amp, Windsurf and Antigravity;motlab updateandmotlab uninstallkeep it current or remove it.- A benchmark against Remotion and HyperFrames in
bench/. On the test laptop (Ryzen 7 5800H, RTX 3060 Laptop, Windows 11) motlab rendered the benchmark scene 2 to 4 times as fast with a GPU. Without one it was still the fastest at 1080p, and HyperFrames was faster at 4K.
Install
git clone https://github.com/staryone/motlab.git
cd motlab
node install.js
motlab doctorYou need Node 24 or newer, Google Chrome or Chromium, and ffmpeg with ffprobe.
What is not tested yet
motlab was built and measured on one Windows laptop. CI runs the tests, the end-to-end renders among them, on Linux and Windows runners without a GPU, but no real video has been made on Linux, and nothing has run on macOS. The full list is in ROADMAP.md, and everything that went into this release is in CHANGELOG.md.