v12.5.5 - Nothing You Made Is Gone

A turn used to be a one-way door. Regenerating an answer deleted the one you had; a Flow turn rewrote the deck you liked and the previous version was gone from the disk. Both keep their history now, and both let you walk back into it. Updating is recommended for everyone.

Version history everywhere

• Asking again keeps the answer you already had. Regenerate an answer, or reword the question, and the previous turn is kept as a version instead of being deleted. Arrows and a counter at the answer step through them; switching restores the whole turn it belonged to, including its tool results, and survives a reload.
• A Flow project keeps every version of its artifact. Each turn's result is archived before the next one can overwrite it, up to the last twelve, and the history opens from the preview toolbar as real renders rather than a list of dates. From a version you can go back to it, download it as a ZIP without disturbing what you have now, or branch it into a project of its own. Coming back is not one-way either: the state a rollback replaces is kept as a version too, and the chat is told what happened so the next turn works from the files that are actually there.
• Flow projects can be put away or thrown out. Archiving is reversible and changes nothing else: the project keeps its files, versions and chat, and only leaves the grid. Deleting moves the project folder to a trash folder next to your projects, so it can be recovered by hand.
• Undo and redo in the Flow editor. Its own undo stack, from the toolbar and the usual shortcuts: typing groups into words, a line break ends a step, and the cursor returns to where the edit was instead of jumping to the end of the file.

Flow

• A deck leaves Flow as PowerPoint, a document as Word, a course as SCORM. PowerPoint is built from the laid-out slides, so the text boxes are real ones the client can retype, with pictures, speaker notes and slide colours. Word keeps headings, lists, tables and pictures editable. A course packages the project for Moodle and other LMS, with a runtime that reports the lesson complete inside the LMS and does nothing outside it.
• A Flow project can be handed to someone else. The export menu offers the project itself: every file as it stands, in one ZIP, in any mode. It carries your work and nothing else, not the version history, not the backups, not the deployment settings.
• Motion can be made in a technique, not just in a palette. Motion gains a Style setting with fourteen techniques (papercut, pixel, particles, whiteboard, kinetic type, motion graphics, sketch, ASCII, isometric, blueprint, neon, comic, origami, silhouette) and three effects that stack on any of them: stop motion, glitch and film grain. Each technique brings the drawing it needs rather than imitating it, so pixel art is really drawn on a pixel grid. It is a separate choice from a style pack, which decides colours and type.
• A rendered video is checked before you are told it is ready. Every finished render is read back frame by frame, so a clip that freezes, a stretch that comes out black, or a video that never moves is caught in the file rather than in the preview, with the exact seconds it happens at. The checks that need no vision model run everywhere; with a vision model set up, the differing frames are looked at as well.
• Flow can just do what you said. A "Free" switch next to the brief turns off the starting file, layout catalogue and checklist, so your brief is the whole specification. What you chose yourself stays on: your files, template, Brand Kit and style pack.
• Auto: the brief picks the output type. The Auto chip reads the brief, picks the mode and template, and shows what it chose so you can correct it.
• Ask first: a few questions before anything is built, as a card of clickable choices folded into the brief. Anything left on "decide for me" is left out, and a brief that is already specific gets no questions.
• A video can be as long as you asked for. "Follow instructions" is now one of the length choices, so the duration comes from your brief alone.

Right-click menus

Chat messages, saved chats in History and the session list, task cards and schedule rows, images, links and API key fields all have proper context menus now, in the desktop app and equally when you open Skales from a browser or your phone. Chat offers Copy, Quote in reply, Save to document, Read aloud, New session from here, Regenerate and Edit and resend. A link offers Copy, Open in browser, Open in the built-in browser and Summarize. A key field offers Copy value while staying masked, Reveal or Hide, and Remove. Delete takes two clicks instead of a dialog. In all twelve languages.

Providers

• GLM and Qwen are providers you can pick. Both are registered the whole way through: the provider card and model list, context and output limits, live model refresh, the group-chat and custom-skill pickers, and onboarding. Descriptions in all twelve languages.
• Gemini 3.6 Flash and Flash Lite are in the model lists, and are the default.
• GitHub as an MCP server without Node, over its official remote endpoint with a sign-in, so it needs no npx and no access token. The local server stays, and both entries say which is which.

Changed

• An isolated agent gets a memory of its own. Each agent has its own store, and its lessons go to its own file. Normal chat, custom agents and scheduled runs keep the owner's memory unchanged.
• You hear about it when an agent schedules itself. Standing work an isolated agent gives itself is now its own notification type, so it reaches WhatsApp, Telegram and the phone with your quiet hours and channel choices applied. You scheduling something yourself stays silent.
• A crash screen now tells you what crashed: a ready-made report with the error, the page and where in the app it broke, in a box you can select, plus a copy button.
• Look at an image by URL. Image analysis takes an http(s) address, instead of downloading every picture the agent only wanted to see.

Fixed

• A third of every request stopped being sent twice. The instructions that frame a turn were placed at the top of the request and appended at the bottom, so the model read the same pages twice and you paid for both. On a measured Flow deck turn the request fell from 86.3 KB to 56.6 KB. Nothing was removed, only the second copy dropped.
• Your own instructions to Skales apply again. The personality and system prompt you write in Settings are back in front of everything else, on every Flow turn, every Code turn and every step of a chat after the first.
• Things that are supposed to exist once now exist once. One shared instance per app now backs the autopilot call limit, the heartbeat, connected tool servers, the browser Skales controls, the local network announcement, log rotation and file saving.
• Deploy settings stay out of every list, download and page. One list now decides everywhere which files Skales keeps for itself, so the project record, deploy settings, saved versions and caches never leave with your work. Your files and existing versions are untouched.
• Turning the effort dial down actually turns it down. High and Extra high add the deep reasoning pass, Low and Medium leave it out. With the dial untouched, nothing changes.
• Stop now ends the session, and a stopped run no longer reads as a failed provider.
• No time limit now means no time limit, with a checkbox next to the slider and an end message that says what actually stopped the run.
• A picture sent over WhatsApp is answered even when the picture does not arrive: the file is waited for and re-requested, and if it truly does not arrive you get an answer saying so instead of silence. Telegram says it too.
• A stuck reasoning model gets the bigger reply budget whenever there is one to give, measured against what the turn actually used.
• Long-term memory asks where a fact came from, a skill loads when you name it rather than when a word contains its name, importing a skill brings its files, and a stranger cannot stop your turn in a Telegram group.