Skip to content

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.

Public documents open with their content, not with a header block

Mario Simice2e665c922ae
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c624f3b..90f6d26 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,11 +1,3 @@
----
-summary: Every released version of Skales Desktop with its user-visible changes, newest first.
-read_when:
- - you need to know what changed in a specific version, or when a feature first shipped
- - you are writing release notes and need the established wording and section format
- - a user reports behaviour that changed and you want to find the release that changed it
----
-
# **Changelog**
All notable changes to Skales will be documented in this file.
diff --git a/docs/skales-guide.html b/docs/skales-guide.html
index 496bf1b..2c4897e 100644
--- a/docs/skales-guide.html
+++ b/docs/skales-guide.html
@@ -1,10 +1,4 @@
<!DOCTYPE html>
-<!--
-summary: "The chaptered end-user guide rendered inside the app: what every feature is and how a user drives it."
-read_when:
- - you shipped a user-visible feature and the guide must describe it
- - you need the established wording for a feature as users see it, not as the code names it
--->
<!--
THIS IS USER HELP. RELEASE NOTES BELONG IN CHANGELOG.md AND IN THE CHANGELOG
VIEW, NEVER HERE.