v0.8.0

keyline 0.8.0 gives every design a folder you can see: drop your images in, find the renders next to them, and pick the design up again by name in any session.

Breaking: --allow-read is now --folder

--allow-read is gone. Pass --folder instead: it now lets keyline write as well as read, and it decides where designs go (below). Without it, keyline works in ~/keyline, so local paths now work out of the box.

A folder per design

~/keyline/
  summer-sale/
    hero.jpg                   your files, added by path
    summer-sale.keyline.json   the design, saved after every edit
    renders/                   PNG, PDF, MP4…

• scene_create takes a name, which is both the design's id and its folder: summer-sale v0 in ~/keyline/summer-sale. Without one, the design gets a generated id.
• A later session, or another app, continues a design by name. An unknown name's error lists the designs there are.
• The workspace is the --folder folders, else ~/keyline. New designs go in the first folder, and files can be read from any of them.
• Claude Code plugin: designs live in the project folder Claude Code was started in. In your home folder or /, they go in ~/keyline.
• Claude Desktop: the folders picked in Settings → Extensions → keyline → Configure, else ~/keyline.
• Docker: ~/keyline is /data/keyline, in the volume.
• Older scenes: scenes made before this release stay in ~/.keyline-mcp and still open by id.

Also

• Contrast: text that fades in is judged at its full opacity, not its starting one, so a fade-in no longer raises a false warn contrast.
• asset_add: base64 is meant for small images such as logos; photos should come by url or path. This keeps photos from passing through the model byte by byte, which was slow.
• Local paths may start with ~.