Changelog
All notable changes to this project are documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning. Until 1.0.0, the document format and the APIs may still change between minor versions.
- Blocks of the script: the prompter’s Blocks tab gives each sentence of the script what to show over it (empty: the camera);
/blocksbuilds them where each sentence is said, and proposes an idea for the empty ones first. - A film from a voice:
/from-voicemakes a film from a voice recording alone: transcribed, cleaned, cut, planned on its words, built, given its music and effects. - My style: “Keep as my style” in the direction keeps the project’s palette, typefaces, tone and rules (in the account when signed in, on the device otherwise); the home screen then offers it, and the assistant follows it from the first turn.
- The prompter: in the studio’s bar and the atelier’s timeline, the script written or pasted (kept with the project), then said to the camera while it scrolls at the pace chosen, after a count-in; the recording joins the project and the assistant’s box is ready to keep its takes.
- The takes chosen against the script: the
takestool (and the assistant, asked to) reads a talking video against its script, sentence by sentence: the last good take of each one is kept in the order of the script, the false starts, repeats and words off the script are cut, and the sentences never said are named. The script is kept with the project. - Export for Premiere Pro: “For Premiere Pro” in the export panel (on the server, and in the cloud with an account), or
tramme premiere <project>: a zip with the timeline (Final Cut 7 XML, File > Import in Premiere), the footage and sounds with their cuts, offsets and levels (voices, music and effects on their own tracks), what is drawn under and over the footage as clips with alpha per scene (ProRes 4444), the captions as subtitles (SRT). After Effects imports the same clips. - Export on the server, in local:
pnpm rendererstarts the renderer on this machine, and the export panel ofpnpm devoffers “Export on the server”, rendered as the desktop app renders it. - Told when an export on the server is over: a notification of the system (browser, desktop, phone) when the app is in the background, a message in it otherwise, followed from any page and after a reload; with an account, a mail too, with the way back to the project.
- Several commands in one message: a
/commandcan be written anywhere in a message (at its start or after a space), as many as needed; the assistant gets each of them, in the order written. One tool alone at the start keeps its form and runs at once, as before.
Changed
Section titled “Changed”- In the message boxes (the assistant, the studio, the home screen), the commands and tags the project knows are marked where they are written: a
/commandin the accent, an@tagin another colour; an unknown one stays plain words.
- On the home screen, a file’s tag replaced the letters “s” of its name instead of its spaces.
0.28.0 - 2026-11-16
Section titled “0.28.0 - 2026-11-16”- Pins moved by hand: in the studio, a pin of the note being written or of a retouch in the list is dragged by its number to another place of the picture; a path or an area moves whole and stays in the frame, and what it points at follows (the layer under a point or a path’s start, the layers a selection takes in).
Changed
Section titled “Changed”- The assistant’s work in progress (what it does, its stages, its last steps, pause and stop) sits at the bottom of the conversation and stays in sight while you scroll; the takes and the pictures it looked at stay above it.
- The watermark is in the top left corner of exported films, and anyone can turn it off in Settings, Behavior, until accounts are open to all.
app.tramme.devis the deployment with accounts, deployed by the platform whenmainmoves; the personal environment’s addresses inapps/worker/wrangler.jsoncare an example to replace with your own domain’s.
- On a project with more pictures than the memory keeps, the storyboard, the preview, the home screen’s picture and the exports of an isolated project drew a frame without some of its pictures, and the storyboard showed the engine’s error over the film. The pictures a frame shows are loaded before it is drawn; a storyboard frame that cannot be drawn keeps its last picture.
- While the preview was loading, the picture showed “Isolated selection could not be calculated: preview is not ready”: the panels that read the layers through it now wait for it, and adding a mask or drawing an area at that moment says to try again in a moment.
- The image of the export in the cloud failed to build: the build’s own
node_moduleswere copied into it (.dockerignore).
0.27.0 - 2026-11-15
Section titled “0.27.0 - 2026-11-15”- Projects in your account: on a deployment with accounts, signing in keeps your projects, libraries, conversations and provider keys in your account, the same in every browser you sign in from; signed out, they stay in the browser as before. The keys are kept sealed, and deleting the account deletes its files.
- After signing in, the projects made in this browser before can be brought into the account (offered once, and in your space); the copies in the browser stay.
- A save that cannot go through waits instead of failing: when the project was saved from another tab or device since it was opened, you choose which version stays; when your session ended, you sign in again and the changes are saved.
- Your account’s button in the project’s top bar; the project is saved before you leave it for your space or sign out.
- The gallery: a film you just exported as MP4 is published from the export’s panel, with a still taken in its middle, a title and a few words, in the gallery or reachable by its link only, and the project offered for copying or not. It is signed with your public name, which you choose in your space. “Open in Tramme” on the site copies a published film’s project into your projects (its code is asked about first, as any project from someone else). Visitors can report a film.
- Export in the cloud: signed in, “Export in the cloud” in the export’s panel renders the project on a server as the desktop app renders it (
apps/renderer, the command line with Chrome and ffmpeg, in a container); the page can be closed, and the film lands in the project’s renders, to download. The jobs wait in a queue, one render at a time. - Export by API and command line: API tokens of the account, made and revoked in your space (shown once, only their hash kept), let
tramme cloud-export <project>send a project to your account, have it rendered in the cloud and bring its film back. A token reaches the projects and their exports only. - The plugins’ marketplace: on a deployment with accounts, the plugins settings have a “Discover” section: plugins published by their authors, installed through the same question as an import, their package checked against the catalogue’s hash, newer versions offered. An installed plugin is published from its row under its author’s public name; a plugin that reaches the network or keys is listed once the back-office has reviewed it. A plugin can be reported; a revoked version is turned off at the next check, and you are told which.
- The back-office (
/admin), for the people who run Tramme: find an account by its address, name or public name, see its plan, end its sessions, give it a plan until a day or put it back on Basic, close it with its projects and films; read the gallery’s reports, take a film down, put it back, set the reports aside. - The desktop and Android apps signed in: your account’s projects are listed beside the ones of the device’s folder, marked “in your account”, and open and save in the account, their pictures, sounds and videos read in parts. The projects of the device are brought into the account from your space, through their archive; the copies on the device stay.
Changed
Section titled “Changed”- The site hides the prices until the payment opens: no pricing page or link to it, no price or credit question in the FAQ, no paid sections in the terms, no offers given to search engines; the app’s space shows no offers either. One switch brings them back, on the site and in the app (
PAYMENT_OPENinpackages/plans).
Removed
Section titled “Removed”- The deployment of the server mode on Cloudflare behind Cloudflare Access (
pnpm deploy, its bucket and its documentation): the server mode ispnpm dev’s, on this machine. The public deployment is the personal mode (pnpm deploy:personal), and the deployments with accounts take its place for the projects kept on a server.
0.26.1 - 2026-11-15
Section titled “0.26.1 - 2026-11-15”- The companion’s npm package is
@qualris/tramme: npm refused the nametramme, so thenpx trammethat 0.26.0 shows started nothing. Start it withnpx @qualris/tramme, or install it once withnpm install -g @qualris/trammeand start it withtramme; the editor shows the new command. - The assistant’s panel said to start the companion “in the Tramme folder”: it now says to start it in a terminal, with Node.js 20 or later, and the messages that ask to start it give the command.
0.26.0 - 2026-11-15
Section titled “0.26.0 - 2026-11-15”- The local companion on npm:
npx trammestarts it on any computer with Node.js 20 or later, with no repository to clone. It pairs by itself with the Tramme app and the desktop app (--originadds another address), and the assistant’s panel shows the command to type. The first transcription installs the local speech recognition once (about 150 MB, in~/.tramme/whisper). In the repository,pnpm tramme agentruns the same companion.
- No terminal window flashing on Windows while the assistant works or lists its models: the Antigravity CLI started its own update in the background, at most every 15 minutes, and that update opened a window. The companion now runs Antigravity with its auto-update off.
- The Android app is in the release again: the stable app’s build stopped on an empty configuration (“EOF while parsing”), so the release carried no
tramme-android.apk. It builds again, and the site offers it.
0.25.0 - 2026-11-14
Section titled “0.25.0 - 2026-11-14”- The Tramme watermark: exported films (MP4, WebM, GIF, PNG, 10 bits) carry the Tramme mark, all white, in the bottom right corner; every 12 s the whole logo opens from it, stays for a few seconds and closes back. It is always there on Basic and without an account; on Plus and Pro it is on by default and a switch in Settings, Behavior turns it off. The first export that carries it says so. The command line’s renders and stills carry it too.
- Talking videos dressed on the words: before the first insert, the assistant sets one graphic charter for the whole video (a plate, an accent and a backdrop taken from the colours of the room, the grain over it), then reads the moments of what is said (the figures, comparisons, lists, names, questions and new parts, each with the moment its words are said) and builds full-frame inserts that replace the face and tell a small story on those words. Section titles can be written with the voice, each word appearing as it is said. The check now names a keyword that appears after its word is said, an insert that holds still for 2.5 s while the voice goes on, and two inserts in a row built the same way; the review does not pass a talking video until they are fixed, and holds it to 3 s of stillness instead of 4.
- A voice-over from words, next to the microphone in the timeline: type what to say, pick one of five voices chosen to differ (warm, deep narrator, lively, soft, clear), each heard on a sample sentence in your language (made once, kept in the sound library), and the take lands on a new voice track at the playhead, the music ducked under it and the voice cleanup on it, in one undo. The whole library stays one click away, and the five voices offered are a list you edit in the Sound settings.
- Smooth slow motion with RIFE: in the Models settings, the slow motion can make its frames with RIFE, a network that learned how things move between two frames (21.6 MB, MIT), instead of the built-in block matching. It runs in the browser, on the graphics card, and goes on on the processor if the card stops. The frames are made at the film’s size (a 4K clip in a 1080p film at 1080p), and in overlapping tiles above 1080p.
- Menus and panels that grow after they open (a list arriving) are placed again, so they never run off the screen.
- Remake a reference (
/remake): give a video, a gif or a Lottie you like, add your logo, screens, footage and words, and the assistant makes the same video around them. It reads how the reference is made (its shots cut to the frame, its music, the places where content sits, its moves, its transitions, its colours and its type, the camera measured on its pixels), shows you that reading scene by scene to correct (an asset to choose for each place, a scene to remove or merge), then plans the film on it, timed on your own music when you give one. The review checks the film against the reference: the scenes, their lengths, the cuts on the beats, the places filled, and never a word, a logo or a picture of the reference. A setting goes on without showing the reading first.
0.24.0 - 2026-11-13
Section titled “0.24.0 - 2026-11-13”- Colour grading as a colourist’s tools do it, in a new Colour category of effects:
- Colour grading (
fx.grade) develops a clip: a camera’s log (Sony S-Log3, Panasonic V-Log, ARRI LogC3, Apple Log, Canon Log 3, HLG) read into scene light with its gamut, then brought to the screen with its hues kept: colours outside the screen’s range pulled in instead of turning cyan, highlights rolling off toward white instead of clipping; white balance (temperature, tint); exposure in stops; contrast, highlights, shadows, whites and blacks, masked by the brightness around each pixel so a window does not halo the wall beside it; texture, clarity and dehaze; vibrance that spares the skin, and saturation; colour wheels over the shadows, mid tones and highlights, and a global one, with their balance and blending; a fade. - HSL (
fx.hsl) moves each of eight colours alone (hue, saturation, luminance), the greys untouched. - Hue curves (
fx.huecurves): hue against hue, saturation and luminance, saturation by luminance and by saturation, edited on a curve with the hues along its foot. - Colour isolation (
fx.secondary) picks a colour with the dropper (a sky, a skin, a shirt), softens its matte, and corrects it alone, or everything but it; its matte can be viewed. - Film look (
fx.film: halation, bloom, grain in the mid tones) and a Vignette for a clip (fx.vignette). - Eight colour looks, ready-made grades put on the selected clips in one tap (Natural pop, Teal and orange, Warm film, Golden hour, Cool night, Bleach bypass, Faded matte, Black and white); on a phone they are tiles of the Effects tab.
- The scopes add the RGB parade and the histogram beside the waveform (the one chosen is remembered), and show for every effect of the Colour category.
- Colour grading (
- The assistant knows when to use each grading effect, and reads a camera’s log through
fx.gradeinstead of a conversion LUT. - The anime example is a new film, Paper Wings: a paper plane at sunset in four shots, drawn frame by frame (clouds lit from the side, the plane banking, telephone wires, a town with its windows lit), animated with sequences, parallax and a camera push.
- A proof of the assistant’s work: one message turned a NASA raw take of 60 s into a 48 s film (cuts, captions, keywords, pictures over the talk, a title, sound) in 12.7 minutes, shown first, with its sound.
- A second proof of the assistant’s work: one message turned five minutes of a NASA talk into three vertical shorts (42, 21 and 33 s), each framed on the speaker, captioned word by word, opening on a hook, in 42 minutes for $1.04; the clip plays the start of each in turn.
- Seven more proofs on real footage: a label that follows a car (tracking), a 16:9 walk made vertical with the frame on the man (reframe), a leap at a quarter speed with the frames between made by Tramme (slow motion), a portrait’s skin smoothed at 100 % (retouch), a 640 × 480 photo enlarged by Real-ESRGAN (upscaling), two shots of one bridge by two cameras given one look (matching), and the pauses of a live answer cut (silences, 60 s to 55.4 s).
- The landing page shows three of the proofs, each opening its comparison on the features page.
- The features page shows features on real footage, before and after (Before and after): a line dragged between the two pictures, the clip, where the tool is in the app and the footage’s credit. The first are colour grading on an ungraded Apple Log clip, keying on a green-screen take, a photo in 2.5D a title passing behind a person filmed without a green screen (all from Pexels), and a voice cleaned of a street’s noise, 15 dB lower, played before or after at the same instant (from Wikimedia Commons), and word-by-word captions on a NASA interview.
Changed
Section titled “Changed”-
The landing shows an editor at work: in Features, an edit playing on real footage (a viewer cutting to the shot under a playhead, a title and a grade clip over it, a click moves the playhead); each Animation card shows its idea moving (a key easing along its curve, a wiggle, a loop and a spring, a layer following another, a palette the shapes follow); one selection going through the toolbox, tool after tool; Export plays a shot beside its formats, each holding its frame (the vector ones drawn, Lottie moving); the platform shows one project on a computer and a phone. Everything plays only on screen, stands still with reduced motion, and loads only as it comes near: a video’s poster now waits too.
-
Online (personal mode), the providers in the settings sit on the dialog’s own background: the key vault’s page drew a grey slab of its own over the glass themes’ translucent dialog (the theme’s wallpaper, then an opaque fill meant to hide it), where the editor run locally draws them itself.
-
A proof’s line shows one picture on each side, up to the frame’s rounded edge: the before was whole under the after, and its colour bled through the smoothed edge (a thin green line around the keyed take).
-
The 2.5D proof compares the photo flat and in relief at one framing (the same scale, the parallax taken off the before) from a source twice as wide, so its picture is as sharp as the photo: the after was the photo enlarged by a third beside the whole photo, and read as softer.
-
A photo in 2.5D takes no depth of field by default: a blurred background read as a softer picture, not as depth (fx.depthBlur stays at hand). The depth parallax leaves the photo as it is at rest: a pan moves the near more than the far, a push in grows the near by as much as it zooms, and nothing shrinks the far. It used to grow the near around the middle even when the camera only panned (a rock at the frame’s edge, pushed 120 px off the water, left its outline echoed over it), and to shrink the far past the frame’s edge (a mountain mirrored into the sky).
-
Matching the look of a shot matches a camera’s cast whole and its brightness and contrast only so far (0.1 and ×0.8 to ×1.25), black kept within 0.05: two angles of one scene show different things, and matching their spread whole lifted and tinted the blacks of the darker one (a tree against the sky turned olive).
-
A layer’s GLSL effects in a row run as one chain on the GPU: the layer is uploaded once and the effects hand their result to each other in half floats, so a grade, curves and a LUT stacked lose nothing between them; the result is dithered as it goes back to 8 bits, so a pushed sky no longer bands.
-
A large effect’s settings are folded into groups in the inspector (a grade’s light, its presence, its colour wheels…), and an effect has a button that puts it back at rest. A curve’s square double-clicked goes back to rest too.
-
LUT, Curves, Colour wheels and Colour correction sit in the Colour category, and the menu that adds an effect is in sections by category.
-
On a phone, the colour wheels and curves are larger, for a finger.
-
The chroma key reads a green or blue screen by colour difference: hair and motion blur come out half transparent, and the screen’s colour is taken out of those edges, which keep the subject’s own colour.
-
The closing section of the site’s pages stays centred: its title and line were styled by a bare h2 and p, which weigh as much as the global reset, and whichever loaded last won.
-
Matching the look of a clip just added reads its picture once the preview has loaded it: run at once, it said “the picture cannot be read yet”.
-
The first frame of a render waits up to 2 minutes for its videos, the others 20 s: two render pages opening a 4K source of 170 MB at once stopped on “frame 0 never finished”. A segments’ folder Windows still holds no longer hides the render’s own error.
-
A long tool call made through the companion stays open while the editor is at work on it: transcribing a 5-minute video took more than the 15 minutes the companion waited, and the assistant got “the editor did not answer”. The editor now says every minute that the tool is still running; the 15 minutes count from its last word.
-
The command line’s picture checks measure text closer to how it is drawn: capitals, a heavy weight and the tracking make it wider, narrow letters and spaces thinner. A keyword in black capitals running to the frame’s edges passed the safe-zone check; a title in lower case was flagged when it fitted.
-
A photo in 2.5D moves in depth as the camera pans: the parallax follows the camera’s pan (it followed only its zoom, so a sideways drift slid the whole photo in one piece), the near shifting more than the far. A depth pushed past the picture’s edge shows the picture mirrored instead of a smeared edge, the photo is framed for the drift as well as for its relief, and its depth of field keeps the near subject sharp with a light blur far away (it blurred everything but the middle depth).
-
Footage holds its own frame across the motion blur’s shutter: with the composition’s motion blur on (the editor’s default), a filmed clip blended two of its frames where the shutter straddled them, which doubled a face and showed a title through a cut-out subject.
-
The French interface writes 2,5D with a decimal comma.
-
Cut the silences takes the pauses out: it removed only 0.24 s from the middle of each, whatever its length; it hears where the voice is in the sound (the voice detector the hesitations use), since a transcript’s word timings stretch over the pauses and hid most of them, so it no longer needs a transcription first; and it works on a clip that shows part of its file, where it made an invalid document.
-
The editor no longer stops saving after one of its own saves met another: a save asked (Ctrl+S, a version, leaving for the home) while the automatic one was on its way was refused as a change made elsewhere, and the saving stopped for the rest of the session, every later change lost. The saves now go one after the other, each naming the version the last one made.
-
A nested composition is heard: the sounds of the videos and sounds inside it play in the film that holds it, in the preview and the exports, at its time, speed and loop (they were silent).
-
A long film renders again in the editor and from the command line: its document, a few hundred thousand values well under 64 MB, was refused by the plugins’ sandbox as too large (the launch film among the examples).
0.23.0 - 2026-11-12
Section titled “0.23.0 - 2026-11-12”- Tramme on Android: the desktop app’s crate also builds as an Android app (
.apkoffered by the site,.aabfor the Play Store), built and signed on CI only. The editor runs in local mode with the projects and the keys on the phone (the keys under the Android Keystore), imports from the gallery, exports a long video to a file instead of memory, then saves it to the gallery or the downloads or shares it; the back button closes, goes back, then leaves. It sells nothing and shows no update notice. remove-bgcuts a whole set of pictures out in one call (images), each saved as its own asset.- The assistant’s
write_filechanges a passage of a file (find) instead of writing a long plugin whole again. - A plugin’s tool reads the project’s pictures, sounds and fonts with
ctx.readFile(path), through the editor: in the desktop app its sandbox could not fetch them (Origyn: a plugin written five times over). - A film plan written again takes only what changes (
changefor some scenes, by name); the rest of the plan is kept. node bench/run.ts <brief>runs a brief of the bench alone on the trial server, through the companion, and stops the turn once its cost passes a cap; three short briefs join the bench (a logo sting, a short data film, vertical kinetic type).- The critic measures the film’s rhythm on its rendered frames: a stretch of 4 s or more where nothing moves, or a film standing still more than half its time, is a defect it never lets pass; how much of the frame the subject fills and how many different pictures the film shows are given to it to weigh. The bench records the same measures for each run (
--picturespicks the picture provider of a run), and a brief that dresses a filmed talking-head video joins it, its footage kept on the machine. - The Windows installer has its own icon: the app’s tile rising from an open box.
Changed
Section titled “Changed”- The critic is harsh: it scores idea, composition, scale, material, rhythm, motion and finish, and a film is done only when every one reaches 8. It no longer takes a small subject in an empty frame, a long hold or flat plates for a choice of style, and it judges a dressed video on what its inserts show and how often the picture changes.
- The assistant’s guide holds what makes a film look made in any style (one visual idea that comes back, a dominant element that uses the frame, scale changing from shot to shot, something new every 2 to 4 s), and how a talking video is edited like the big channels (inserts that show what is said, in varied forms, the speaker’s framing changing, a look taken from the room).
- Claude works at the Medium effort by default instead of High: on the bench, with the changes below, four films of different kinds cost 62 % less and came out at least as good. A level chosen for a model stays as it is.
- The assistant costs less per film, for the same work:
- its system prompt no longer changes with the project: the brief, the film plan and the installed plugins travel with the message, again only when they changed, so writing a brief or a plan no longer throws the conversation out of the cache;
- the guides only some work needs (a video where someone speaks, shorts, sources, clips, node plugins, stock, sequences, tracking…) are read on demand, and the system prompt that every request reads is a third shorter;
- the inputs of the tools the instructions name ride in the cached prompt, so the model no longer fetches their schemas mid-turn;
- the vocabulary’s full entries leave out what only the interface uses (a field’s panel group, its slider step, a label repeating its name);
- a scene built apart is no longer sent to read the whole film plan, its own beats being in its message;
- a proposal’s answer carries the quality checks of its composition, so the contact sheet is asked for once a scene is built rather than after every proposal;
- a tool’s input with a plain slip (an object where a text is wanted, a single value where a list is, a number written as text, an option in another case, a number past its bound) is read and told, not refused;
- a portrait still, contact sheet or motion strip is sized by its longest side, like a landscape one, instead of being three times heavier.
- The dependencies are on their latest stable versions, Preact 11 among them. The command boxes are plain text boxes to screen readers, as HTML allows a text area to be, no longer comboboxes.
- The repository works with pnpm instead of npm (
pnpm install,pnpm dev,pnpm test;corepack enablegives the version package.json names): each package declares what it imports, only the dependencies the project needs run install scripts, and no version younger than a day is taken.
- Style frames and pictures made by Gemini work again: the picture model is now read from Google’s list instead of a name that no longer existed, which made every style frame fail.
- The style frames and the end of a scene find a scene by its name or a word only it holds, not only by its exact id.
- A turn stopped half way keeps the line of what it spent.
- A plugin’s check with the name of one of its tools runs (the stick figure’s pose check said it was “a tool, called as a check” in every review).
- A film’s music made by ElevenLabs is no longer refused when its prompt is long, nor for being asked as instrumental beside its plan.
- The site offers the build that has just come out: it read GitHub’s list of releases, which can still show the one before for a minute.
Security
Section titled “Security”- The desktop app writes its archives with zip 9, past four advisories of the zip crate (RUSTSEC-2026-0367, -0368, -0369, -0429).
- No dependency carries a known vulnerability: undici and Puppeteer are raised under the web scenes’ engine, which stays on its pinned version.
0.22.0 - 2026-11-10
Section titled “0.22.0 - 2026-11-10”- Audience measurement with Google Analytics, opt-in and counted only on the production addresses. The site asks once, with a “no” as easy as the “yes”, and nothing of Google’s is loaded before the yes; a “Visit statistics” button in the footer changes the choice. The web app and the desktop app have it as a setting (Settings, About), off until turned on, with no banner. The desktop app sends its events itself (it needs
TRAMME_GA_API_SECRETat build time). - Two settings for what the assistant waits on while it edits: “Let the assistant transcribe without asking” and “Let the assistant fetch real logos and people without asking” (Settings, Behavior). Off, a turn left alone still does without; on, the licence record says the settings allowed it.
- In the desktop app, a download button lights up in the home page’s top bar, with a dot, as soon as a newer version is found; it leads to the installer of the system. The look for a new version, made at the start, is now repeated every half hour while the app stays open (it still only asks the server every twelve hours).
Changed
Section titled “Changed”- Qualris is the publisher of Tramme: the footer, the About and Privacy pages, the structured data, the licence notices and the installers name it, and link to qualris.com in a new tab. The footer line is now just “© 2026 Qualris”.
- The privacy page describes the audience measurement and says who to write to (hello@qualris.com).
- The setting that checks for a new version says it asks the server, not GitHub.
- While the assistant makes a first film, its message in the empty frame sits on a card you can read on any film, and the status pill above the film no longer touches it.
0.21.0 - 2026-11-09
Section titled “0.21.0 - 2026-11-09”- The isolated asset loader never imports a module into the trusted page; CLI Free code layers now load and initialize their modules inside the opaque worker.
- CLI stills and raster exports now route expression-only projects through the opaque sandbox, including nested instance expressions.
- All five web-scene prototypes now carry
scene.json; the CLI composite produces a project that packs and unpacks with its font licence. websceneis now a built-in node; the six-frame CLI composition prototype no longer needs a project plugin.- Isolated video assets now refuse oversized frame dimensions and release replaced decoders.
- Isolated projects now refuse an asset inventory above 4,096 entries before loading files.
- Isolated projects now cap retained decoded images at 256 MiB and release replaced image bitmaps.
- Isolated image assets now have a 32 MiB compressed-file limit before browser decoding.
- Isolated font, JSON and LUT asset loads now stop at bounded response sizes and cancel oversized streams.
- The CLI project server now confines static files to their mount and refuses project configuration that overrides
/project/. - Web scenes now share an absolute-time
window.__hfruntime with browser-tested CSS, WAAPI, SVG, GSAP, Lottie and Three.js seek adapters. - Web scenes now have a validated
scene.jsonmanifest, published JSON Schema, approved project paths and archive round-trip coverage. - CLI scene checks now name nondeterministic browser APIs by file and line, and project packing refuses those scenes.
- Isolated model rendering now receives bounded, approved
.glbbytes through the host instead of fetching from the sandbox worker. - CLI plugin exports now load declarations before creating the renderer, keeping project modules out of the trusted browser page and removing its
sandbox=0escape. - The isolated renderer now refuses assets and video proxies outside the current project folder before loading them.
- Asset loading now runs at most eight requests concurrently and refuses oversized isolated images before bitmap creation.
- Sandbox messages now budget decoded bitmap surfaces separately and preserve the page’s copy of document images.
- Isolation checks now exercise project code at module import and additional browser network APIs in Chrome and Edge, before any tool or drawing call.
- Failed plugin attachments can be retried after repair, and storyboard stills report sandbox attachment errors.
- Sandbox capability replies now reject oversized data before it crosses the worker bridge.
- Page-to-sandbox calls and document snapshots now have a 64 MiB plain-data budget.
- A repeatable web-scene prototype now measures iframe preview against alpha PNG capture for GSAP, CSS/SVG with a custom font, and Three.js.
- The web-scene prototype can now capture a folder and composite its transparent frames as a Tramme plugin layer in a CLI export.
- The web-scene prototype now has a seekable iframe preview with a time slider and measured parity against captured frames.
- Web-scene development will use the pinned low-level HyperFrames engine for CLI and desktop, with documented preview differences.
- The isolated renderer now keeps at most two reusable full-frame canvases after a frame, releasing excess surfaces instead of retaining them in memory.
- Sandbox renders now refuse invalid sizes or a canvas side above the editor’s 8,192-pixel project limit before allocating the frame.
- Project extensions now run tools and checks in separate isolated workers per plugin. One extension cannot use another extension’s active call to borrow its network grant; updating a plugin replaces its worker.
- An approved plugin network request now stops reading a response above 64 MB instead of buffering it without a limit.
- The project host now stops reading an oversized plugin module or font as soon as its byte limit is crossed, even when the server keeps sending data.
- The isolated project worker now coalesces document updates during startup and stops if more than 128 messages queue; a project host also refuses more than 64 distinct plugin modules.
- The experimental sandbox preview option now also selects isolated picture rendering for stills and raster exports of projects that contain expressions but no plugins.
- The sandbox host now stops a project extension that returns more than 8 MB of nested plain data in one result, before passing that result into the editor.
- Malformed sandbox declarations and draw results now stop the isolated worker and report an invalid response instead of breaking the editor page.
- Project tools and checks now have at most 16 simultaneous requests to the host; repeated request IDs cannot repeat a project file operation.
- Restoring an installed-plugin backup now refuses a file over 64 MB or entries declaring more than 128 MB expanded in total before decompressing them.
- The project sandbox now refuses a 65th simultaneous call and project plugin modules larger than 1 MB before transferring them to its worker.
- The plugin host now rejects unknown bridge requests, project path escapes and malformed or oversized file/network requests before calling the editor’s capabilities.
- A project extension that hangs during load, checks, tools, rendering or vector export now stops after a deadline. The isolated frame is released and the next attempt starts a new one.
- Sandboxed plugin drawing now receives project font bytes from the trusted host, in document order, and waits for the face to load before drawing. A font URL outside the project is refused before any request.
- CLI archive and folder validation now obtains plugin declarations from an opaque browser worker; project modules no longer initialize inside Node. A looping module is stopped after a deadline, and Node-only plugin behavior fails closed until its browser bridge is available.
- Plugin workers now start inside an opaque-origin iframe with a network-denying policy in the web editor, desktop app and CLI; the host supplies their code and local plugin modules. The broader safe-projects gate remains open while other execution paths and desktop webviews are checked.
- The
ducktool now creates the same editable four-keyframe track blocks as drawing a dip; sounds outside a track retain their existing layer gain automation. - A sound track can now duck under another track’s voice clips without a transcript. The mix follows clip moves and mute changes; the source is chosen from the mixer’s D control.
- Sound tracks now have editable volume dips: arm D in the timeline, drag a range, then click its block to adjust the range, depth and slopes. The dip adds to the existing fader, is undoable as one edit and is heard in preview and exports.
- Generated music now keeps its proposed tempo, section plan, provider request mode and measured beat alignment beside the saved file. Providers without structured music use a prompt bed and the same beat check.
- Music generation now checks the received score’s beats against the film’s cuts before placing it. When a speed change of at most 2% improves alignment, playback keeps the original pitch; the tool reports the counts before and after.
- Music generation now sends film-shaped instrumental sections with an explicit tempo and exact section lengths to ElevenLabs Music v2.5. Invalid plans are rejected before the provider call.
- Music generation now reads the film’s length, cuts, markers and hero moments before its paid request.
/music-planshows the proposed tempo and how many cuts land on its beats without making a sound. - Mixer strips now show their ordered effect chains. You can open an insert’s settings, bypass or move it, and add voice cleanup, music under voice, telephone or big room presets. The
/chaincommand and assistant can propose the same edits with the full chain shown before applying it. - Delay and distortion can be placed anywhere in a track or bus chain. Echoes use milliseconds or notes at an explicitly chosen composition tempo, with bounded feedback; distortion has drive, tone and wet controls. Existing telephone, radio, megaphone and echo voices keep their sound through the same processors.
- Ordered track and bus effects now process their combined sources in playback, scrubbing and every export, preserving source files and the existing per-clip settings. Changing a chain refreshes its live sound and loudness measurement.
- Projects can keep ordered, bypassable audio-effect settings on sound tracks and buses, with each edit undoable in one step.
- The mixer master now shows live three-second loudness, true peak and clipping before the personal listening volume, alongside the composition’s target. Its stopped-film measurement remains available, and the assistant reads the same master levels.
- Live meters on mixer tracks and buses show peak, RMS and a held peak during playback, with a clipping indicator that stays lit until reset. Closing the mixer releases its analysers; the assistant can read and reset the same meters with
meters. - The desktop app has accounts: sign up, sign in and your space, like the web app. Its calls go to the accounts backend of the environment it was built for (the beta app to the beta, the stable one to production), the session is kept in the system keychain, and sign-in with Google or GitHub is not offered in the app yet.
- A beta build of the desktop app, “Tramme Beta”: it installs beside Tramme, and the beta site offers it.
-
Built-in pack tools now refuse data paths outside their own folder and stop reading a pack data file above 8 MiB.
-
The editor now refuses a shipped pack module larger than 1 MiB before loading it.
-
The editor now refuses an oversized or malformed built-in pack index before offering its tools.
-
Oversized plugin files and installed-plugin backups now stop before the editor reads them into memory.
-
Plugin packages and backups now stop at 2,000 archive entries; oversized packaged JavaScript stops before extraction.
-
Creating an installed-plugin backup now stops before compressing too many files or bytes.
-
Creating a plugin package now checks its file paths and size limits before compression.
-
Installed plugins now skip oversized stored modules, and library reads stop when a file exceeds its limit.
-
Plugin companion data now has file-count and byte limits, with reliable encoding for larger binary files.
-
Plugin packages now refuse encoded or URL-like data paths before their files are copied into a project.
-
Plugin backups now refuse unsafe installed-plugin names before creating an archive.
-
The timeline bar of a captured web scene shows its pictures as thumbnails.
-
Web scenes can hold videos and sound: the export extracts the pictures, follows the playhead and adds the sound to the film.
-
The assistant changes a web scene as a take you can accept, reject or undo, and checks its scripts for what would break the export.
-
A web scene shows live in the editor, inside a sealed frame, and follows the playhead and its animated parameters.
-
Web scenes have parameters: declared in the scene, shown as rows in the inspector, animated like any property and used by the export.
-
Selecting a web scene layer shows its code (read only) in the inspector.
-
The assistant now takes a project’s palette from its first good generated picture.
-
A web scene layer without captured pictures now shows a labelled placeholder in the editor instead of breaking the preview.
-
The browser editor’s message about web scenes now points to the command line (
tramme render). -
The desktop app now keeps web scene folders in its projects (scenes/), as the web editor and the command line do.
-
A test now compares a web scene’s seeked page with its exported frames.
-
A web scene exported by the command line can use the project’s fonts and pictures from its assets folder.
-
A web scene now sees the project’s tokens (colours, numbers, curves) as CSS variables when exported.
-
The assistant can write, correct and check web scenes (
write_scene,edit_scene,check_scene): a correction changes one file of one scene and nothing else. -
tramme rendernow exports web scenes: it captures each scene folder to transparent pictures, composes them like any layer, and re-captures only a scene whose folder changed. -
When a plugin sandbox stops (a runaway script, a crash), the editor now says what stopped and that your project and unsaved edits are untouched.
-
Plugin isolation now documents its time and size limits, and says plainly that a memory cap is not one of them.
-
Installed plugins can no longer follow a network redirect outside an approved origin.
-
The editor’s common project file URLs and multipart uploads now reject invalid format paths before requests.
-
LLM provider routes now reject malformed encoded provider names with HTTP 400.
-
Plugin and sound libraries now reject malformed encoded names and use decoded names for MIME types.
-
Project file routes now reject malformed percent encoding with HTTP 400.
-
Project storage now accepts JSON version snapshots, and the editor rejects forged version-index paths.
-
Filler-cut review now validates its project asset path before reading the list.
-
An open media bin or tag naming field no longer edits assets after switching projects.
-
The Direction panel now discards delayed project reads and brief writes after navigation, and validates image paths.
-
Media search no longer reuses transcript words across projects with the same file path.
-
Media placement now discards delayed duration and sound probes after a project or composition switch.
-
Timeline sound sync now discards results returned after the open project or composition changes.
-
Inspector sequence thumbnails now omit media URLs outside the current project’s assets.
-
Timeline sound sync now validates media asset URLs before decoding clips.
-
The source monitor no longer falls back to an unchecked media URL when its asset cannot be loaded.
-
Video layer and timeline placement now validate project media URLs before duration and sound probes.
-
Assistant media frames now refuse image and video URLs outside the current project’s assets.
-
Transcript reads and media transcription now refuse source paths outside the open project’s assets.
-
Plugin tools can now list, read and address only validated files under the current project’s
assets/folder. -
Assistant file commands now refuse encoded project paths before starting a read or write.
-
Built-in tools now reject encoded cross-project asset URLs and encoded file paths before a read or write.
-
Isolated plugin modules and fonts now stay inside the project folder even when their URLs contain encoded separators or dot segments.
-
Project plugin file requests now reject encoded traversal and ambiguous URL or Windows path characters before reading or writing.
-
Repeated project-module reloads now release temporary encoded source URLs once the isolated worker answers.
-
Malformed plugin-load messages from the isolated frame now stop that worker without throwing in the editor page.
-
Importing a project with plugins now stops clearly when an isolated worker is unavailable, without running the plugin in the editor page.
-
Composition and critic checks for isolated projects now evaluate their quality rules inside the project worker.
-
Scene-form advice in the composition check now reads isolated projects through the project worker.
-
The critic now finds visible layer entrances through the isolated project worker when reviewing an isolated film.
-
Camera pushes in isolated projects now frame expression-driven layers and text using the project worker, including the camera’s starting zoom and pan.
-
Pinning a layer to another layer now follows expression-driven corners from the isolated project worker when isolation is active.
-
Motion strips now read animated-property figures from the isolated project worker when project isolation is active.
-
Components made from isolated projects now take their frame from the evaluated picture in the project worker.
-
The mix report now draws picture motion from the isolated project worker when project isolation is active.
-
Video stabilization now follows expression-driven playback speed through the isolated project worker.
-
Sound beats, tracked video frames and callouts now follow expression-driven playback speed through the isolated project worker.
-
Sound cues for isolated projects now follow the picture through the project worker when placing effects, planning music and checking the mix.
-
Tracking an object from a drawn rectangle now places that frame using the isolated project’s evaluated geometry.
-
Sound effects that stop or build a music bed now read its animated level through the isolated project worker when isolation is active.
-
Live true-peak readings no longer show a spike created by the meter when screen and audio updates cross at different times.
-
Playback no longer adds the live limiter’s automatic gain on top of the composition’s loudness target, keeping a steady mix at its expected level.
-
The home page’s top bar was squeezed against the top edge when the page was taller than the window; it keeps its height, now one value for every top bar.
-
The icons of the phones’ apps sit on a white tile, not a dark one; the desktop icons stay the mark alone.
0.20.0 - 2026-11-05
Section titled “0.20.0 - 2026-11-05”- Quick button (desktop app): an optional small floating button, switched on in Settings > Behavior, that stays over your other apps while Tramme is behind them. It opens a panel to describe a film, start from an idea or reopen a recent project.
- Refractive glass theme (experimental): floating surfaces (the direction box, menus, pills, toolbars) now bend the picture behind them at the rim, with a faint colour fringe, in Chromium-based browsers and the desktop app. Other engines keep the frosted look.
Changed
Section titled “Changed”- The former Liquid Glass theme is no longer offered under that name: it was a frosted glass, not Liquid Glass. Its styles remain as the base of the refractive glass theme; those who had picked it now get that one.
- The direction box on the home screen has a thinner focus ring.
- The settings search has a custom clear button and a slightly taller field.
- The home top bar groups its icons together, then its buttons.
- The / menu on the home screen is no longer covered by the film cards, and bends and blurs them in the glass themes instead of letting them show through its text.
0.19.0 - 2026-11-03
Section titled “0.19.0 - 2026-11-03”- Timed motion direction in
film-plan: each scene can name its moving subjects, actions, start and end times, easing, settling and sound cues. Invalid timing is rejected before saving, and scene builders receive the complete choreography. Plans can identify a seamless loop; existing plans remain valid. - Motion loops pack:
/motion-loopadds an editable orbit, flowing ribbons or travelling grid behind the composition, with colors, density, dimensions and period in the inspector. Drawing is deterministic, including when frames are requested out of order. - Encoded video checks: local MP4, MOV and WebM renders are decoded after encoding and adding chapters, including parallel exports, to verify dimensions, frame rate, frame count and duration.
tramme check-mediachecks an existing file, with optional expectations and JSON output; failed checks return a nonzero exit code. GIF and PNG sequences explicitly skip this video check. - ARC product-loop example: an editable six-second product study, with a timed film plan and a packaging script that produces a self-contained
.trammearchive. The motion production guide documents the direction, review, delivery checks and native loops.
Changed
Section titled “Changed”- The critic respects the brief: flat graphics, long holds, silence, hard cuts and rich palettes are artistic choices rather than automatic completion failures. Craft suggestions are separated from blocking technical defects, and corrections name the observed frame or timestamp, subject and concrete change.
- Visual review covers the whole film: overview rows span the beginning, middle and end, followed by selected cuts, entrances and directed movement, within the existing image budget. Labels identify the actual frames and times; long films no longer spend the whole review budget on their earliest cuts.
- A single-shot film can use one picture kind, without being asked to introduce unrelated imagery for variety.
- Local exports of projects with plugins use the current rendered image: the sandbox drew to the preview canvas while the encoder read a different framebuffer, which could produce a frozen or empty video despite a correct preview. The capture path now writes the sandbox picture into the framebuffer read by the encoder; a browser regression verifies movement in the decoded MP4.
0.18.0 - 2026-11-02
Section titled “0.18.0 - 2026-11-02”- Liquid Glass, an optional interface theme in Appearance: neutral translucent controls, soft reflections and pointer-reactive lighting, with reduced-motion, reduced-transparency and contrast preferences respected.
Changed
Section titled “Changed”- Safe projects are an immediate roadmap priority: the safe projects roadmap defines the isolation, scoped permissions, failure handling and adversarial tests required before ordinary projects can open without a code-execution question. The public roadmap and documentation list this work as upcoming; the execution permission remains in place, and this isolation hardening is planned, not shipped.
- Windows refreshes file icons after installing, updating or uninstalling Tramme: Explorer is notified of the changed associations so
.trammefiles use the current transparent logo rather than an older icon with a white background.
0.17.1 - 2026-11-01
Section titled “0.17.1 - 2026-11-01”Changed
Section titled “Changed”- The new logo everywhere in the app: the top bars of the editor and the home screen showed the old T of frames and the name in the interface font; they now draw the logo from
brand/svg, mark and name, the mark alone on a narrow bar. The assistant’s and the view switch’s marks are the new one too. - Going from the projects to a project and back no longer shows an empty page: a cover in the theme’s colours and the mark is on the page from its first paint and closes before the next one is asked for. The saved theme is put on the page before it paints, so a light theme never starts dark. The assets’ loading shows the mark’s two shapes coming in one after the other, in place of a line of text.
- Models are called by one name everywhere: the model button, the menu and the usage lines show the name the listing gave (Codex’s, OpenRouter’s), or, for a model listed by its key only, the key written out (“GPT-5.1 Codex Max” for
gpt-5.1-codex-max). The steps of a turn open above their button, and the conversation follows its end as the steps come, unless you scrolled up to read. - The app’s icons stand on no ground: the favicon, the installed app’s icons and the desktop icon are the mark alone, in the studio’s accent, as a program’s icon is, not on a white tile. The two icons the systems fill (maskable, Apple’s) sit on the studio’s dark ground, and the desktop app’s own sizes were drawn again.
0.17.0 - 2026-10-31
Section titled “0.17.0 - 2026-10-31”- The site, redesigned: one grid, one heading style, one way to show the app. A top bar with menus (Product, Features) that work without script, a footer in columns, and a landing page of five sections: the app playing, tabs that switch between the studio, the atelier, the assistant, the packs and the export in one frame (radio inputs and CSS, no script), the examples, the questions (also told to search engines) and the closing call. New pages: Features (every section in detail, with the toolbox by category), Examples (the repository’s films, each with a way into its folder), Pricing, About (with the facts counted from the code), Privacy (what is kept where), and the changelog as a docs page. In the editor’s own theme, both themes, a phone to a wide screen, the landing page no heavier than before.
Changed
Section titled “Changed”-
A new licence, from the version after 0.16.0: the Functional Source License 1.1, ALv2 Future License (FSL-1.1-ALv2) replaces the Apache License 2.0. The source stays available: anyone can use it, modify it and redistribute it for any purpose except offering a competing commercial product or service, and each version becomes Apache 2.0 two years after its release. Versions up to 0.16.0 stay under the Apache License (LICENSE-APACHE), as do the contributions of the one outside contributor, listed in THIRD_PARTY_NOTICES.md. Contributors now sign off their commits (
git commit -s) and agree that their work is under that licence and any later one the author chooses (CONTRIBUTING.md). Thelicensefield of every package, the README, the site (it no longer says “open source”) and the link preview follow. -
The new logo: the mark and the name in
brand/, on the site (the top bar, the footer, the docs) in the theme’s accent and ink, and as the app’s icon: the favicon, the installed app’s PNGs, the desktop app’s icons (tauri icon) and the link preview card, all drawn byscripts/app-icons.tsandscripts/og-image.tsfrom the brand files and the editor’s theme tokens (scripts/brand.ts). The link preview shows the studio and the site’s own words again; its screenshot path had gone stale. -
The Claude models are listed, never written down: the menu, the default model, the critic and what each model is asked (adaptive thinking, effort levels) came from lists written in the code (Opus 5.5, Sonnet 5.5, Haiku 5.5, Haiku 4.5), so a new model reached the menu only with a release. They now come from the source of each route: the companion asks the Agent SDK what the Claude Code login offers (
supportedModels(): the name, the effort levels and the adaptive thinking of each model, the one recommended marked), and the Anthropic API lists what the key can use (GET /v1/modelsthrough the Claude route, the newest first, active models only, with the capabilities of each). Both are merged in the menu, the companion’s first, and kept ten minutes. A model nobody chose is the one recommended (else the newest Opus); a chosen model that is gone is replaced, with a notice; a model the listing does not know is asked for no thinking and no effort.MODELS,DEFAULT_MODEL,ADAPTIVEandNO_FALLBACKare gone (a model that has no server-side fallback refuses it once, and the request goes on without).
- The local companion finds Codex where its own installs put it: Codex was offered in the model menu only when
codexanswered on the PATH, which the Codex app and the VS Code extension (openai.chatgpt) do not set up, so a computer with Codex signed in, but nonpm install -g @openai/codex, did not list it. The companion now also tries the app’s program (%LOCALAPPDATA%\OpenAI\Codex\bin, the newest build first) and the extension’s, in VS Code, Insiders, Cursor and Windsurf, the newest version first, and runs the turns with the newest one that answers (the models Codex offers depend on its version). The model menu also lists Codex’s own models, read fromcodex debug models(the listed ones, in Codex’s order, kept ten minutes), where it offered only “its default model”.
0.16.0 - 2026-10-30
Section titled “0.16.0 - 2026-10-30”- Retouching in the studio: pin several things on the picture at once, each a point, a path drawn with the finger (a line for the assistant to follow or lay things along) or an area drawn round or across layers to select them. An area only proposes layers: you drop or add some, then confirm, use it as a hint with no layer chosen, or set it aside (the setting Selecting layers by drawing: always, above three layers, never). Retouches, typed or spoken, are added to a list that can be reordered, taken back to change and removed, then sent all at once as one turn, each with its own pins, moment and scene.
- A library of references (taste and finish, step 8):
referencesreads principles and faults of the craft in words, with how to see each and how to fix a fault;reference-keepkeeps the user’s own films with their reasons and the facts read from them, and the library warns when the films kept converge on one look; the critic is told the faults. Typefaces and references share one normalisation of words. - Scene by scene (taste and finish, step 7): a film planned with three scenes or more is built one scene per fresh context (the plan’s scenes gain
comp,briefandstatus;scene-done), each kept to its own composition by a scope on its proposals, then assembled in the director’s conversation; the Studio’s notes show each scene under its name andbench/usage.tsprices each apart. The setting Scenes built apart turns it off. - The critic (taste and finish, step 6):
critiquehas the film reviewed in a fresh context by a model that did not make it, against a measured definition of done that it cannot overrule, with strips around every cut and entrance and the style frame;scene-takesmakes two or three takes of a scene that failed twice and keeps the best; Critic rounds is a setting; its cost is counted apart. Along with@to tag assets in the message box and the home’s box. - The missing vocabulary (taste and finish, step 5, the rest): the interface pack (ten pieces, light and dark, and the
screentool that fills adevice-screenwith them), 3D solids (solid.3d: box, slab, sphere, torus, capsule, cylinder in matte, glossy, glass or metal, lit by an environment image or a studio gradient;model.3dtakes anenvtoo, and the two sharegl3d.ts), candlesticks and price lines in the Charts pack (1.2; plain numbers are now a series, whichchart.line’s own default needed), andcompare, a render beside a target and their difference with a likeness score and the words on what differs most (the measure moved to core, andtramme compareuses it). The guide names them. See Interface pieces, finance charts and the comparison. - Layers in perspective, a corner pin and a push onto a detail (taste and finish, step 5, in part):
rotationXandrotationYturn a layer around its horizontal or vertical axis in the composition camera’s perspective; thefx.pincorner pin and thepintool carry a picture onto four corners, given or followed from another layer; thepush-intool pushes the camera onto a detail and back with its text kept readable. The checks and the viewport read a tilted layer through its quad; the Lottie and SVG exports draw it flat and say so. See Tilts, the corner pin and the push-in. - Material (taste and finish, step 4):
generate-imagemakes objects on a transparent ground (object), in the style of the film’s target; thesurfacetool lays nine textures and lights drawn by the engine (grain, paper, halftone, gradient, glow, ribbons, grid, bokeh, caustics); thestocktool searches the free libraries (Poly Haven and ambientCG textures, environments and models; Pexels and Openverse photos; Pexels clips) and keeps the chosen file with its licence; real logos and pictures are fetched only with your yes and listed when nobody is there; thecreditstool now covers every fetched or made file. A Pexels key can be connected in the settings. See Surfaces and Stock. - A film plan and style frames (taste and finish, step 3): before building, the assistant writes the few kinds of picture the film alternates (interface, type, object, data, diagram, photo, 3D, character, map) assigned to scenes, and one to three directions written precisely (
film-plan). An image model draws a style frame for each (style-frames, a Style frames setting: Off, 2 or 3); the one kept is the film’s target: its palette becomes the project’s colours, its lettering is matched in the typefaces catalogue (typefacestakes it to compare), its plates and objects are made again without words. The check says when scenes as built repeat one form, and the Direction panel of the studio shows the plan and the target. See Film plan and style frames. - Typefaces (taste and finish, step 2): the
typefacestool looks for open families by character (“condensed grotesque, heavy, for titles”) and shows them on a specimen sheet set in their own letters;typeface-usebrings the chosen ones into the project as font assets, their files at a pinned version underassets/fonts/with a record of their licence. The recipes write headlines in the display face and the rest in the text face, and the assistant’s instructions tell it to pair a display face with a text face and never to leave the system font. See Typefaces. - The assistant finds what already ships (taste and finish, step 1): the packs’ entries are listed by need in its instructions, it is told to search the vocabulary before writing a plugin, and the plugins it wrote in a turn are listed to you at the end, to keep in the library.
- A phone, browser or window frame around an interface built in layers: the Frame for an interface built in layers tool of the walkthrough pack lays the frame with a content group that the screen clips;
ui.devicedraws without a screenshot and in two parts. tramme check <doc>prints the picture checks of a project, folded by cause.- A coverage check for a talking video: the stretches with only the speaker on screen (a note from 12 s, a warning from 20 s).
- A timeline by tracks (montage.md): a composition can be a sequence, its clips on picture and sound tracks with lock, hide, mute, solo, a magnetic mode that closes gaps, a height, and an adjustment clip for a range of tracks. The format gains optional fields only (
kind: "sequence",tracks, a clip’strackandlink, a track’svolume,pan,bus,to); a document without them is read as before. - The edits of a video editor, one function each in
@tramme/coreand the same for the keys, the mouse, the assistant: ripple delete, ripple trim, roll, slip, slide, insert, overwrite, reorder on a magnetic track, linked clips, a video’s sound detached on its own track, copy and paste with the look, cut at the playhead (Ctrl+B, Q, W, Shift+Delete, L,,and.). - Media: bins, tags and a search that also finds a word said in a clip; a source monitor with in and out marks and sub-clips; media gone missing listed offline (the preview goes on, an export names them, “Find the files…” brings them back); clips lined up by their sound; multicam (one camera per track, a panel that cuts between them); drag a media or a composition onto a lane; several compositions open in tabs.
- Sound: a mixer with a strip per sound track and bus (volume, pan, mute, solo, automation written by moving a fader while the film plays), a loudness target and a measure, and a voice-over recorded on the timeline.
- Picture: match the look of a shot to another’s with editable colour wheels; Real-ESRGAN as a choice for enlarging pictures (the built-in Lanczos stays the default).
- Publishing: presets for a vertical short, a square, a landscape film, a 4K master and a GIF, with what stands in the way listed and fixed; export the marked part (I and O); exports in line, each on the film as it was asked for; chapters (markers of kind
chapter) written into the files the command line renders, and copied as a list from the browser. - The assistant has the editing operations as tools:
ripple_delete,insert_clip,overwrite_clip,ripple_trim,roll,slip,slide,detach_audio,link,sync_clips,add_adjustment,match_look,publish. A guided tour of the lot. - The hesitations cut by the fillers tool can be reviewed and put back one by one from the media panel.
- Guided tours for what had none: Grade and match a look (the scopes, matching a shot to another, the 10-bit export) Make it yours (tokens, plugins and packs, the tours plugins bring) and The tools of the / menu (footage, voice, the material read, whole motion pieces, following an object, pictures and clips by a provider, reuse, checks). The tricks tour gains masks and the viewport’s safe zones, grid and onion skin; the home tour names the language setting. The montage tour gains several cameras, adjustment clips and chapters; the sound tour, recording a voice-over; the assistant tour, dictation and the messages that wait while it works. A test checks that every place a tour points at exists in the interface and is listed in Guided tours.
- The bar of a browser or window frame (the walkthrough pack) is drawn at the top of its frame; it was drawn from the frame’s centre, under the screenshot, so its dots and address never showed.
- The numbers of the list recipe are in the plate’s colour on their accent dots, not white on yellow.
- The check reads like a list you can act on: issues of one cause are one line (the worst one, the span, the compositions concerned), at most twelve lines reach the assistant, the rest counted.
- Contrast is measured against the card the text sits on, in the composition it is played in, with the standard’s ratio (3:1); a text still fading in and a pictogram are not judged, and neither is text over a layer whose colour is unknown.
- The atelier’s tour is offered when a project first goes to the atelier, not only when one opens in it: the studio is the default view, so the tour was reached only through the help menu. The editor tour’s last step now lists the tours that exist.
- A tour step whose place is missing no longer costs the next step its preparation: the step is skipped, but the next one still opens its tab. The mixer step of the montage tour points at the tabs until the film has a sound track, instead of vanishing.
- The voice detector loaded the wrong onnxruntime build (the one whose wasm files transformers.js does not configure), so it fell back on the energy of the sound; it now loads the build the other models use.
- The editor’s
timehelpers moved to@tramme/core(packages/core/src/timing.ts), the editor re-exporting them: the montage operations and the assistant need them without the interface.
0.15.1 - 2026-10-28
Section titled “0.15.1 - 2026-10-28”- The local companion transcribes in the language spoken too: it ran Whisper without a language, so transformers.js took English. It now reads the language from Whisper’s first step, as the browser does, and tells it back so the next chunks of a long sound keep it.
- A video added from the assets plays whole: its layer is as long as its file, and a composition shorter than it lengthens to hold it (one undo takes both back). A 12-minute video added to a new 5-second project was cut to 5 seconds and looped there.
- The cut in the file reaches past the composition: stretching a video’s end past the composition’s end lengthens the composition with it, so what was taken is seen and played instead of falling after the end.
- The model chosen stays chosen: the companion missing one of the editor’s checks (busy with a turn or a transcription) no longer replaces the model picked with another connected AI’s; that takeover now only happens at startup, while the chosen model has never answered.
- A media file’s length that cannot be read no longer hangs: reading it gives up after two retries, where the media library’s default tried again for ever.
0.15.0 - 2026-10-28
Section titled “0.15.0 - 2026-10-28”- A queue for the messages written while the assistant works: every message box (the conversation, the Studio’s direction bar, the notes) keeps accepting messages during a turn. They wait above the box, each with a button to take it back, and leave together when the turn ends, as one turn of the assistant, each with the context of the moment it was written (the time, the selection, the scene, the pin), so “this layer” is the layer that was selected then. After a stop or a failed turn the queue stays, with a “Send now” button, and leaves with the next message; a turn that ends with a proposal waiting for a decision holds it until the proposal is applied or rejected. The queue survives a reload of the page.
- Dictation: a microphone in every message box (the home page, the conversation, the Studio’s direction bar, the notes). Click to speak, click to stop, and what you said is written where the cursor is, for you to read and send; Escape drops the recording. It runs on the downloaded Whisper model first (Whisper base, 80 MB, is offered when none is downloaded), and a setting in Models, Sound chooses the downloaded model, the companion or the server. The desktop app asks for the microphone (
NSMicrophoneUsageDescriptionon macOS). - Haiku 5.5 in the model list, next to Haiku 4.5, with adaptive thinking and the five effort levels (no server-side fallback is asked for it). The default model does not change.
- The conversation’s cache lifetime, as a setting: 5 minutes (as before) or an hour, in Settings, Behavior. An hour costs more to write and less when you come back after more than five minutes.
- The bench prices and compares the assistant’s turns: every route now reports its usage (the chat-format providers through
stream_options, with the cached share where each gives it; cache writes split by lifetime; each turn names its route, and says when it has no usage rather than counting zero).node bench/usage.tsadds the dollars (a price table for Claude, “unknown” for a model without one, “at least” for Haiku 5.5), the cache share and the route per turn, per conversation and in all;node bench/usage.ts --compare <before> <after>compares two series of runs. Costs stay in the bench, never in the chat. - Clips, made by a provider (generation-roadmap.md, step 5):
generate-videohas Veo 3.1 Fast, through Hydracept, make a 4, 6 or 8 second shot from words, or animate a still picture of the project as its opening frame. The clip is saved underassets/videos/with its record (.video.json), proposed as a video layer at the playhead, and answered with a frame so the assistant judges it;againandchangemake it again from its record. A new Videos section in the settings sets the provider and the length. Each second is billed, so the user says yes first, as for the pictures and the sounds.
Changed
Section titled “Changed”- The system prompt is in cache order: the same text, reordered, so that the reference (
docs/document.md) follows the instructions and comes before what changes with the project (the installed plugins, the packs, the brief). The Messages API caches the fixed part apart for an hour, so it is served from the cache across projects; the other routes get the same order in one piece.
- The local companion is found whenever it starts: the app looks for it again every few seconds while it is missing and every fifteen once it answers, on every screen and whichever route works, and when the window regains focus. A companion started after the app, or one that stops, is noticed without a reload.
- Speech in any language, transcribed in it: transformers.js transcribes as English when it is not told the language, so a French dictation came back as English words. Whisper’s own first step now tells the language spoken, for dictations and for the sounds transcribed in the browser.
- Dictation, quicker the first time: it runs Whisper on the processor in the compact weights the download offer names (77 MB), where a GPU fetched the full ones (291 MB), and shows the download as a percentage beside the microphone. A second click while the microphone opens no longer opens it twice, and the recording time never shows below zero.
0.14.0 - 2026-10-26
Section titled “0.14.0 - 2026-10-26”- Shorts, framed closer and cut from any video (steps 2 and 5 of the shorts roadmap): a speaker small in the frame gets a gentle push-in that settles over the short, and when the people detector hesitates the frame follows the cutout’s mask instead. A video nobody speaks in — a match, a ride, a build-up — gets its candidates from its sound and its cuts (the build-ups into a louder section, the loudest moments, snapped to cuts and bar lines), described in words so the assistant picks the same way, and its shorts build without captions.
- Pictures, chosen and changed (generation-roadmap.md, steps 2 to 4): a new Pictures section in the settings sets the provider by default, the quality and the size at most (small asks the provider’s cheapest size).
generate-imagemakes up to four takes of an ask — a contact sheet in the conversation, one click keeps one, the others are never saved; makes a picture again from its record changing only what is asked (againandchange); changes a reference — an image asset or a frame of the video — with the project’s palette sent along (OpenAI and Gemini), a mask saying where (the cutout tool makes them), or extends it past its edges to a wider format; and brings a small picture to the size of the frame before placing it. - Logos in 3D (
plugins/extrude.js, packs-roadmap.md, step 17): a logo that turns for an opening or an end card. Theextrudetool (/extrude) takes the path layers of a logo or an icon (an SVG through svg-paths, or one path), reads its holes, extrudes it with a bevel and writes it as a.glb— one material per colour of the logo — that the built-in 3D model layer draws turning on its turntable under the studio light, its yaw, pitch and explode keyable. The faces are triangulated by ear clipping with the holes bridged in; the flat logo stays, hidden, to edit and extrude again. Type is extruded once it is outlined in the SVG. - Kinetic type, further (
plugins/kinetic.js1.1.0, packs-roadmap.md, step 16): two new moves for a word, a name or a figure.scrambleruns every character through others, seeded, before each settles in turn from left to right — a code breaking, a name revealed.flaplays the text on a split-flap board: each character flips through the drum to its own, the top half of the old flap folding down and the bottom half of the new one opening, a departures board or a counter. Both are pure functions of time, with a preset each. - QR codes (
plugins/qr.js, packs-roadmap.md, step 15): an end card the viewer scans. The pack encodes the code itself (ISO/IEC 18004: byte mode with UTF-8, versions 1 to 20, the four correction levels, the mask of least penalty) — its symbols are the same, module for module, as a reference encoder’s. Theqr.codenode draws the modules square, rounded or as dots in ink on a plate with its quiet zone, a logo in the middle (the code goes to level H to carry it), revealed module by module as a sweep or a seeded scatter, and exports as SVG and Lottie. Theqr-scannablecheck flags modules under 5 px, a quiet zone under four modules, light modules on a dark plate or ink under 4:1, and a code on screen for less than 3 s. - Print looks (
plugins/print.js, packs-roadmap.md, step 14): a whole film printed as a risograph. Four GLSL finishing passes, computed on the frame in linear light inside the pass:print.halftone(an AM screen of one ink on a grid turned by the angle — the cell sets how coarse it reads),print.riso(two inks, each a little off register, multiplied into paper that carries a grain),print.grain(film grain sized by the luma — brighter places carry bigger grains),print.duotone(the picture’s light laid between two colours). Three stacked presets: risograph, newsprint, two-tone. Each pass compiles in the render tests’ Chrome and gives its known pixels on a gradient. - Rigid bodies (
plugins/physics.js1.1.0, packs-roadmap.md, step 13): a small engine in the pack — boxes, circles and convex polygons falling, colliding, stacking and coming to rest.stepWorldis pure (frame 90 is the same reached directly or frame by frame), solves with sequential impulses over SAT contacts (the least-overlap axis, the contact clipped to the face, a twin point when a face meets a face — a stack needs two to stand), friction in the cone, restitution fading under a walking pace, a touch of damping, the overlap eased out and a body slow for a while put to sleep. Thephys.bodiesnode runs it through the engine’s checkpoints with the frame’s sides and floor as static bodies; the text drop’s letters are bodies now, so they knock into each other and pile up the way they land. - Matter pack (
plugins/matter.js, packs-roadmap.md, step 12): the row the plugins roadmap left open. Thematter.morphnode walks both shapes again at equal arc length and matches their winding and their starts (the rotation of the second that meets the first with the least summed distance), so an icon becomes another without twisting, its curves followed, several contours paired by size and place and the extra ones growing from a point. Thematter.liquidnode paints seeded blobs that merge and part — a field of circles traced by marching squares, oriented so the loops chain, drifting as slow as lava, or as a flood crossing the frame from the left and draining back. Thematter.papernode sweeps a sheet across the frame, covering it at the cut, its edge torn by seeded noise with its fibres and its shadow, the same in every render. All pure functions of t: the liquid answers any frame in any order. - Formulas (
plugins/math.js, packs-roadmap.md, step 11): a TeX subset laid out by the pack in STIX Two Math (OFL) — no MathJax, no network. The parser reads fractions, scripts, roots, sums and integrals with their limits, small matrices (\begin{pmatrix}),\text,\colorand\mathbb, the Greek letters and the common operators (\cdot \times \le \ge \ne \infty \to), an unknown command throwing with its position; the layout walks the tree and places each glyph from the font’s own table (glyphs.json, 216 glyphs extracted once from the font byscripts/packs/math_glyphs.py+scripts/packs/math.tsthrough the SVG reader), each symbol an id stable per occurrence so themath.formulanode can change one formula into another — the shared symbols move to their places, the others fade and arrive, the way a proof unfolds on a board. Variables are set in the font’s math italic. Theformulatool copies the glyph table into the project once, so a formula draws the same everywhere, and refuses a symbol the font does not carry; theformula-legibilitycheck flags a size under the format’s floor and a formula on screen for less than its reading time (slower than text). - Audiogram pack (
plugins/audiogram.js, packs-roadmap.md, step 10): a podcast extract as a clip for the feeds.analyseAudionow computes the sound’s 32 log bands (40 Hz to 16 kHz, an FFT of 2048 samples at every frame of its 50 Hz rate, saved decimated to 12.5 Hz — a 30-minute analysis stays under 6 MB), and theaudiogram.wavenode draws them as bars, a mirrored wave, a line or a ring at the moment of the extract that plays, rising with the voice and falling back like a meter, a playhead crossing; theaudiogramtool lays the clip out, varied by a seed — cover behind, the show’s name, the wave, the words said as captions when the sound has its transcript, a progress bar trimming itself across, the sound (or a video’s own) playing from the moment asked. Each band is read against its own loudest moment, so a pause reads as a pause. A 1 kHz tone lights its band; the bars read the bands linearly between the frames. - Maps pack (
plugins/maps.js, packs-roadmap.md, step 9): “our offices in Lyon, Montreal and Dakar” becomes a map, offline. Natural Earth (public domain: countries at 1:110m and 1:50m, first-level regions, 7 000+ populated places) ships beside the pack, simplified and quantised to 1e-4° byscripts/packs/maps.ts; themaptool (/map) finds places by name with the accents folded and the aliases known (“NYC”, “Bombay”), asks back when a name is ambiguous (“Springfield” is five), picks the projection and the framing from what is shown, and writes into the project only the shapes the map shows (a two-country atlas is about 2 % of the 50m file). Themap.viewnode draws the countries from the tokens, the named ones in the accent, pins with their labels kept apart, routes as great circles drawn on; the camera (centre and zoom) animates, and with a route it flies from one place to the next on van Wijk and Nuij’s smooth zoom — out in the middle, exactly on its end, never faster than the eye follows — while the route draws itself, then pulls out to the whole map. A still map exports as SVG. Themap-legibilitycheck flags highlighted countries too small at their zoom, labels with no room beside their pins and a zoom that doubles in under 0.6 s. - Charts, further (
plugins/charts.js1.1.0, packs-roadmap.md, step 8): thecharttool reads a CSV (separators,;and tabs sniffed from the first line, quoted fields with doubled quotes kept whole, decimal commas read as numbers) and, withkind: 'race', turns a table of periods by entries into thechart.racenode, keyed to run over the composition — bars sliding to their new rank, values rolling, the period shown large behind, the leaders kept in view and the tail cut (12 racing at most in 9:16, 20 in 16:9, the cut named). Thechart.scatternode draws two measures together, points travelling between periods with their trails, labels kept apart. Thechart.functionnode draws a curve the tool sampled (the points come computed; the node never evaluates a string), with the pack’s readable ticks, a dot travelling along it, a tangent and the area under it on demand. Thechart-readabilitycheck flags colliding labels on a scatter and more than 12 entries racing in 9:16. - Chat and emoji packs (
plugins/chat.js,plugins/emoji.js, packs-roadmap.md, step 7): the text-message stories of short videos. Thechattool (/chat) reads a script (A: …, a time in[2s]when a line lands), times it by reading (max(0.9, words/3.3 + 0.3) a line, a reply that takes thought pausing longer), and plays it as thechat.threadnode — bubbles entering on the kit’s curves from their sender’s side, a typing indicator before each incoming message, the thread scrolling to keep the last message in view — in the walkthrough pack’s phone in 16:9, full frame in 9:16. Thechat.noticenode drops notifications in and stacks them for the cold open. Thechat-readingcheck flags a message pushed away before its reading time and a typing indicator under 0.4 s. Theemojipack ships the 300 most used emoji as Fluent Emoji Flat SVG (MIT, converted byscripts/packs/emoji.ts), theemojitool places them as picture layers by name or character — only the files used are copied into the project, and they draw the same on every machine, never the system’s emoji font; given a chat thread, it draws the thread’s emoji as the same pictures, inside the bubbles. - Handmade pack (
plugins/handmade.js, packs-roadmap.md, step 6): warmth for explainers. Thefx.boillayer effect (GLSL) redraws the layer a little off every 2 or 3 frames, so a machine-drawn line trembles like one drawn by hand (the amount in px, held between changes); thetwosmodifier holds any value for n frames with a small seeded jitter at each change, for stop motion and cut-out paper; thesketch.shapenode draws a rough line, arrow, rectangle, ellipse or bracket as two seeded passes that overshoot their corners (rough.js’s idea, in the pack’s own code), hachured fill included, revealing withprogress; theannotatetool (/annotate) draws a circle, an underline, a box, a highlight, a strike or a bracket around a layer, on a beat after it lands, its keys riding the layer’s position when it moves. Thesketchbookkit brings the paper plate, the graphite ink and slower curves, and Caveat (OFL, latin subset) ships beside the pack as the handwritten face. - Screencast pack (
plugins/screencast.js, packs-roadmap.md, step 5): a screen recording played as a product film, without a key placed by hand. Thescreencasttool samples the recording (one look every half second, a 30-minute recording capped at 1 800 — one a second, and said), measures where the picture changes on a 32 px grid, tells the whole-screen change of a scroll or a page load from the local one, and saves the regions of interest over time as a JSON asset. From them it keys the video layer’s zoom — in where the action is (eased at 1.5× a second at most, held while the region stays, out before each page change, never over 2.5×, never showing past the recording’s edge) as ordinary scale and position keys on the composition’s clock, and marks a found click (a small region after a still stretch) with the walkthrough pack’s cursor ripple. The still stretches are named for the edit — a speed-up or a cut, offered, never applied. Thescreencast-motioncheck flags a zoom faster than 1.5× a second and a focus that leaves the picture. - Rhythm pack (
plugins/rhythm.js, packs-roadmap.md, step 4): checks only, what a motion designer catches in a film that is right frame by frame and wrong as a whole.off-beatflags a cut landing more than 2 frames from every beat of the music (the film’s beats analysis) and names the beat — the bar line, at a section change — to move it to;even-shotsflags four shots or more of nearly the same length (spread under 15 % of the mean): the film plods;palette-driftflags fills and strokes written outside the tokens and far from all of them (ΔE over 10, CIE76), or more than five colours on screen at once;type-driftflags more than two typefaces in one film and near-duplicate sizes on one frame (within 10 %). The/reviewworkflow adds the pack when the film has music. - Code view pack (
plugins/codeview.js, packs-roadmap.md, step 3): code on screen for developer tools and product films. Thecodeview.codenode colours code by a lexer written in the pack (js, ts, py, rs, go, sh, json, yaml, sql, css, html; tokens to the kit’s accents, moved away from the panel until they read at 4.5:1, comments at 55 %), with line numbers, highlighted lines (the others dimmed, the view scrolled to the first), typing at a seeded human rhythm (18 characters a second, a pause at each line’s end, the caret blinking), and a change between two versions — the tokens both share slide to their place, the removed fade, the new ones type in (a longest-common-subsequence diff of tokens). Thecodeview.terminalnode runs a session written as a script ($ command,> output,...with seconds): commands typed, output arriving in chunks with its ANSI colours mapped to the tokens, a spinner and progress bars ([###] 2) stepping with time. Thecode-screentool (/code-screen) lays code or a session in the walkthrough pack’s newwindowframe (a title bar and tabs, no address bar), at the format’s legibility floor (24 px on a 1080-high frame, 28 in 9:16), a long file cut to what fits with the cut named (the highlighted lines kept where they are), and thecode-legibilitycheck flags small type, more lines than fit, and typing faster than reading. The walkthrough pack is at 1.1.0 for the window frame. - A project’s older copy of a pack offered its update: the Code section lists an “Update to {version}” beside a copy of a shipped pack older than the editor’s, written in place with its version recorded, the way an installed plugin’s copy already is.
- The sound heard while scrubbing: dragging the playhead plays a short window of the sound at each step (80 ms, at most every 60 ms, never the videos’ own streamed sound), enough to hear the moment a cut or a hit lands; a setting turns it off (on by default).
- The
/menu remembers what is used: the commands a user actually runs open the menu first (at most six kept on this machine), and the search is unchanged once something is typed. - The packs’ commands on the home screen: the direction box’s
/menu lists the shipped packs’ tools after the built-in ones, before a project opens — a pack command a project does not hold yet waits in the editor’s box until the project’s packs attach. The list comes from an index generated from the packs themselves (npm run packs:index:plugins/index.jsongains each pack’s commands and their French,docs/packs.mdthe site’s new Packs page), which CI checks cannot go stale. - The desktop app asks for attention when a question waits: while you are in another window, a question of the assistant or the editor flashes the taskbar (Windows, Linux) or bounces the Dock icon (macOS) besides its notification, until the window is focused or the question goes; in front of the window, the message alone, as before.
- The preview’s playback clock is pinned by tests: the wrap of a loop, the end without one, and a playback overtaken by another or by a pause are each tested, out of the preview itself; nothing changes in how it plays.
- The model chosen on the home screen: the direction box offers the model menu beside the format, so the first turn of a new project runs on the model picked there.
- A turn paused: the assistant at work can be paused before its next tool and resumed, from the pill over the film or the studio; stopped while paused, the tool that waited never starts (a picture or a sound costs money).
- The turn under way, in the studio: what the assistant does now and for how long, the model it runs on, the stage it is at among all of them on a bar, its last three steps (all of them on demand), pause and stop.
- What a tool did, under its line: each call says how long it took, why it failed (the first line of its error) or the tool’s own notice; a sound or a picture names the provider and the model that made it. Conversations saved before read these lines back from their history.
Changed
Section titled “Changed”- The app is named Tramme: the editor, the desktop app, the site, the assistant and the documentation write the name with a capital. The command line (
tramme), the packages (@tramme/…), the.trammearchives, the project files and the stored settings keep their names.
Removed
Section titled “Removed”- Films from a description (
@tramme/film): thefilm,film-guideandfilm-reviewtools, the/filmworkflow, the film kits (midnight, daylight, poster, studio, terminal, soft, luxe, paper),tramme filmon the command line and the fonts shipped for them. Its compiler gave every brief the same few layouts. Words written on the home screen now start the assistant directly: it directs the film with the editor’s own vocabulary (compositions per scene, templates, recipes, packs, kits) and checks it withcheck. A project made by the film tool still opens: its scenes are ordinary compositions, its description an ordinary file.
- The PNG sequence export said, in French, “une image par tramme” instead of “par trame”.
- A folder holding 3D models imports: bringing in sources with a .glb or .gltf among them failed as a whole, the project format refusing those files under assets/ (in the browser, on the server and in the desktop app alike); they are now kept as model assets the 3D model layer draws, a large .glb sent in parts like a video. The extrude tool’s .glb is written the same way.
- The packs’ forms in French: the fields of the packs’ tools in the
/menu (charts, stick figures, walkthrough, localize, icons, diagrams) carried English titles and hints in a French editor; every field is translated, and a test now keeps them so.
0.13.0 - 2026-10-25
Section titled “0.13.0 - 2026-10-25”- Diagrams pack (
plugins/diagram.js, packs-roadmap.md, step 2): flows, architectures, cycles and trees written as flowchart text (a Mermaid subset:A[Label] --> B(Round),C{Decision},-->|label|,---,-.->,subgraph;LR,TB,RLorBTto force a direction, left out to let the format pick it — left to right in 16:9, top to bottom in 9:16; errors name their line) or the same as JSON. The parser reads it; a layout written in the pack, pure and deterministic, places it — layered (ranks by longest path, crossings reduced by barycentres, coordinates balanced), a ring for cycles, a hub for stars — and thediagramtool (/diagram) expands it into ordinary layers: boxes (shape.rect, the kit’s radius), labels (wrapped, sized to the format), edges (shape.pathwith their arrowheads, drawn on with the trim between their ends’ arrivals), revealed in reading order with an uneven stagger, in one group; ahighlightnode dims the rest and lifts one route through the graph in the accent. Thediagram-legibilitycheck flags a label overflowing its box or set too small, an edge crossing a label, and more boxes than the format holds at once (about 12 in 16:9, 8 in 9:16). - Icons pack (
plugins/icons.js, packs-roadmap.md, step 1): Lucide 1.61.0 (ISC, 2 166 icons with their tags) shipped beside the pack asplugins/icons/lucide.json, converted byscripts/packs/icons.tsthrough the SVG reader into path values on the 24-unit grid. Theicontool (/icon) finds pictograms by name, tag or a few words (ranked search with synonyms of the common words: “money” findsbanknote,wallet,coins), lays one or several in a row, a grid or beside the lines of a list, in the film’s colours (@ink, @accent or a colour), each a group namedicon:<name>of path layers with round caps and joins, its stroke riding the group’s scale, its contours drawing themselves with the trim, staggered unevenly; when the words are vague, the candidates come back as a contact sheet of named icons. Theicon-strokecheck warns when an icon’s stroke is under 2 px at the composition’s size and when one group mixes weights. - Packs, step 0 (packs-roadmap.md): the ground the packs stand on, in Tramme itself. Strokes that draw themselves:
trimStart,trimEndandtrimOffset(0 to 1, animatable) onshape.rect,shape.ellipseandshape.path, measured along the outline’s length and drawn as a window of the stroke (a dash over it), by Lottie’s rule (an end before the start swaps with it; a rectangle’s outline starts on its right side under the top right corner, an ellipse’s at the top, both clockwise), so a trim draws the same stretch in the preview, in Lottie and in SVG; exported to Lottie as trim paths (tm, the fill kept whole in its own group) and to SVG withpathLengthand a dash; theshape.pathnote rewritten on them, and the map-journey recipe reveals its line with them instead of a matte. SVG to paths: an SVG reader inpackages/interop(path data with arcs as cubic Béziers, circle, ellipse, rect, line, polyline, polygon, their transforms and their groups’ presentation, one contour per shape; the viewBox mapped into the drawing’s size, an unstyled shape filled in black as SVG does, arc flags read even when written against the next number) beside the export, and the built-insvg-pathstool (assistant and/menu) that turns an SVG asset into a group of path layers with their fills and strokes, its strokes drawing themselves on the kit’s curves. Packs that carry data: a pack may hold a folder beside it (plugins/<pack>/), its files read at authoring time withctx.packFilefrom the editor’s own origin, offered to a plugin whosemeta.idis a shipped pack’s (tramme/<pack>, which the packs now declare) and to a project’s own copy; the data is never copied into the project. The assistant reaches the packs: the shipped packs’ nodes, tools and presets are found bylist_nodes { query }even when the project holds none (counted, not listed), a proposal that draws with one adds it to the project in the same undo step (the installed plugins’ path: the copy on first draw, the version recorded), and the system prompt names them in one line. One test for every pack:packs.test.tsreadsplugins/index.jsonand runs the shared checks on each pack it lists — registers, every node validates with its default props, and every title, label and description carries its French. - Stick figures pack: Pivot and StykAnimate-style characters in
plugins/styk.js. Thestyk.figurenode draws a rig of fixed-length segments (after StykAnimate’s “Blue” and Pivot’s default man, or any figure the project defines): theposeproperty gives each segment an angle relative to its parent, held key to key like Pivot animates, driven by an expression, or reaching a{ target: [x, y] }with two-bone IK (bendpicks the elbow or knee side) and stretching with{ a, l }; keyframed poses hold, the way Pivot’s frames do. Thestyk-figuretool lays a figure in the composition (the man, the plain black one, or one already walking — a 1 s walk cycle of eight held poses), and thestyk-figurecheck flags a pose naming a segment the figure does not have, an IK target the limb cannot reach, two targets on one chain, and a rig with a missing parent, a cycle or a duplicate id. - The / menu on the home screen: the direction box offers the tools and workflows as the message box does (the same menu, shared). A project started with
/namesends its words with that command, as the message box would; a tool named alone waits in the editor’s box with its form. - Native notifications in the desktop app: a question waiting for the user’s answer and the end of an assistant turn are told by the system’s notifications (Tauri’s notification plugin), the web view showing none of the web’s.
- Playback could start again from where it was paused rather than where the playhead had been brought, and play every sound twice or more at once, right after Play or when a loop wrapped: until the sounds had loaded, the frames still read the last playback’s clock (the audio context runs on while paused), which landed past the end, wrapped and started another playback over the first. The clock now starts at once, and a start overtaken by another or by a pause schedules nothing.
0.12.0 - 2026-10-21
Section titled “0.12.0 - 2026-10-21”- Time displacement: the
time.shiftnode reads a composition later in some places than in others: slit-scan along a side, a time ripple from the centre or the edges, or a liquid time in noise patches. It keeps a ring of past frames as a 3D texture and stays a pure function of time. - Faster blurs, shadows and glows: a layer’s Canvas 2D filters now run over its box, grown by what they spread, instead of the whole frame. The
effectsload case renders in 6.8 s a frame instead of 27.4 s on a machine without GPU raster, with the same pixels. An effect can say how far its filter spreads (canvas2d.reach); without it, the whole frame is filtered as before. - Installed plugins in every project: an installed plugin’s tools, checks, workflows, kits and presets are offered in every project. They run in the project’s sandbox, never on the page, and the project’s own names win. A project can turn one off (
meta.pluginsOff). When a layer, an effect or a modifier of one first enters a project, the plugin and its own files are copied into the project’splugins/in the same undo step. Its version is recorded inmeta.installedCopies, so the project opens the same anywhere, and a newer installed version is offered per project, never applied without the user. A project holding such a copy is always drawn through the sandbox. A plugin reaches only what it declared (meta.permissions): its network origins and provider routes through the newctx.fetch, and writes underassets/and its declared paths. It is stopped for the session after three failures in a row. The assistant’slist_nodestakes aquerythat finds the installed plugins’ nodes and tools, left out of its index, and the system prompt names the installed plugins. - Installed plugins: a Plugins section in the settings installs a plugin once on this device, from a
.jsmodule or a.trammepluginpackage (a zip of the module and its own files), picked or dropped. It asks first, before any of the plugin’s code runs: what the plugin brings, what it may reach and its API version. An update asks again only when it asks for more. Each plugin can be turned off or removed, and all of them can be exported as one backup and imported back. The plugins are kept in the desktop app’s folder, in a folder the user picks (Chrome and Edge, with the File System Access API), in the browser’s storage (made persistent where the browser allows), or on the private deployment’s server. A plugin’smetagrows anid, alicence, anauthor, ahomepageand itspermissions; plugins without them stay valid. - 10-bit exports:
tramme render --depth 10reads each frame at 16 bits from the compositor’s half-float frame, not rounded to 8, and writes H.265 Main 10 (MP4), ProRes 4444 (MOV), VP9 profile 2 (WebM) or 16-bit PNG; the browser’s export offers 10 bits for MP4 and WebM when this browser encodes them (asked to WebCodecs first: H.265 Main 10, AV1 or VP9 profile 2) and says when it cannot. Gradients made by the effects and the finish keep their levels; exports stay SDR. - Long jobs that resume: the video jobs run in chunks saved as they finish, say how long is left, can be cancelled, and pick up where they stopped. Two of them:
upscalemakes a picture or a video twice its size (Lanczos, lightly sharpened), andinterpolatemakes up the frames between a video’s frames (2 or 4 times as many, along their motion), saved as a copy linked to it (interpolated, a new optional field of an asset): a layer slowed under 1× plays the copy and slows smoothly instead of repeating frames. - Smoother skin, when asked: the
skintool finds the faces of a video (MediaPipe’s Face Landmarker, in the browser) and saves the skin of each as a mask video, eyes, brows and mouth left out;fx.smooth, a surface blur that keeps edges, softens the video through it, lightly by default. The landmarker joins the models of the settings (Faces). - Hesitations cut: the
fillerstool finds the “uh”s and “um”s a transcript leaves out (where a voice detector, Silero VAD, hears speech and no word is written; the ones a transcription model wrote too) and cuts them as the silences are cut, the transcript of the edit remapped and the captions reconnected. Each cut is listed with its moment, andrestoreputs any back by its number. Silero VAD joins the models of the settings (Where someone speaks). - A clean voice: the
denoisetool takes the background noise out of a voice (RNNoise, in WebAssembly, loaded when first used, faster than real time) and saves the cleaned voice beside the original, which stays (clean, a new optional field of an asset); the layer plays the two mixed by its Clean voice amount, 0.85 by default so the voice keeps its life. The check warns about a voice whose noise floor is high, and the assistant cleans such a voice before captions and sound design. - Parallel export:
tramme rendercuts the film into segments rendered at once by several pages of the same Chrome (as many as the machine’s cores and memory allow,--pages nto choose,--pages 1for one after the other), each encoding its own, then joins them without encoding again; the sound is mixed once over the whole film. The frames are the ones a single page draws, simulations included. - Components in the editor: an instance shows its component’s parameters in the inspector like a node’s properties (animatable, linkable), its overrides marked and removable, a button to open its component and one to detach it; any property of a composition becomes a parameter from its menu (Expose as a parameter), and the composition lists its parameters and how many instances use it. Components are marked in the compositions list, and kept in the library shared by the projects (
component-keep,component-use). - The assistant writes things once:
define_componentturns layers into a component and an instance in their place,instantiateplaces one or a whole distribution of it,detachturns an instance back into layers (the / menu has them too). The assistant’s guide asks for a component as soon as something repeats, and a new check, Repeated elements, points at layers written several times nearly the same. The section titles, keywords, lower thirds and end cards are placed as instances of a component of their look, their words as parameters: two keywords share one component. - The time field: the
timeFieldmodifier reads an animation later for some elements than for others, by rank (the old Offset, which it now runs), along a direction, by distance to a point or a layer, or by noise that can drift: a wave, a ripple, a liquid time, from one animation. A distribution takes one too (time), so a hundred instances become one wave. A modifier’s amount or seed can be keyframed and slides. - Distributions: a comp layer makes N instances of its component at once (
distribute), on a grid, a line, a circle, along a path or on another layer’s points, as many as asked or one per row of a JSON asset; each parameter is given by a rule (a value, an expression ofindex,countandrow, the palette in order or at random). Each instance has its rank, so the offsets and the noise of the modifiers keep working across instances. Expressions readindexandcounteverywhere. - Components: a composition that lists
params(each with its type, the properties it lands on and a default) is a component, and every comp layer holding it an instance with its own values (params, fixed or animated) and its own changes to any property inside (overrides); changing the component changes every instance. An instance can be detached into plain layers that draw the same. Styles are sets of properties defined once at the document’s top level and applied to any layer (styles); keyframed, a style is an animation played from where it is used. New optional fields of the document. - A Models section in the settings: the model each local tool runs (the cut-out of a person or of any subject, detection, depth, transcription) is named with its size and licence, and another can be chosen for this computer, among models whose input and output Tramme knows; detection, depth and transcription also take any model of the hub made for their pipeline, tried on a blank input before it is kept. A model whose licence forbids commercial work says so.
- The models in this browser, by hand: the Models section says whether each model is downloaded and how much it weighs, downloads it ahead of its tool with its progress, deletes it, and lists the models no tool uses any more with the space they take.
- Transcription without a server or a companion: the desktop app and the personal deployment transcribe in the browser itself when neither the server nor the local companion can, with the model chosen in the settings; the companion runs that model too (
TRAMME_WHISPER_MODELstill overrides it on its machine). - An asset made by a model says which: the cut-out’s masks, the pictures cut out, the depth maps, the people found, the tracks and the transcripts keep the models and versions that made them (
madeBy, a new optional field of the document); another model chosen later never changes them. - Voice effects: a sound or video layer’s voice can be pitched (in semitones, its length kept), or sound like a robot, a telephone, a radio, a megaphone or an echo, the same in the preview and the exports; with Keep the pitch, a voice at another speed or on a speed curve keeps its pitch.
- Proxies: the
proxytool encodes a lighter copy of a video (540 lines) that the preview plays instead, so a 4K or high frame rate file plays smoothly while editing; the exports keep the original. Importing a video this computer decodes too slowly offers one (measured on a second of it). Settings → Preview → Play proxies. - Stabilisation: the
stabilizetool takes the camera’s shake out of a video, smoothed or locked still, shot by shot, and the video layer zooms just enough for the whole clip to keep its edges out. - Scopes: a waveform and a vectorscope of the frame show beside the picture while a layer with a grading effect (LUT, curves, wheels, colour correction, key) is selected.
- Colour wheels:
fx.wheelspushes the shadows, the mid tones and the highlights toward a colour (lift, gamma, gain, each a wheel to drag in the inspector) and sets their levels. - Curves:
fx.curvestones a layer by a master curve and one each for red, green and blue, edited as points on a square in the inspector. - LUTs: a
.cubefile imported into the project (alutasset) grades a layer throughfx.lut, at a strength: a look, or the conversion of log footage. - Masks on any layer: drawn outlines that cut a layer, each added, subtracted or intersected with the ones before it, with its feather, expansion, opacity and invert, its path animatable like a shape’s (
masks, a new optional field of a layer); a Masks section in the inspector; their outlines are edited in the viewport with the path tools (drag a vertex or a tangent, Alt+click adds a vertex, Delete removes it), and a mask can follow a tracked object (Follow a track). Expressions read a track at another time too:track(layer, name, at). - Chroma key:
fx.keymakes a green or blue screen transparent, in light and in shade alike, with its tolerance, its softness, the spill taken out of the edges, a choke, and a matte view to judge it. Its colour, like every colour of the inspector, can be picked in the viewport with a dropper (the effect off while picking). - Transitions between shots:
fx.transitionon the incoming shot mixes it with the outgoing one over their overlap: crossfade, dip to a colour, push, slide, zoom, whip pan (both blurred along their move), a luma wipe from a grey picture, and a glitch. Their sounds cross with the picture (equal power), unless the transition says otherwise. In the timeline, a clip’s menu puts a transition on the cut before it, the two shots overlapping from their files’ handles (or saying how much is missing), and its band drags its length. The assistant reaches for one kind per film, cuts by default. GL effects also readuLayerTime, the time since their layer’s in point. - Speed curves: the speed of a video or sound layer can be animated; the file plays at the integral of the speed, so a shot slows into its moment and speeds out of it, the same in the preview and the exports. 0 freezes the frame, a negative speed plays backwards. Tracks, callouts and the sounds placed on what is seen follow the ramp, and captions follow the layer whose speech they show (
follow). The sound follows the curve too, its pitch with the speed. The curves editor has four speed presets for the selected video or sound: ramp in, ramp out, hero moment and bullet. - A file already in the project is not imported twice: importing it again from the assets panel, attaching it to a message for the assistant, or finding it twice among the sources of a new project gives back the asset that has it, and nothing is written again. Each imported asset keeps a hash of its content (
hash, a new optional field of the document). - An export says where a frame’s time goes: next to the
ms/frame,tramme renderprints the time per frame spent evaluating the document, drawing it, waiting for video frames, reading the pixels back from the GPU and waiting for the encoder, so a slow export tells whether the JavaScript, the GPU, the decoding or the transfer holds it back. - Load cases to measure the renderer:
tramme loadrenders documents that each push one part of a frame (400 animated layers, blurs and effects with motion blur, a 4K source video, simulations) and prints, per case, the time per frame, its parts and what holds it back;--jsonkeeps the figures and--beforecompares a later run with them, figure by figure.
Changed
Section titled “Changed”- The Models settings, regrouped: the tasks on the picture, then those on the sound, one line each with the model chosen, its size, licence and whether it is in this browser, and a single button to download or delete it. A model hub id is entered once, for the task picked beside it.
- Faster evaluation of many elements: a frame of 400 instances of a component under a time field is evaluated in about 12 ms instead of 29 (the field read once rather than per instance, the modifiers’ settings, the curves and where each property lives found once, the readings at other instants shared within a frame).
tramme loadhas aninstancescase. - Two layers showing one video at different moments read it at once: a crossfade between two shots of one take, a split screen or the clips of a cut that overlap each read forward on a decoder of their own (three per file at most) instead of making one decoder seek at every frame. On a crossfade within a 4K file, the time spent waiting for video frames drops by three quarters.
- In the preview, a video played at another speed kept its pitch while the exports changed it: the pitch now goes with the speed everywhere.
- An export of two layers playing the same video at different moments could draw one of them with a frame of the other: the shared decoder dropped the first layer’s frame when the second one’s came.
tramme stillandtramme renderfailed on a project with its own plugins (“unknown node type”): the sandbox was never asked to load them. A frame drawn by the sandbox also came out upside down, in the CLI and in the editor’s preview and filmstrip.- The cut-out of a person ran the small general network (U²-Netp) instead of U²-Net trained on people: the model hub repository it read held the wrong file. It now downloads rembg’s human segmentation weights (176 MB), which keep the person and leave the objects they lean on. Whisper large v3 turbo, in the settings, now comes from the export that can time the words; the former one could not transcribe for the editor.
0.11.1 - 2026-10-19
Section titled “0.11.1 - 2026-10-19”- The home screen’s format choice (16:9, 9:16, 1:1, 4:5) drew each format’s rectangle above its ratio instead of beside it, on a computer as on a phone: since 0.11.0 the label of a segmented control is an element of its own, and the rectangle inside it broke the line.
- On a phone, a project of several shots pushed the name and the export out of the top bar: the composition picker stayed in it. It leaves the bar under 900 px with the format, and the ⋯ menu now shows from that width, so both stay at hand (between 760 and 900 px the format had no way back).
- On a phone, the home screen’s brief lines up with the films under it, and its format choice spans the box’s width in four equal parts; it sat indented, the formats left-aligned under the other buttons.
- On a phone, the settings’ search spans the dialog’s width.
0.11.0 - 2026-10-19
Section titled “0.11.0 - 2026-10-19”- The editor installs as an app: PNG icons (192 and 512, a maskable one for Android, Apple’s) drawn from
icon.svgbyscripts/app-icons.ts, a complete manifest, and an “Install the app” button on the home screen when the browser offers it (Chrome, Edge, Android; on an iPhone, Share → Add to Home Screen). - The installed app opens offline (personal mode): the service worker keeps the editor’s own files of each build — the page, its bundles and fonts, the sandbox, the icons — in a cache named after the build, the previous builds’ dropped. The projects are in the browser already.
- Each settings section says what it is for, under its title, as the Preview’s did.
Changed
Section titled “Changed”- The editor fits a phone: the top bar keeps the name, the view, undo, redo and export (as an icon), and moves the format, the frame rate, the versions, the help and the settings to its ⋯ menu, which was never shown; the atelier’s tabs are one bar across the bottom, the panels stopping above it; the transport drops the first and last frame buttons and its Timeline and Curves tabs keep their icons; the timeline’s names take a share of the screen, not the width remembered on a computer.
- The settings’ search shows a whole section when its title matches; its description no longer counts.
- The preview could stay black, never starting: the renderer waited for every font of the page, and Chrome sometimes leaves one of the interface’s (Geist Mono) loading for good. The page’s fonts are now waited for 3 s at most, once; the document’s own fonts are still loaded one by one.
- “plugin … did not load in the sandbox” on opening a project: a second load asked while the first was under way (a turn resuming as the project opens) found the plugin already asked and failed. A load under way is now waited for, a refusal gives the sandbox’s reason once and is tried again when the file changes, one broken plugin no longer keeps the others out, and a sandbox whose worker failed is made again.
- The providers’ settings in personal mode follow the editor’s theme and language: the vault’s page read its preferences before the editor’s were kept (the production build puts them in a chunk shared with the editor). Its background, its titles and its empty state now match the other panes.
- The labels of the segmented controls (the view switch among them) hide on narrow bars as intended: the label was bare text the rule could not reach.
- On a phone, the studio’s picture fills its stage: a rule of the atelier shortened it and left an empty band.
npm run dev:personalworks again:wrangler devgave every request the address of the deployment’s routes, so the Worker could not tell the editor from the vault. The dev server runs on a copy of the config without them.
0.10.0 - 2026-10-18
Section titled “0.10.0 - 2026-10-18”- The command line’s renders run in the sandbox: the runtime page the CLI drives evaluates and draws whole frames in the plugin sandbox when the project has plugins — stills, the assistant’s previews and the frame capture included;
?sandbox=0opts out. Step 4 of docs/evaluator-sandbox.md. - With the sandbox flag on, the plugins’ modules no longer load on the page at all: the registry takes its nodes, effects, modifiers, tours and translations from the sandbox’s declarations (schemas and the same sandbox-backed wrappers), and the asset store skips the plugins’ files; the flag flips at runtime and the registry is rebuilt from the other source. Step 5 of docs/evaluator-sandbox.md.
- The stills and the web exports can run in the sandbox (the same flag, when the project has plugins): the PNG sequence, GIF, WebM and MP4 ask the sandbox for each frame — videos decoded on the page first, one picture back, read as pixels or blitted for the capture-based MP4 encoder — and the stills (assistant, contact sheets, storyboard) do the same for their JPEGs.
- The preview can run entirely in the sandbox (experimental, off by default): a setting makes the viewport blit the sandbox’s finished frame — modifiers, Canvas2D effects and simulations evaluated in the worker, video frames still decoded on the page, the checker behind transparency as anywhere. With the flag on, a plugin’s code never runs in the page. Step 2 of docs/evaluator-sandbox.md.
- The sandbox renders whole frames: the per-project worker now owns an Evaluator, the built-in registry and the plugins’ modules, evaluates a composition at a time — modifiers applied, Canvas2D effects stacked, simulations stepped inside — and returns one finished picture over a transferable. The frame primitive of docs/evaluator-sandbox.md (series step 1); the preview’s flag comes next.
- A design note on moving the evaluator into the sandbox (docs/evaluator-sandbox.md): why the last four page-side pieces of plugin code (modifiers, Canvas2D effects, the stepping of simulations, the module’s load) are one move and not four patches, the options priced, and the series that ships the whole-frame sandbox behind a flag.
- 3D models join a project like any material:
.glband.gltffiles are accepted by the home screen, the chat’s attachments and the sources import — they becomemodelassets, the panel lists them under their own label, “create a layer” places amodel.3dlayer bound to the file, and an attached model tells the assistant where it is and how to place it. - The plugins’ geometry crosses the sandbox: a node’s outline is built in the sandbox with a recording Path2D and arrives with its picture as SVG path data (clips and the viewport rebuild it), its viewport handles come as plain data, and its vector export (
svg,lottie) is computed in the sandbox and primed before a conversion reads it — none of the plugin’s geometry code runs on the page. - An archive’s plugins are validated in the sandbox: the import imports them in the per-project worker and validates the document against their declarations — the page never runs their code at import time (an accepted archive used to be imported on the page just to be validated).
- The sandbox draws the plugins’ nodes: a node that needs no synchronous geometry on the page (no
path,handlesor vectorexport) is drawn in the per-project worker — evaluated props, frame numbers, simulation states and the other layers’ data cross as plain messages, and one transferred picture comes back per layer over its bounds; the first pass of a frame defers, so stills and exports keep waiting for the exact picture while the preview keeps the last one. Modifiers, Canvas2D effects, simulation stepping and geometry nodes stay on the page, documented (stage 2 of docs/plugin-isolation.md). - The editor runs the plugins’ tools and checks in the sandbox: the preview, the stills and the browser exports load plugin modules with their authoring code left out, and the registry carries sandbox-backed entries instead —
use_tool, the/menu and the checks call them the same way, with no page rights on the other side (stage 1 of docs/plugin-isolation.md). - A plugin sandbox: a per-project browser worker where plugin modules can be imported and their tools and checks run with no page rights — the protocol, the worker (its own bundle, its network narrowed to its own origin), the page-side host that bridges files, writes, stills, transcripts and aborts, and the registry wrappers, with end-to-end tests of the pair (docs/plugin-isolation.md, stage 1).
- The code question names what each plugin brings: the import’s inventory reads each plugin module’s text (without running it) for its declared exports — nodes, effects, modifiers, tools, workflows, checks, kits, presets, tours — and the dialog lists them per plugin file, so what is accepted is known before it runs.
- A design note on isolating untrusted plugins (docs/plugin-isolation.md): the options (the main thread as today, a dedicated worker with OffscreenCanvas, a strict CSP with a reduced API, a Wasm/QuickJS sandbox), their costs, what each takes from the plugin API, and a staged recommendation — the code moves only once the author picks.
- 3D models come in by every door: the Assets panel imports .glb and .gltf files (they were refused as an unsupported format) and lists them under 3D models, with “Create a layer” placing a
model.3dsized to the composition; the chat’s and the home screen’s file pickers offer them too.
0.9.0 - 2026-10-18
Section titled “0.9.0 - 2026-10-18”- A compressor per sound (
compress, 0 to 1): one DynamicsCompressor between the equaliser and the gain in the one mixer — the loud moments brought down (a voice kept level, a hero that never jumps out), harder as the amount grows, in the preview and every export alike. - Four new commands:
/transcript(the words of a sound or a video, read with the moments that matter),/cut-silences(a newsilencestool cuts a talking video on the gaps of its transcript — hesitations shortened, the spans laid back to back),/beats(the edit lands on the beats and sections), and/still(a newstilltool saves a picture of the composition at a moment as an image asset). - A low contrast check: the free-space analysis now carries each cell’s luminance, and the check weighs a text’s ink (its colour, its opacity) against what sits under it — a picture through the analysis, or the composition’s background — and warns when the contrast ratio falls under 2.5:1.
- Effect-stack presets: a preset can now be a stack of effects applied to every selected layer at once (the add menu pushes it). Built-in: cinematic tone, dreamy glow, VHS, and a dark shadow plus halo that keeps type readable over anything.
- 3D models placed by node matrices load: a node’s matrix is read as its translation, rotation and scale (glTF’s own Duck, BrainStem and many exports used to be refused).
- A cropped video (fit cover, the default, the one an imported video takes) drew from its layer’s centre instead of around it: only a quarter of the picture showed, pushed to the bottom right. The picture is centred on the layer again, around its focal point.
- One clock and one framing for a video everywhere: the tracks, the callouts that follow them, the checks and the sound moments read a video at its start, speed and loop and through its focal point, as the picture is drawn (they assumed normal speed, no loop and a centred crop).
0.8.0 - 2026-10-18
Section titled “0.8.0 - 2026-10-18”-
Fonts in the style kits: each built-in kit names its typeface (Newsreader for Editorial, IBM Plex Mono for Hairline, Archivo Black for Punchy, Karla for Calm, Space Grotesk for Neon). Applying a kit fetches its woff2 once, keeps it in the project as a font asset, and the recipes write in it; the project keeps its own font if it has one.
-
Six new recipes, laid out as ordinary editable layers like the others: a map journey (a line travelling stop to stop on a map, revealed in step with the riding dot), a word-by-word quote with its author line, a logo reveal (iris, wipe or rise) that holds, a list that ticks in (tick, number or dash markers), a timeline that draws itself across the frame, and a split screen of two or three sliding panels.
-
A background removal tool (
remove-bg): the U²-Net matte run once on a picture becomes the alpha of a PNG saved as a new image asset, placed as its own layer — titles and graphics pass behind the subject. -
A free space tool (
space): a frame read as a small grid of how busy each cell is (edges, robustly scaled), saved as data with the clear sides and the largest clear rectangle in fractions of the frame — where a title or a caption block fits without covering what matters. -
A lip sync tool (
lipsync): the words of a transcript drive a drawn character’s mouth — the nine classic shapes (closed, M/B/P, F/V, A/I, E, O, U/W/Q, L, other) written as keys on a sequence’sdrawing, closed between the words, remappable with a mouths map. -
Three simulated nodes: a rope (tied to the layer’s origin, pulled towards another layer, swinging in the wind), a cloth (pinned along its top edge, falling and catching a wind that breathes) and a flock (boids that steer together across the frame, deterministic on its seed). Stepped frame by frame from the layer’s in point, so exports and previews agree.
-
A 3D model node (
model.3d) and itsmodeltool: a .glb (glTF 2.0) joined to the project is drawn in 3D on the node’s own WebGL2 context — rigid animation of its parts, a turntable spin, an animatable explode, studio, sun or flat light — with a lean parser of the format (packages/nodes/src/gltf.ts, no skinning: skinned meshes draw at rest). Model files join a message or the sources like any material. -
A WebGL2 service for node plugins (
render.gl): a node gets a context of its own, kept from frame to frame (its compiled programs, its uploaded meshes), sized to its bounds and drawn into the layer; a failure lands in the error bar like any node’s. -
Depth (
depthtool): the depth map of a photo or a video, read in the browser (Depth Anything v2 small, WebGPU or the processor), saved as a grey file (bright where near) played by a hidden layer, and wired:fx.parallaxmoves the layer the way the composition camera would, a photo also takesfx.depthBlur. -
Photo in 2.5D (
photo-2.5dtool): one pass that reads the depth of a still photo, adds the composition camera with a slow drift and scales the photo past the relief’s widest stretch, so nothing shows at its edges. -
Two layer effects behind them: Depth parallax (
fx.parallax, a per-pixel relief from the map, linked to the camera) and Depth blur (fx.depthBlur, a depth of field with an animatable focus for focus pulls). -
Two light themes, lin and porcelaine, beside papier: the picker now draws eight of them with their own colours, four to a row (the dark ones above, the light ones and system below), and the window bar and the page’s colour-scheme follow.
-
A filmstrip along the video clips: the clip shows its film as small thumbs, decoded in the background from the preview’s own decoder (one at a time, a thumb every quarter second shared by the clips of a file, nothing while the film plays, a small memory of the recent ones). The thumbs follow the cut and the speed.
-
The videos’ Speed (0.25× to 4×), the pitch of their sound with it, the sound of the exports and of the preview alike; trimming a video’s head carries its start at its speed.
-
The fades of a video or a sound as two handles at the clip’s top corners: drag one, the fade follows, snapped to frames.
-
The markers at the keyboard: M drops one at the playhead, 1 to 9 jump to the markers in order.
-
A crossfade with the layer under it, from the clip’s menu: opacity keys on both over the time they share. An opacity already animated is never touched.
-
Loop the section to the end, from the clip’s menu of a video or a sound: what plays past the section starts over from the start in the file (the sound loops natively in the mixes; in the preview a looped video’s sound is close but not exact — the exports are).
-
The adjustment layer: it draws nothing of its own — its effects apply to everything under it in the stack (a grade over a scene, one blur for a set). A composition without one pays nothing.
-
The project’s versions: the clock beside the save state keeps instants of the project (the document saved first, so a version says exactly what is on screen), each restorable from a list, each removable.
-
The home screen’s search: from six films on, a field at the right of “Your films” filters the cards by name.
-
A text over detail check: once the free space tool has read a frame, the checks warn when a text sits on its busy cells (about a third of the text’s area or more) and point at the clear rectangle the analysis found, so a title moves where the picture is quiet.
Changed
Section titled “Changed”- The home screen’s cards keep one thumbnail ratio (16/10, the film filling its box cropped): the rows stand as tall as each other whatever the film’s format, where a vertical film used to stretch its whole row.
- The lines between the atelier’s panels show at rest instead of hiding in the gutters, each says what it does (the chat’s: “drag: the chat grows or shrinks”), and the tours’ “The tricks” has a step on them.
- The tours’ “The tricks” also tells the clips’ thumbs and fades, the crossfade and the loop, the videos’ speed, the markers at the keyboard and the versions.
- Under the hood: the free space tool reads its video straight at the grid’s size instead of decoding a full frame for a handful of cells, glTF meshes are parsed once per node (three reads before), a node’s own WebGL canvas is capped at 2048 px (a zoomed node used to ask the GPU for a canvas as big as the frame) and only grows, shared by the type’s layers at their own sizes instead of reallocating its buffers every frame, a photo’s depth map is saved at 1024 px at most (4096 held no more depth than the model reads), the kits’ fonts are pinned to one version so every film gets the same file, the transcript the tools read is picked in one shared helper, and document attachments tell the assistant their size.
- The cloth’s Sway is a period in seconds, 1.6 by default: the rhythm the wind had before it was read as one.
- Clicking Export while an export runs no longer closes its progress, and a finished file is no longer lost by a click beside: it waits in the export popover (a small dot on the button says so) with its save buttons.
- The settings’ section descriptions sat unstyled on the cards’ top edge, half outside; the theme picker crushed its previews to pills and wrapped eight themes as six plus two.
- The storyboard’s play button turned into a bare disc when playing: its pause icon drew nothing (a stroke path forced into a filled button).
- The examples’ cards stood upright, their thumb a small centred picture: they are horizontal cards again (thumb beside the text), as designed.
- Lip sync: a mouth holds its shape for the word instead of snapping shut between letters (each key now holds until the next), the mouth closes again after the last word, and the transcript’s language drives the phonemes, so a French line is no longer mouthed as English.
- The free space analysis measures its grid’s border cells too (the frame’s edges were read one cell off, held at nothing).
- The recipes’ hidden pieces do their work again: the logo reveal’s iris and wipe really apply their mask (it was left out of the matte), the map journey’s line is revealed by its rectangle, and a kit whose typeface cannot be fetched still applies its colours. The wipes and the timeline line grow from their starting edge, and the journey reveals from where it starts, whatever way it runs.
- The crossfade fades the layer that ends first, whichever of the pair it is; it is not offered when one clip holds the other (either would vanish while it plays alone), and it works on a layer without a transform of its own.
- Three of the five kits’ fonts (Newsreader, Karla, Space Grotesk) could never be fetched: the font CDN keeps variable fonts under another address.
- The recipes’ entrances squeeze before their fade out when time is short (a slow kit, a one-second piece): their keys used to come out of order and the whole piece was refused.
- Depth: a depth video follows its source’s trim and speed (it played the file from its start, ignoring the clip’s start and rate), the layers the tool adds copy the source’s playback settings, and photo 2.5D no longer grows the photo a little more every time it runs. A photo’s depth of field reads the hidden map layer (it named the map’s file, which the document refused, so it never drew), its parallax survives the depth of field joining it, and its framing is its own scale times the margin, once, whichever tool runs first (an inset stays an inset).
- A looped section sounds and previews as it should: the mixes wrap what plays past the section back into it (the raw offset used to run on into the file’s remainder), and the preview seeks inside the section at the clip’s speed. A section that starts past its file’s end no longer fails the mix.
- The tools that pick a media by default (logo reveal, split screen, background removal, 3D model) no longer take an asset a tool made beside it (a depth map, a cut-out) in its place, and they take the selected layer’s own media, a 3D model’s included. The depth tools no longer skip a layer of yours whose name holds “-depth”.
- The timeline’s filmstrip no longer hangs the tab on a clip narrower than one thumb (it asked for thousands of canvas slots), and it reads a video layer’s static start instead of breaking on it. It no longer decodes forever when the clips on screen ask for more thumbs than its memory holds, and the last thumbs of a batch show without waiting for another repaint.
- The free space’s clear margins measure inward from each edge (they counted cells along it), and the text-over-subject and text-over-detail checks read a video at its speed and its loop.
- Running background removal again refreshes the cut-out it placed instead of adding a second one.
- The versions: restoring one no longer meets the “unsaved changes” guard on reload, and a version pushed out by the thirty kept is deleted from the project instead of piling up unseen.
- 3D models: meshes without index buffers load (their vertices are read in order), the whole model’s bounds follow each part’s transform, so a rotated, scaled or offset part no longer falls outside the frame, the turntable spin turns the model about its own centre (one authored away from the origin used to orbit instead of spinning in place), and a replaced model file is read again.
- The simulated nodes: the rope reaches its target from wherever its own layer sits (the target was read in the composition while the rope lives in its layer) and
length 0keeps the distance it starts with instead of tracking the target’s every move; the cloth’s wind breathes at the period the field promises (it played as a frequency, too fast at the default). - Background removal places the cut-out over its source picture, with its position, scale, rotation, crop and span, instead of centred in the frame.
- The keyboard: M and 1 to 9 answer only when no modifier is held, so the browser’s own shortcuts keep working in the atelier.
- Map-journey stops written “0.2, 0.3” (spaces after the commas) parse as pairs instead of being dropped, and the recipes no longer crash naming a layer whose asset has gone missing.
0.7.1 - 2026-10-18
Section titled “0.7.1 - 2026-10-18”Changed
Section titled “Changed”- The studio’s notes panel is resized like the atelier’s panels: a handle between the film and the panel, from 330 to 640 px, remembered from one session to the next.
- The studio’s note box grows to four lines, then scrolls; the film keeps the room of the box at its tallest, so writing neither shrinks it nor covers it.
- The model menu in the studio’s notes panel was crushed to nothing: it keeps its room, its name shortens first, and on a narrow panel the route label (Companion) gives way instead of the buttons, the new conversation’s included, being pushed out of the panel.
0.7.0 - 2026-10-18
Section titled “0.7.0 - 2026-10-18”- The studio, the default view of a project: the film in front, directed by notes. A note is written in the box under the picture, pinned to a moment or a place of the frame if needed, and the assistant answers with a take shown on the picture, kept or set aside. The storyboard below shows the scenes with their frames, the sound and the notes at their moment; a click on a scene puts the notes on it. The Direction panel holds the brief (subject, tone, rules), the look and the material of the film. The former layout stays as the atelier, one switch away in the top bar and the settings.
- The Transcribe button: on a sound or a video joined to a message, on the material of the film, in the assets, in a new “Speech” section of the inspector of sound and video layers, and in their menus. It reads the same state everywhere: to transcribe, under way, transcribed.
- The timeline’s own menus on the right click. On a clip or its name: split at the playhead, trim the start or the end to the playhead, bring it to the playhead, then the layer’s menu (the same as in the layer list). On an empty place or the ruler: the playhead or a marker there, end the composition there or at its content, add a layer, select all, the whole timeline in view. On a marker: go there, delete it. On a keyframe: go there, its curve.
- Guided tours “The tricks” (atelier: timeline zoom and lasso, snapping edges, cutting a video, the right click, scrubbing and arithmetic in fields, expressions and modifiers, the keyboard, export) and “Speech and transcription” (both views: where to transcribe, what the assistant does with the words). The editor tour’s timeline step tells the new menus.
- The interface is bundled with its fonts (Geist and Geist Mono, OFL-1.1): it looks the same on every machine, offline included.
- A theme of previews in the settings: each of the five themes (studio, obsidienne, carbone, crépuscule, papier) is picked on a small picture drawn with its own colours, and “système” follows the computer’s light or dark setting; papier joins the site’s light palette.
- The lists of choices (a project’s format, the frame rate, a property’s choices) open the editor’s own menu: a line of detail can sit under a choice, the chosen one carries a check, and the keyboard works through them (arrows, Enter, Escape, first letter). On a touchscreen the native list stays.
- A take announces itself with a clapperboard: a
clapicon on its pill and its card, “Prise N” in the theme’s accent.
Changed
Section titled “Changed”- The landing page follows the app: the studio first (“Motion design, directed in words”, a new Studio section with its notes, takes and direction), then the atelier with its timeline menus; new pictures of both views in the paper and studio themes; the site’s colours are the editor’s paper and studio tokens; its words are a motion designer’s (keyframes, curves, wiggle and loop, a style named once; the JSON and the terminal are links for the curious, no longer the pitch); sections are surfaces on the ground with gutters instead of hairlines, the top bar a floating pill, and the glows are gone. What the page loads is unchanged but for the studio’s picture, lazy.
- Nothing is transcribed on its own any more: not a project made from a video or from sources, not a file joined to a message. The user starts it with the Transcribe button; when the assistant needs the words of a media not transcribed yet, it asks first in the conversation (a turn left alone never asks, and works without them). The project’s first greetings say so.
- Dragging the left edge of a sound or a composition cuts its head off like a video’s: what follows stays in place (its start in the file carried, at its rate or speed).
- The browser’s menu no longer opens on the timeline, the transport, the curves or the storyboard (it stays in text fields), and a right press on the ruler no longer moves the playhead.
- One art direction for the whole application, built only on the theme’s tokens (the reference board is
docs/design/board.html): Geist everywhere (13 px base, Geist Mono for timecodes and values), text buttons as pills, icon buttons as 8 px rounded squares, fields without borders that take a 2 px accent ring on focus, panels and cards as 14 px surfaces set on the background and separated by 8 px gutters instead of seams, dialogs at 20 px over a blurred scrim. No colour is written outside the theme files any more; the playhead, the selection and the focus are the accent’s, never a red of their own. - The studio is dressed like the rest: the violet of the assistant, its gradients, halos and sparks are gone. Tramme at work is its mark breathing and a 2 px accent ring around the picture; the notes’ numbers, the pins and the stage tags are the theme’s accent; the storyboard’s sounds are drawn (music neutral, voice accented, effects as ticks, heroes warm); the playhead is the same line in the studio, the storyboard and the timeline.
- The atelier is panels on a background: the left panel, the viewport, the bottom and the inspector are rounded surfaces in gutters, and the resizers hide in the gutters (an accent line while dragged). The viewport’s toolbar and banners float as pills over the picture; the transport reads its time in mono; the timeline’s clips keep their layer’s colour and the chosen one takes an accent ring; the curves sit on a soft surface with their presets in a floating pill. On a phone, the tabs float in a pill above the safe area.
- The assistant speaks in one thread in both views: the notes with their number, the work as stages (its steps one click away) and the takes as cards, in the studio’s side panel and in the atelier’s assistant alike — the bubbles are gone.
- The settings’ rows are grouped in cards, one section at a time under its title; the navigation reads as rounded lines. The guided tours follow the new shapes, and every
data-tourmarker stands where it was. - The home screen’s cards show each film at its own aspect ratio on the picture’s stage colour: a vertical film no longer leaves empty bands beside its preview, and the examples follow.
- A field focused by the keyboard showed a doubled outline: the global focus ring painted on the field’s inner input as well as on the field itself. Text controls now answer with their container’s ring alone, and sliders and colour swatches keep a thin one.
- The projects’ thumbnails left see-through bands (a checkerboard) beside vertical films: the thumb now takes the film’s aspect from its manifest.
0.6.0 - 2026-10-11
Section titled “0.6.0 - 2026-10-11”- Markdown documents (
.md,.markdown) come in with the sources now: dropped on the home screen, chosen with “From sources (files)” or a whole repository folder, or joined to a message. The assistant reads them whole with the sources tool (a long one continues withread_file), the way it reads a PDF page by page; a folder’sREADME.mdalone is enough to open a project from its sources.
Changed
Section titled “Changed”- The local companion runs the Antigravity CLI (
agy, a Google login) in place of the Gemini CLI, which Google retired for personal accounts on June 18, 2026. The model menu offers it as “Antigravity”, with the models it lists for the login (agy models: Gemini 3.1 Pro, Gemini Flash, Claude…), apart from the Gemini models of an API key; its default model takes an effort level. It runs with a home of its own under~/.tramme/engines/antigravity, so the user’s plugins, skills and MCP servers stay out; it gets Tramme’s tools, and of its own only the reading of the images joined to the message. A model chosen for the Gemini CLI becomes Antigravity’s default.
0.5.0 - 2026-10-11
Section titled “0.5.0 - 2026-10-11”- Importing a
.trammeproject that carries code — plugins, or expressions — now asks first, listing what it would run (the plugins with their file and size, the expressions with where they are). Nothing runs before the yes, and a refusal writes nothing. The shipped examples skip the question. - With a finger, a long press opens the same menus as a right click: a keyframe’s curve and delete, the layers, the compositions, the assets, the tokens and the project cards. A press held still never moves a key or a layer.
- Dragging over the timeline’s tracks or the curve editor’s background draws a lasso that selects the keyframes it covers, across layers and properties. Shift adds to the selection, Ctrl/Cmd flips it, and a selected group moves in one undo entry. With a finger the drag still scrolls.
- A path’s vertices and tangents are manipulable in the viewport, for any node that declares a
pathproperty: drag a vertex (its tangents follow), drag a tangent with Shift held to keep the two mirrored, Alt+click the stroke to add a vertex, Delete to remove the selected one. An animated path gets a keyframe at the current time. The anchor cross drags too: the layer stays put on screen (the position compensates), Alt moves the anchor alone, and an animated or driven transform refuses with an explanation. - An onion skin for drawn animation: with a sequence layer selected, the toolbar’s onion button shows the previous drawing in red and the next in green over the picture, following the playhead at rest (hidden while playing or dragging). Never part of the document or the exports.
- Shorts: the title of each short lands with its first sentence (not at a fixed 0.2 s), each passage of the plan takes a strong word (keyword) that pops on screen the moment it is said — a word never said comes back in the answer — and a project with a brand (the plate and ink tokens) gets its progress bar and end card, the card lengthening the short. The build answers with a contact sheet of the shorts, a one-line check summary per short, and the export panel offers all the shorts at once, exported one by one, named after their titles and kept in renders/.
- A three-band equaliser on every sound (Sound layers and the sound of videos):
eqLow(shelf at 120 Hz),eqMid(bell aroundeqMidFreq, 200 Hz to 8 kHz) andeqHigh(shelf at 8 kHz), in dB. A band left at 0 builds no filter, so an untouched mix sounds exactly as before.
Changed
Section titled “Changed”- The home screen’s header is one door: a single New project button opens every way to start — blank project, a video, sources from files or from a folder, a
.trammeor Lottie file. Dropping a file on the page opens it as before.
- The curve editor drew no curves: the path was built with a
Wwhere anLwas meant, so keys and handles were there but the line between them never appeared. The background’s click and lasso also stop being eaten by the grid and the curves themselves.
0.4.0 - 2026-10-10
Section titled “0.4.0 - 2026-10-10”- Sound that follows the picture: cues read from the animation’s own timing (cuts, moves at their fastest, landings, appearances, about one hero in four seconds), placed on with
on: heroes, cuts, moves, lands, appears; a hero stacked from several sounds (sound: "a+b") with the music stopping before it and thinning out into it;sound-findbrings CC0 recordings from Freesound (through Openverse), judged automatically, into your library with their credit;mixbalances each effect against the music and voice band by band;creditswrites where each sound comes from. The sounds placed go in aSoundgroup. - Every export is mastered: a composition’s
soundsettings bring it to a loudness (-14 LUFS by default, BS.1770) with its true peak under -1 dBTP, and give its effects one shared room. Audio layers say theirrole(effect, music, voice, ambience),weight(support, hero) and what they underline. The preview plays the same master. - The check measures the mix: the master’s loudness and peak, each effect on its cue and heard over the bed, the music under the voice, unplanned dips and silences; it shows a picture of the mix and lists moments to check by ear.
- ElevenLabs voice-overs with Eleven v4 by default, and v4 Turbo, v3, Multilingual v2 or Flash in the Sound settings; the style of a voice-over (an accent included) becomes an audio tag on v4 and v3. Music with
music_v2_5. A voice picker in the Sound settings and avoicestool list the account’s voices and the shared library’s, filtered by language and accent. - Fold or unfold every group at once (layers and timeline, one state for both; Alt+click folds a whole branch), and find a layer by its name.
- Several clips selected in the timeline (Ctrl+click, Shift+click, a band drawn in an empty part, Ctrl+A) move together; moved edges snap to the playhead, the markers and the other clips (Shift held: free).
- Waveforms in the sound clips of the timeline, and a solo button that plays one sound alone in the preview.
Changed
Section titled “Changed”- When the assistant applies its changes by itself, it no longer stops on a question: paid generations count against an allowance per turn (Sound settings), and it decides what a sensible choice answers instead of asking. A question asked during a turn shows in the conversation, and the user is told when away.
- The eye of a hidden layer and the clip badge keep their columns in the layer tree.
0.3.0 - 2026-10-10
Section titled “0.3.0 - 2026-10-10”- “From sources” takes a whole folder, chosen or dropped, its subfolders walked through. A kit among the files (a
brief.jsonof kindtramme-kit, as an agent writes it from a project’s repository) sets the project up: its name, its colours and curves as tokens, the fonts it names as font assets, its brief; the whole kit stays atassets/sources/kit.json, its paths pointing at the files as imported, and the assistant reads it first.
- An SVG with a viewBox and no size of its own (most logos) no longer stops the preview and the renders: it is drawn in its viewBox’s proportions, 2048 px on its longest side.
0.2.0 - 2026-10-09
Section titled “0.2.0 - 2026-10-09”-
The local companion runs Codex (a ChatGPT login) and the Gemini CLI (a Google login) besides Claude Code: it finds them on the computer, the model menu offers them (“ChatGPT (Codex)”, “Gemini CLI”), and they reach Tramme’s tools as an MCP server held for the turn, with no shell, files or web of their own. Each keeps its session for the next message; switching agents midway hands the conversation over as text.
-
The assistant’s access puts the AI accounts first: with nothing connected, its panel offers to connect Claude, ChatGPT (OpenAI) or Gemini, and the local companion folds under it (never offered on a phone). When the chosen model cannot be reached but another AI is connected, its strongest model is taken and the user is told. The settings list the providers before the model and the companion.
-
Projects from sources: “From sources” on the home screen (or several files dropped on it) brings documents (PDF), pictures, videos and sounds into a new project (
assets/sources/). Thesourcestool lists them on a contact sheet and reads each one (a document’s pages as text and pictures, a video’s frames with what is said); the/analyzeworkflow reads them all, writes what it learned in the brief (about,sources) and proposes directions for the video before building. PDF documents join the project format and can be attached to a message. Tool contexts gainfiles()andfileUrl(path). -
Personal mode, a public deployment without accounts (
npm run deploy:personal, docs/deploy.md section 8): projects stay in each visitor’s browser (IndexedDB, served by a service worker with the same routes as the Worker), keys in a key vault of another origin that the editor and the plugins cannot read, and the browser calls the providers itself (a relay that keeps nothing for those that refuse calls from a page). The server keeps nothing. -
@tramme/api: the storage and provider routes shared by the Worker, the service worker and the key vault, with a storage contract every bucket passes (R2, IndexedDB, memory). -
Example projects “Launch film” (45 s on the beat, nested compositions, a 2.5D camera, sound-reactive motion, music written as code) and “Showreel” (made by the assistant). “Hello”, “Night sky” and “Road trip” leave the examples; the first two stay as test fixtures.
-
Plugin tools: a project plugin can export
toolsthat the assistant runs withuse_tool(analyses, layouts, generators). A tool answers with text and images and may propose changes, which join the assistant’s proposal. -
Notes for the assistant (
ai: { when, avoid, example }) on nodes, effects, modifiers and tools;list_nodesandtramme nodesnow list modifiers and tools too. -
Chat commands: typing
/lists the tools and workflows (/captions,/title,/keyword,/lower-third,/dress,/review, and those of the project’s plugins). A tool with its form filled runs at once, without a model; words after the command hand it to the assistant. -
Plugin workflows: a project plugin can export
prompts, instructions for the assistant picked from the/menu. -
Quality checks: text too small, too brief or past the safe zone, overlapping text, text crossing an element, crowded entrances, still stretches. The
checktool (assistant and/check) runs them and shows a contact sheet of the key moments;motionshows a strip of frames to judge a movement. Plugins add their ownchecks. -
Recipes:
kinetic-title,bar-chart,statandtransitionlay out whole animated pieces as editable layers; style kits (editorial, punchy, calm, neon) set the colours, curves and pace they follow. Plugins add their ownkits. -
Perception tools:
beatsanalyses music (tempo, beats, bars, sections, loudness per band),shotsfinds the cuts of a video,subjectsfinds the people in a video or an image (a small model run in the browser),paletteturns the colours of a picture into tokens. -
Following the music: the
reactmodifier andaudio()in expressions make any property move with the beats, bars, hits or loudness of an analysed sound. -
Check
text-over-subject: warns when text covers a face, once the people are known. -
Text behind the subject: the
cutouttool (assistant and/cutout) cuts the person, or the main subject, out of a video layer with a small model run in the browser, saves the matte as a mask video timed like the file, and adds the same footage through that mask above the video. Titles placed between the two pass behind the person, in the preview and in every export. -
GPU effects: plugins write layer and finishing effects in GLSL; new built-in effects
fx.matte(track matte from another layer),fx.displace(displacement map),look.chromatic(chromatic aberration),look.grade(colour grade in linear light). New property typelayer. -
In the preview, a layer or effect that fails is drawn as a red frame and named in the error bar instead of blanking the whole picture.
-
2.5D camera: a composition can have a camera (pan, zoom, perspective, focus, depth blur) and layers a depth, for parallax and depth of field.
-
Viewport handles declared by nodes (the rectangle’s corner radius, plugin nodes’ own points).
-
Presets in the add menu: neon title, frosted card, light leak, spotlight; plugins add their own
presets. -
Plugin nodes can say how they export to SVG and Lottie (
export.svg,export.lottie). -
Plugin manifest (
metawith the plugin API version, checked at load) and the@tramme/pluginpackage (types,definePlugin()). -
Plugin library shared by the projects: keep a project’s plugin there and use it in another (
/library-add,/library-use). -
Simulations: a node can carry a state from frame to frame (
simulate), stepped deterministically with checkpoints; nodes read other layers withhost.layer(). Newfollownode: a dot following a layer on a spring, with a trail. -
The assistant knows when each built-in node, effect and modifier fits (notes in
list_nodes). -
Example project “Night sky”: a project plugin with a node, a tool and a workflow.
-
Plugins roadmap:
docs/plugins-roadmap.md. -
Sound roadmap:
docs/sound-roadmap.md(sound effects, ambiences and music made by the assistant in the editor). -
Sound library: 421 recorded sounds (Kenney’s packs, CC0: impacts, interface, digital, jingles, sci-fi) measured and described in
sounds/catalog.json, and 13 sounds written as code (whoosh, riser, sub boom, cinematic impact, glitch, sparkle…); your own sounds in a library shared by the projects (/api/sounds). -
Sound tools for the assistant and the
/menu:sfxsearches the library and places a sound on the moments the document names (entrances, exits, markers, cuts, beats, bars), its hit on the frame, its variants alternating;synthmakes a sound from Web Audio code and answers with its waveform and measures;ducklowers music under a voice;sound-keepkeeps a sound in the library;generate-soundhas a provider make a sound effect, a music bed (ElevenLabs) or a voice-over (ElevenLabs, OpenAI, Gemini). The/sound-designworkflow, and the assistant’s guide for sound. -
The
generate-imagetool (assistant and/generate-image): a provider (OpenAI, Gemini, Z.AI) draws a picture the project lacks — a background a title reads over, a texture, an illustration, a prop — from its prompt, in the proportions of the composition; the file and what made it (assets/images/<name>.image.json: prompt, provider, model, proportions) join the project, the picture is proposed as an image layer (filling the frame or whole, over the whole composition or from a time, in the background on demand), and the tool answers with the picture so the assistant judges what was made. The keys stay in the Worker (/api/generate-image,/api/configlists the providers that draw); nothing is sent without the user’s yes (the same setting as the paid sounds). The assistant’s guide says when to have a picture made and why words never go in one (text layers say them). -
Generation roadmap:
docs/generation-roadmap.md(pictures made by a provider, then takes, image to image, moving pictures, and what checks read in a picture). -
Motion figures: what the numbers of an animated property say (
packages/core/src/motion.ts), sampled from the same evaluation the render uses — how far it travels, peak speed and when, evenness of the speed (1 is the linear tell), direction changes, how far it overshoots its end value, and when it settles. Themotiontool answers with the figures of the span’s biggest travels beside its strip of frames, so the assistant judges a movement with its numbers, not only the spacing. New checks that read them:linear-travel(a position or scale at constant speed for 0.3 s or more: ease it; a spring, a wiggle or any turn stays silent),spring-settle(a spring still moving when its layer leaves: more damping or more time; or overshooting its mark by more than 30%: one bounce is lively, more is nervous) andtwin-motion(two layers whose positions follow the same series: offset, stagger or vary one). -
Motion taste: the craft’s rules, distilled from the public references of the field (the Animator’s Survival Kit, Disney’s twelve principles, the Material, Carbon and Apple motion systems, kinetic typography) and encoded where the engine acts on them. A “Motion” section in the assistant’s guide: space before time (an even speed is the missing ease), entrances of 200 to 400 ms eased out and exits faster, one moving subject at a time with an uneven stagger, anticipation, arcs on the long travels, settles instead of hard stops, springs for what lands and curves for what intends, the reading time of text, and curves defined once as ease tokens (out, in, standard, emphasized, also named in
docs/document.md). Three checks that read the figures:abrupt-entrance(the first move after a layer appears runs at full speed: ease it in),straight-travel(a big diagonal travel that keeps to its straight line: bend the move) anduniform-stagger(a group entering with even offsets: vary the gaps). The/polishworkflow runs the whole loop on a composition: check and motion tools, the fixes the guide asks for, check again. Thebar-chartrecipe’s fades now ease with the kit’s curve. -
Motion sense everywhere the model looks: the notes per node family carry what each thing’s movement should be (text moves as a block or word by word, a counter rolls with an ease out, a bar draws along its x, a path draws itself over 0.4 to 0.8 s, a callout follows without lag, captions pop on the spoken word, a group staggers its children, footage drifts or zooms slowly and never both); the style kits expose the four curves as tokens,
standardandemphasizedbesideenterandexit, flavored per kit; and themotiontool reads the pixels of its frames (optical flow by block matching between two stills): it says when the whole frame moves and how fast in px/s, and points at the blocks that move against the rest — a background that should hold, something crossing the move. -
Themes: the interface colours become a list of themes, one palette chosen in the settings and kept in the browser: Studio (the former look), Obsidian (near-black, the chrome recedes into the room), Carbon (pure graphite, no blue in it), Dusk (a warm dark for the long sessions), Paper (the former light grey), and System (follows the computer). The meaning of colours stays across themes (selection, keyframes, expressions, links); the picker shows three swatches per theme, and an old preference migrates.
-
Display modes: the same interface, laid out differently (top bar’s expand button, or the settings). The editor stays the default; Cinema gives the film the whole window — the panels become floating glass cards summoned from the edges (layers, properties, the transport and the timeline as a bottom drawer); Conversation makes the assistant thread the main column, with the film beside it and the layers one edge away. A display change re-measures the stage.
-
The
shortstool (assistant and/shorts): a long video as shorts, in two calls. First the candidates: the transcript grouped on pauses and sentence ends into passages that stand alone (15 to 45 s by default), each with its times and what is said. Then a plan of passages built into one composition per short: the video filling the asked format (vertical 1080×1920, square, horizontal) and starting at the passage’sstart, the transcript remapped to the short, saved as its own asset and captioned (thecaptionstemplate), the title with its bar (thetitletemplate). Each short is an ordinary composition: editable, checked and exported like any other. The frame follows the speaker:focuson the video layer (the point of the picture kept at the centre of the frame, as the image layer had; animated, it follows the subject in a cropped frame), which the build animates across each short from the subjects analysis of the video when there is one — the biggest person of each analysed frame, held when nobody is found, drifts under 4 % of the picture ignored. The/shortsworkflow, and the assistant’s guide for shorts (a short stands alone, hooks in its first sentence, ends on a point).transcriptIdOfmoved to@tramme/corewith the rest of the transcript domain. -
Sound layers: volume animatable (fades, ducking),
fadeIn,fadeOut,lowCut,highCut,reverb, andrate(speed and pitch) on audio layers; the same butrateon the sound of videos. -
The
checktool reads the mix: clipping, a mix far too loud or quiet, two sounds starting together. -
Sound settings (Settings, Sound): the preview’s volume and mute (the exports keep the mix), the level of effects and music beds the tools place, how much a music drops under a voice, varying repeated sounds, asking before a paid sound (a dialog; nothing is sent to the provider without a yes), the provider and voice for voice-overs, and your sound library (listen, delete).
-
Guided tour “Give the video its sound” (help menu): the library, asking the assistant, the
/sound tools, sound layers and their properties, checking the mix, exporting with the sound. -
Assistant effort levels, chosen for each model next to the model menu and in the settings: Claude Opus and Sonnet (low to max,
highby default, where Opus 5.5 alone would run atmedium), and the reasoning models of the other providers (OpenAI o-series and GPT-5, Gemini 2.5 and later, OpenRouter models that reason, gpt-oss on a local server: low, medium, high, or the model’s own default). A model that refuses its level runs at its own. -
The assistant tells you when it is done (Settings, Assistant): a notification from the system when the editor is in the background, a message in the editor after a long task.
-
Automatic application of the assistant’s changes (Settings, Assistant), turned on after a confirmation: a proposal is applied as soon as the turn is over, still checked first, shown in the conversation and undone with Ctrl+Z.
-
Event lists: a JSON asset of timed events (
{ id, t, label, detail?, values, set? }) that keep running totals: changes that add up (money in any currency, laughs, points, kilometres) or values an event sets (a weight, a temperature). Written by theeventstool (assistant and/events) from lines such as3.1 Petrol cash -18 | full tankor9 Weigh-in weight =72.5, and totals written as they should look:Cash: £23.67,0,00 €,Days: 0 day|0 days,Time: 0:00. Expressions read it withevents()(.total(),.text(),.since(),.pulse(),.last()…).event-counterputs the running totals in a corner, counters that roll at each change;event-tagsa tag at each event (PETROL −£18.00, or the total it leaves; newevents.tagnode);event-receiptevery event on a receipt typed line by line, then its totals (newevents.receiptnode). Every one of these layers reads the list as it renders: save the list again and they all follow. Example project “Road trip”. -
Counters:
direction,downrolls the digits back, for a value that goes down. -
Tracked callouts: the
tracktool (assistant and/track) follows something filmed through a video, framed by a rectangle drawn over it, a region of the picture or its name (person, car, dog… found by the detector), and saves where it is over time (track-<video>-<name>); a cut ends the track. Thecallouttool puts brackets and a label on it (newcalloutnode) that stay on it, even when the video layer is moved or retimed. Expressions read where it is withtrack(layer, name?).
Changed
Section titled “Changed”- The project format (still
tramme-project/1) admits PDF documents underassets/. Every project of 0.1.0 opens as before; a project holding a PDF (made from sources, or with a document attached to the assistant) does not open in 0.1.0. - Tool contexts gain
files()andfileUrl(path): plugin tools may use them; a host that builds tool contexts itself must provide them. - Switched project license from MIT to Apache-2.0.
- Provider keys are connected in the editor, under Settings, Providers: Connect, Change key, Disconnect for Anthropic, OpenAI, Gemini, OpenRouter, Z.AI and ElevenLabs. The Worker keeps them in R2 and never sends them back; Cloudflare secrets still work, a key connected in the settings comes first.
- Custom providers: any service of the OpenAI chat format (DeepSeek, Groq, Mistral…) added by name, base URL and key; its models show in the model menu (
custom:<id>:model). - Settings in sections: a menu on the left (Editor: Appearance, Preview, Guided tours; Assistant: Model, Providers, Behavior, Connection) with a search that finds a setting whatever its section, the chosen section on the right; on a phone, the sections as tabs.
- The assistant’s conversation with Claude is append-only: nothing already sent is rewritten, so the prompt cache stays warm and Claude’s thinking stays valid. Old tool results are cleared by the API (context editing) once the conversation grows; the system prompt is cached for an hour.
- Lighter tool answers:
list_nodesgives an index (properties asname:type=default, notes, tool inputs) and the full entries on demand (types), about 60% fewer tokens;get_documentreads one part withpath;read_filereads long files in parts (offset). - Longer answers (64k tokens) on the server path; a request Claude declines goes to another model on the server (
fallbacks), and the user is told when it is declined anyway. - One mixer for the preview, the browser exports and the command line (
@tramme/render): the command line mixes in its page and hands ffmpeg the finished track, instead of its own ffmpeg filter graphs.
- Expressions that read an analysis (
audio()) or an event list (events()) now have their values in the inspector, the curves, the viewport’s boxes and the assistant’sevaluate, instead of neutral ones. - On phones, the assistant’s message box no longer slips under the tab bar when the conversation is long.
- Counters: separators and units (
,%€) take their own width instead of a digit’s. - MP4 export: the H.264 configuration (avcC) is written from the stream itself. The one some encoders give (Media Foundation under Windows) was malformed, so Windows, QuickTime and phones refused the file (“format not supported”) while Chrome and VLC played it.
- Assistant, server path: stopping during several tool calls no longer breaks the next message; a tool call whose input is invalid or cut off is no longer run with an empty input (the model is told and calls again); inputs are checked against each tool’s schema on every path.
- Assistant, server path: a request part the API refuses (thinking display, context editing, effort…) is dropped on its own instead of turning off the thinking summary; retries wait as long as the server asks (
retry-after). - Assistant: a server that does not answer, or an answer whose stream breaks before anything was shown, is tried again by itself (twice) instead of ending the turn.
- 2.5D camera: a nested composition is drawn through its own camera (parallax and depth of field); it was ignored everywhere but in the root composition.
- Check
stillness: a nested composition counts as playing, as a video does, instead of making its parent look frozen; its own still stretches are found when it is checked. - Counters: digits share one cell again, as wide as the widest digit (the test looked for the letter “d”, so each digit took its own width and the number shifted as it rolled); the
statandbar-chartrecipes measure them the same way. tramme packandtramme unpackcheck a project with its own plugins loaded, as the editor’s import does; a project using plugin nodes (the night-sky example) was refused with “unknown node type”.
0.1.0 - 2026-10-02
Section titled “0.1.0 - 2026-10-02”First public release.
Engine
Section titled “Engine”- JSON document as the source of truth: nested compositions, layers, groups, assets, design tokens, markers and sound. Format
tramme/1, described indocs/document.md, with a JSON schema inschema/tramme-1.schema.json. - Deterministic rendering: every frame is a pure function of time.
- Every property can be static, keyframed, an expression or a link, with an optional modifier stack (wiggle, loop, spring, offset, variation, smoothing).
- Open vocabulary: each layer type is a node that declares its property schema. The inspector and the validator are generated from it.
- Native nodes: shapes, path, image, text, counter, group, composition, particles, GLSL shader, code, sound, image sequence, video, captions.
- Layer effects: blur, shadow, glow, color, tint.
- Canvas2D layer renderer and WebGL2 compositor (motion blur, linear color, finishing).
- Project plugins: projects can add their own nodes, effects and modifiers as JS modules.
Projects
Section titled “Projects”- Project format
tramme-project/1(manifest, allowed paths, checks), exchanged as.trammearchives. Projects created under the former names (“trame”, “emotion”) are still read.
Editor
Section titled “Editor”- Projects home: recent projects with thumbnails, new project (formats, frame rate, duration), project from a video, opening a
.trammefile or a Lottie animation, examples. - Viewport with zoom, pan, safe zones, grid, and direct manipulation (move, scale, rotate).
- Timeline (layer bars, keyframes, markers), Bézier curve editor, inspector generated from the schemas.
- Undo and redo for every change, autosave with conflict detection across tabs.
- Hand-drawn animation: image sequences held on twos or driven by an exposure sheet.
- Video layers decoded frame by frame with WebCodecs, speech transcription to timed captions.
- In-browser export: MP4 (H.264), WebM (VP9 with alpha), GIF, PNG sequence, Lottie, SVG still, WAV.
- Guided tours, settings (theme, preview quality), English and French interface.
- Mobile and touch support: tabbed panels under 760 px, a compact header with a “more” menu, pinch to zoom and two-finger pan in the viewport, larger touch targets, installable as a web app.
Assistant
Section titled “Assistant”- AI assistant that edits the document through the same operations as the editor: proposals are previewed, then applied or rejected, and can be undone.
- Claude through a local companion (
tramme agent, Claude Agent SDK) or through the server with an API key. - Other providers: OpenAI, Gemini and OpenRouter through the server, local models (Ollama, LM Studio) from the browser.
- Image, sound and video attachments; video dressing (cuts, captions, templates).
Command line
Section titled “Command line”trammeCLI: validate, still frames, offline rendering (MP4, MOV ProRes 4444, WebM with alpha, GIF, PNG, WAV) with headless Chrome and ffmpeg, Lottie and SVG export, Lottie import, pack and unpack, comparisons and benchmarks.
Deployment
Section titled “Deployment”- Cloudflare Worker serving the editor and the API, projects stored in R2, access protected by Cloudflare Access.