What Prefab does, and what comes next

Placeholders are filled in inside .docx, .xlsx and .pptx, and the formatting survives. A placeholder that Word has split across three runs is still found, and an Excel table’s column headings are updated alongside the cells so the file opens without a repair prompt.

Any agent that speaks the Model Context Protocol can list your templates, build new ones and deploy them. Off until you switch it on, and it reaches only the folders you have granted.

A prefab:// link can fill in placeholders rather than falling back to defaults, and reports what it created instead of leaving you guessing.

A folder from a template can keep working: files that land in it are renamed, converted, resized, tagged or sorted, using the answers the folder was created with. Preview before applying, and undo a run.

Placeholders, actions and saved sets of answers defined once and available to every template. A template’s own definitions still win.

A command that fails is now reported as failed rather than every command looking as though it worked, and commands have a timeout.

Export to a single .prefab file that carries the files it deploys and any templates it embeds. Double-click it on another Mac, or on a PC.

Finder’s right-click menu, the menu bar, the app itself, or a prefab:// link from Terminal, Shortcuts or a script.

Sonoma and Sequoia as well as Tahoe. Folder icons use the system’s own mechanism on macOS 26 and fall back to a composited image below it.

The visual template editor, placeholders, actions after deployment, Finder tags and folder icons, importing a folder you already have, and starter templates.

A folder remembers which rules have run over a file, so it does not do the work twice. Some of a rule lives outside that memory: change a rename pattern, an image quality or the text of a command, and files already handled stay as they are. Adding or removing a rule does reach them, and Apply Rules to Existing Files always does. Widening it changes what every folder considers done, so both platforms move together.

Deploy a template without leaving the launcher. Both sit on top of the prefab:// links that already work.

Your template library on every machine you use, kept in step. This is the one thing that cannot work without an account, so it will ask for one - and only for this.

A library everyone works from, so a team sets projects up the same way. Also account-based, for the same reason.

An agent can already run and undo a folder’s rules, but not write one. Letting it attach a git-init, a command or a watched-folder rule is the obvious next piece.

Repository templates, .gitignore presets, Xcode and VS Code workspaces - the setup that usually follows the folders.

The whole app rather than a subset: the visual template editor, placeholders, actions after deployment, folder icons, importing a folder you already have, starter templates and the template library.

Templates in the menu you already use, on a folder, a file or the background of a window. In the main Windows 11 menu rather than behind Show more options.

The same rules as the Mac: files that land in a deployed folder are renamed, converted, resized or sorted, using the answers the folder was created with. Preview before applying, and undo a run.

Substitution in .docx, .xlsx and .pptx, keeping formatting intact.

A .prefab file written on a Mac opens on Windows and back again. Finder tags are carried through untouched rather than dropped, so a template that has been to Windows still tags its folders when it is used on a Mac.

A folder remembers which rules have run over a file, so it does not do the work twice. Some of a rule lives outside that memory: change a rename pattern, an image quality or the text of a command, and files already handled stay as they are. Adding or removing a rule does reach them, and Apply Rules to Existing Files always does. Widening it changes what every folder considers done, so both platforms move together.

The app carries the agent switch and the same commands as the Mac from 1.1.7. What follows is the Model Context Protocol server, which looks for a library where macOS keeps one and so cannot see a Windows library yet. It is updated after the Windows release rather than before it, so one version of it is known to work against both.

Your template library on every machine you use, kept in step, whichever system each one runs. This is the one thing that cannot work without an account, so it will ask for one - and only for this.

A library everyone works from, so a team sets projects up the same way. Also account-based, for the same reason.

An agent can already run and undo a folder’s rules, but not write one. Letting it attach a command or a watched-folder rule is the obvious next piece.

Repository templates, .gitignore presets, Visual Studio and VS Code workspaces - the setup that usually follows the folders.