Personal AI agent for macOS, Windows, Linux, Android & iOS. Set a goal, it works alone: coding (Skales Code), desktop + browser automation, autonomous scheduled Tasks. Teams of agents and humans across paired desktops. Agent2Agent, MCP, computer use, voice, local LLMs (Ollama), Agent Skills (SKILL.md). 26 AI providers, BYOK. No Docker, no terminal.
HTML agentic-aiai-agentai-assistantandroidautomationautonomous-agentdesktop-appelectronioslinuxllmlocal-ailocal-firstmacosmcpollamaprivacyreact-nativetypescriptwindows
12.8.3 Intact: the changelog, the guide and the readme describe this release
Mario Simicff496b2b45e2
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 8c6d1c6..bb4a685 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -6,6 +6,97 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).+## v12.8.3 - Intact++### Fixed++- **A finished answer is no longer followed by a second one nobody asked for.**+ A line typed while Skales was still writing goes into the queue, as before.+ Two things then went wrong with it. A queued message that could not be handed+ over was put back, and putting it back is what woke the queue again, so the+ same text was submitted over and over; and the composer unlocks by itself when+ a turn stops responding, which the queue read as "the turn is over" while the+ turn was still running on the machine. Now a message is tried once more at+ most and then waits in plain sight with a Try again next to it, and nothing+ goes out until the run is genuinely finished rather than merely unlocked.+- **Long Telegram answers arrive whole.** Since 12.8.2 the answer is written+ into the message you are already looking at, and that path never checked+ Telegram's per-message limit: a long answer stopped mid-sentence at the last+ piece that still fit. A message that had waited in the queue was worse - it+ counted as delivered although Telegram had refused it, so it never arrived at+ all. Answers are now split and sent in order, with code blocks closed and+ reopened across the split, and nothing counts as delivered until Telegram+ confirms it.+- **Saving a mail account no longer destroys its password.** Changing any field+ on an existing account wrote the row of dots back over the real password. If+ an account is already in that state it now says so and asks for the password+ again, instead of reporting a login failure from the provider.+- **The mail Test button checks what is on screen.** It tested the saved values+ while showing the verdict as a verdict on the ones just typed, so a corrected+ port was reported as refused before it had been tried. Only the password still+ comes from storage.+- **Port and encryption belong together.** Switching encryption moves the port+ the way the label always promised, and the four impossible combinations say so+ at once instead of arriving later as a certificate error - which is also what+ implicit TLS on a STARTTLS port used to be reported as.+- **Skales answers correctly about its own integrations again.** A read-only+ mail account, or a settings file written by an older version, made the+ assistant deny Google, Drive, Docs and IMAP that were configured and working+ the whole time. Nothing had been removed: its self-check read different files+ than the tool catalogue and the settings screen. On local and small models+ those tools could also be squeezed out of the tool budget first; they are now+ protected once configured. A Google account missing one field now names the+ field instead of vanishing.+- **The context size you set for a local model reaches the engine.** It was+ never passed on, so the server chose a window on its own - 4096 on some+ machines - while the banner read your setting back to you rather than the+ window in force. The banner now shows the window the server actually holds,+ changing the setting restarts the local server, and a request that does not+ fit ends the turn once with the real numbers instead of being retried until+ the partial answer has been erased and restarted several times.+- **A local model no longer advertises reading pictures when it cannot.** The+ VISION badge is checked against the running engine, so a model whose projector+ is not on disk says so. An engine that is running with nothing loaded is no+ longer reported as not running, the role buttons say why they are disabled,+ and a start skipped because autostart is off says that too.+- **Raw `<textcall>` markup no longer appears in answers**, and - more+ importantly - the call inside it is now carried out. Removing the markup+ without running the call would have meant asking for something, and nothing+ happening, with no error.+- **Teams, Organization, Group Chat and Swarm are reachable again**, on every+ theme. The pages and the runner were never touched; only the doors to them had+ been taken out, and on the top-bar and icon-rail themes there was no way in at+ all.+- **One conversation can no longer lock the others.** Opening a chat kept the+ previous one's run, which held the input and the history list; starting a new+ chat was the only way out. A conversation that cannot be drawn now shows the+ reason and leaves the rest of the app alone.+- **Allowing something "for this session" holds across Chat, Code and Flow.**+ The three surfaces kept three separate notes of it, and in Code the answer+ could land in a copy the waiting run never saw, so the same question came back+ after it had been answered. In Flow a card showed "running" even when the+ answer could no longer be applied - after a restart, for instance; it now says+ the runner was lost and asks you to send again.+- **Rewrite (/spin) keeps what it produces.** The rewritten text was only put on+ screen, so the next refresh of the conversation removed it again - the feature+ ran and appeared to do nothing. It is written into the conversation now, and a+ write that fails says so and leaves the text where it can still be copied.+- **The Home/Chat switch shows the column that is on screen.** Opening a+ conversation raised the chat column while the switch still lit Home. Your+ stored preference is left alone.+- **Portrait pictures in Discover are shown whole** instead of cropped to a+ band.+- **Browser Control can attach a file to a web page.** Upload fields that a page+ hides are now listed and can be addressed directly, including through the+ button in front of them, so no operating-system dialog is needed; the field is+ read back afterwards and a mismatch refuses to submit.+- **Custom endpoints are first-class in the agent editor.** Each server you set+ up appears under its own name, the choice survives reopening and restarting,+ and an endpoint that has been switched off is named rather than shown as+ "Default".+- Memory "Minimal" now says what it does: it shortens the memory context, and+ the tool schemata have their own switch directly below it.+## v12.8.2 - Mood### Addeddiff --git a/README.md b/README.mdindex 8bea0c6..04388ae 100644--- a/README.md+++ b/README.md@@ -8,7 +8,7 @@ The private AI that lives on your computer and does real work, not just chat.<img width="960" height="580" alt="Dashboard" src="https://github.com/user-attachments/assets/bba3411e-85eb-44e8-ab58-be2a5a88a650" /></p><p>- <a href="https://github.com/skalesapp/skales/releases/latest"><img src="https://img.shields.io/badge/version-12.8.2-10b981?style=flat-square" alt="Version 12.8.2" /></a>+ <a href="https://github.com/skalesapp/skales/releases/latest"><img src="https://img.shields.io/badge/version-12.8.3-10b981?style=flat-square" alt="Version 12.8.3" /></a><a href="https://skales.app"><img src="https://img.shields.io/badge/license-BSL_1.1-10b981?style=flat-square" alt="License" /></a><a href="https://skales.app"><img src="https://img.shields.io/badge/Windows_+_macOS_+_Linux_+_Android_+_iOS-10b981?style=flat-square&logo=windows&logoColor=white" alt="Platform" /></a><a href="https://github.com/skalesapp/skales/stargazers"><img src="https://img.shields.io/github/stars/skalesapp/skales?style=flat-square&color=10b981" alt="Stars" /></a>diff --git a/docs/skales-guide.html b/docs/skales-guide.htmlindex 91ce9b3..05f3357 100644--- a/docs/skales-guide.html+++ b/docs/skales-guide.html@@ -744,7 +744,7 @@<div class="logo-mark">S</div><div><div class="logo-text">Skales</div>- <div class="logo-version">v<span data-skales-version>12.7.4</span> User Guide</div>+ <div class="logo-version">v<span data-skales-version>12.8.3</span> User Guide</div></div></a>@@ -915,7 +915,7 @@<!-- Hero: the front page only --><div class="hero">- <div class="hero-badge">📖 Official Documentation · v<span data-skales-version>12.7.4</span></div>+ <div class="hero-badge">📖 Official Documentation · v<span data-skales-version>12.8.3</span></div><h1>Skales <span>User Guide</span></h1><p>Your personal AI operating system. Set a goal, automate, create, all running locally on your machine.</p></div>@@ -1269,6 +1269,7 @@<h3>Sending while it is still writing</h3><p>You no longer have to wait for the answer before typing the next thing. Messages you send while Skales is working are <strong>collected and answered together, as one turn</strong>, in the order you wrote them — not as one answer per message, which used to mean three impatient messages became three answers to three halves of a question, and three times the wait.</p><p>A bar above the composer shows how many are waiting, lists them, and lets you remove one or clear them all before they go. Up to twenty can queue. If a run ends without the queue being taken up, a card offers to hand the whole queue back to you rather than dropping it. The same rule holds everywhere Skales listens — a run on the server, Telegram, WhatsApp and the phone all fold a queue into one answer.</p>+ <p>What is waiting goes out once the run is really over. That is not the same moment as the composer unlocking: a turn that stops responding frees the composer so you are not stuck, while the run itself carries on, and a queued message sent into that gap used to arrive as a second answer to a question that already had one. If a queued message cannot be sent at all, it is tried once more and then stays in the bar saying so, with <strong>Try again</strong> beside it, rather than being retried silently.</p><h3>Working with a reply</h3><p>Right click a message for its menu: copy, rewrite, quote in reply, save to a document, read aloud, regenerate or branch a new session from that point. Select part of a reply first and the same right click acts on the passage instead, starting with <strong>Rewrite selection</strong>.</p>@@ -3940,7 +3941,7 @@</section><footer>- <span>Skales v<span data-skales-version>12.7.4</span> · © 2024-2026 Mario Simic · BSL 1.1</span>+ <span>Skales v<span data-skales-version>12.8.3</span> · © 2024-2026 Mario Simic · BSL 1.1</span><a href="https://skales.app">skales.app</a></footer>