0.9.0-beta.28Beta

Added

• Agents can import images from your folders. import_image now takes path (one image) or paths (up to 50) as well as base64, so an agent can use a 3 MB photo or a 20 MB sprite sheet it already has on disk instead of pasting it as text. It reads only images (PNG, JPEG, WebP, GIF, BMP and AVIF, decided by the file's bytes, not its name), up to 50 MB and 64 megapixels each, and only from folders you allow. The first time it asks for a new folder, the chip says "AI asks to read images · Hero" with Review…, which opens the folder in full: Allow lets it read that folder and the folders inside it for this session, or always if you tick "Always allow this folder on this PC"; Not now refuses it for the session; Choose another folder… lets you pick a different one. Links and junctions that lead outside an allowed folder, network paths, drive roots, your home folder and the system's folders are refused. The Agent connection window has a new FILES group with "Read images from your folders" (on by default: it only lets an agent ask), the list of image folders with Remove and Add folder…, and while an agent works, "Read 12 images from Hero" with Show for the list of what it read. The Changes tab names the file after an image fill ("an image (1200 × 800) · head.png"). Paths and folder names are never written into your file: they stay in memory, and remembered folders stay in this PC's settings. polyform mcp serve reads only the folders given with --allow-images. Downloads from the web come later. (#315)

Fixed

• export_sprites no longer claims engines read its files. Its description and the agent guide said PixiJS, Phaser and Unity importers read the default manifest. None of them had been tried, and Unity has no built-in reader for that format. They now say what it is: a TexturePacker-style JSON Hash, a JSON Array or a Spine atlas. (F-376, #328)