Skip to content

Projects and files

Cask Flow keeps every project in one place: ~/Library/Application Support/Cask Flow/Projects/. There is no save panel and no “where shall I put it” question. Settings > Projects shows the path and has a Show in Finder button.

Each project is a .caskflow package: a folder that macOS shows as a single file. Inside it are project.json, an Assets folder holding every image and clip the project uses, the undo journal, a thumbnail, and a small metadata file.

That makes a project self-contained. Copy the package to another Mac and the media goes with it.

New project creates a project called Untitled and opens it straight away. The composition is 1920 by 1080, 60 frames per second, 5 seconds long. Settings > Projects shows that shape under New projects, read from the same constants the button uses.

The first time you open Cask Flow it seeds one example project into the library. It is an ordinary project: rename it, edit it, duplicate it or delete it. Nothing in the app treats it as special, and deleting it does not bring it back on the next launch.

Importing an image or a clip copies the file into the project’s Assets folder. Deleting or moving the original afterwards does not break the project. The cost is disk space.

Cask Flow saves about a second and a half after you stop making changes. There is no save command to remember.

Undo is persisted alongside the project, so reopening it lands you where you left off rather than on a clean stack.

One agent tool call is one undo entry. Manual edits coalesce per gesture and per property: dragging X from 0 to 100 across five drags is one ⌘Z back to 0. Changing a different property, touching a different node, or an agent call ends the run.

The Changes tab on the right lists those entries newest first, with Undo on each step and Redo on the ones you have undone. Undoing through a row is the same operation as pressing ⌘Z that many times.

If the bundle changes on disk underneath the open editor, a sync client, a checkout, a duplicate made in the Finder, Cask Flow stops saving and refuses every write, including the agent’s. The editor shows a notice with two answers: reload from disk, which discards this session’s edits, or keep your changes, which overwrites what is on disk.

There is no cloud sync in Cask Flow, and no edit lease. This is the only state that makes a project read-only.

The Import from Cask Film button on the Projects screen reads a Cask Film .caskproj package and writes a new Cask Flow project from it. A report afterwards says what came across and what did not.

It is a one-way import, not a link. Editing the Cask Flow project does not touch the Cask Film one.