Skales: the source was deleted at 12.9.30 because it no longer matched the product
Personal AI desktop agent for Windows, macOS, Linux, Android & iOS. Set a goal, it works on its own. Teams (pair two desktops, agents + humans), Agent2Agent, Workflows, Codework, multi-agent orgs, desktop + browser automation. 15+ AI providers, BYOK. No Docker, no terminal. Agent Skills (SKILL.md). Migration importer. Recurring autonomous tasks.
At a glance
- What is it?
- Skales is a proprietary desktop agent for Windows, macOS, Linux, Android and iOS, and this repository distributes it rather than containing it. The page states plainly that a version 7 source snapshot stood here until release 12.9.30 and was removed, that it had 138 TypeScript files against 984 in the tree actually built, and that it drew four security reports about code the shipped application does not contain.
- Who is it for?
- Skales suits someone who wants a single click-to-run desktop agent across Windows, macOS, Linux and two phone platforms, is willing to supply a key from one of fifteen providers or run locally, and does not need to read the code. It does not suit anyone whose decision depends on auditing the implementation, because the source was deliberately withdrawn and the product is closed, and the page is candid about why.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 5 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- skalesapp/skales2,241 ★ · +387
| Repository | 2026-09-10 | 2026-11-15 |
|---|---|---|
| skalesapp/skales | 1.9k | 2.2k |
387 Stars in the last 66 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
This repository distributes the product and does not contain it
The most important paragraph on the page is the one labelled as being about the repository, and it removes any ambiguity about what is here. This is where Skales is distributed: releases, the changelog, install guides and the issue tracker. Skales itself is proprietary and stays proprietary, and the product is the signed application downloaded from the project's own site. So the root you are looking at holds no application code, which is worth stating because the recorded primary language for the repository is TypeScript and that language now describes whatever remains rather than the shipped agent. The tree backs the distribution claim exactly. It carries a `.gitignore`, the changelog, three platform install guides for Windows, macOS and Linux, a code of conduct, contributing instructions, a security document, third-party notices, a trademark file, a proof of authorship file, two license files and a `pets/` directory. There is no `src/`.
The v7 snapshot was removed because it had drifted from the product
The page gives the removal its own account, and it is specific about the drift. A v7 source snapshot stood in this repository until release 12.9.30 and was removed with that release. Its last code commit was 26 July 2026, so it had been frozen for roughly two months before the deletion, and well before that it had stopped describing the software people were running. The numbers given are four: 138 TypeScript files against 984 in the tree that is actually built, and 70 API routes against 225. On top of that drift came a cost that is stated without hedging, that the snapshot drew four security reports about code the shipped application does not contain. That is a specific failure mode for an open source mirror: a tree old enough to be interesting and different enough to be misleading, where the reports that arrive are real reports against code nobody is shipping. The fix chosen was deletion rather than synchronisation, and the page argues the point explicitly, that a source tree six months behind the product created more confusion than clarity.
The licence changed in the same release the source was removed
Both changes shipped together, which the page presents as one decision. With 12.9.30, Skales moved from the Business Source Licence 1.1 to its own End User Licence Agreement. What that means for a reader is spelled out in the reassuring direction: for what you may do, nothing changes, with private use, study and teaching staying free of charge, and commercial use having required a licence under the previous terms as well. The stated reason is the same confusion argument, that one agreement in plain language shown once on first start is easier to understand than a source licence pointing at code that no longer described what you were running. The full text ships beside the application, in an English file and a German one, and the tree also carries a commercial licence document, a proof of authorship file and a trademark file. Note that the repository's own licence metadata records no recognised licence at all, which is consistent with a custom end user agreement rather than one of the standard licences a scanner would recognise.
The terms boundary is named at 12.9.27 and the change lands at 12.9.30
One sentence in the disclosure is about which releases keep which terms, and it has a gap. The page says releases up to 12.9.27 keep the terms they were supplied under, and it dates the move to the same release as the source removal, 12.9.30. Between those two points sit 12.9.28 and 12.9.29, and the sentence does not say which agreement applies to them. Read one way, the old terms run to 12.9.27 and the new ones begin at 12.9.30, leaving two releases unaccounted for. Read the other way, the boundary at 12.9.27 is approximate and everything after was already under the new agreement two releases before it formally changed. Either reading is defensible and the page does not choose between them. This matters more than a version-boundary usually would, because the thing being delimited is a commercial licence rather than a feature, and a business reading the changelog to work out whether a specific build may be used commercially is exactly who needs the sentence to be unambiguous.
The security row of the comparison table stops mid-sentence
The page argues the case for a local agent with a table comparing typical agents against this one across seven rows. Setup is Docker, a terminal and a Python CLI against a downloaded executable, disk image or AppImage that is double-clicked. Operating system support is Linux and Docker required against Windows, macOS and Linux native. Updates are a manual pull and rebuild against a one-click auto-updater. Privacy is cloud only against local-first, bring your own key, offline capable. The two quantified rows are resident memory at 1.5 to 3 gigabytes and above for a typical agent against roughly 300 MB, and time to first task at hours to days against 30 seconds. Neither figure is accompanied by a method, a build number or a measurement platform. The seventh row is Security, described for the other column as unsigned scripts and for this one as Apple Developer ID signed, and the cell ends there, with the parenthesis about Windows never closed on the page.
The heading says eleven places and the list beneath it has twelve
The feature index has a collapsible section whose entry reads as the eleven places Skales lives, and the list nested under it names twelve: Chat, Code, Studio, Cockpit, Planner, Iris Orbit, Memory, Mobile, Skales Pocket, Plugins, Discover and Wrapped, and Settings and Add-Ons. The last of those is indented at the same level as the rest, so on the page it reads as a twelfth member of a list the heading numbers at eleven. It may be intended as configuration rather than a destination, which would make the heading defensible, but nothing on the page says so. The same index shows looser anchor hygiene: several entries carry a variation selector inside their link target, so the Cockpit, Iris Orbit, Privacy, Providers, Installation, Architecture, License and Settings links all point at fragments that begin with an invisible character before the hyphen. Neither problem breaks the page for a reader clicking through it in a browser. Both are the kind of thing a hand-maintained index of this size accumulates, and they are worth knowing about if you are writing your own documentation in the same shape.
Patch releases ship most days under single word names
The release numbering is dense. The three most recent tags are 12.9.46 published 2026-09-30, 12.9.45 on 2026-09-29 and 12.9.41 on 2026-09-25, which puts three patch releases across six days. A version numbered 12.9.46 means forty-six patch builds have shipped inside the 9 series alone, and the last commit to the repository is dated the same day as the newest tag. Each release carries a single word in its title rather than a description of the change: Mend for 12.9.46, Steer for 12.9.45 and Lantern for 12.9.41. That reads well as a brand and badly as a changelog, because the words do not tell you what changed, which leaves the changelog file and the discussion tracker as the only places to find out. A project shipping at this rate also makes the source snapshot problem easier to understand, since a tree frozen in late July could not track a release train moving several builds a week, and the page's own arithmetic, 138 files against 984, is what that gap looks like when you measure it.
Two macOS download targets and a testimonial from a contributor
The distribution surface is wider than the platform list in the summary suggests. The download links are broken out separately for Windows, for macOS on Apple Silicon and for macOS on Intel, and for Linux, which is unusual attention to pay to two architectures of one platform. Mobile is separate again, with an Android listing and an iOS listing, and the page adds that a paired phone drives the desktop's full tool set over a QR code or runs standalone. The repository carries three platform install guides to match. Elsewhere the page offers a free built-in trial that needs no API key, then a key from fifteen or more providers or a fully local setup, and a migration importer for people arriving from two named agent tools and one chat product, reachable from Settings. The page also carries a long pull quote from a community contributor praising the product and adding that no one else in the landscape is close. It is attributed and it is favourable, which is fine to note as a fact about the document rather than as evidence about the software.
Editorial conclusion
Skales suits someone who wants a single click-to-run desktop agent across Windows, macOS, Linux and two phone platforms, is willing to supply a key from one of fifteen providers or run locally, and does not need to read the code. It does not suit anyone whose decision depends on auditing the implementation, because the source was deliberately withdrawn and the product is closed, and the page is candid about why. Before adopting it, treat the README as product marketing rather than technical documentation, check which terms your own version was supplied under because the licence changed partway through the 12.9 series and the page names a boundary at 12.9.27 without covering the two releases after it, and read the security scope document before reporting anything. The RAM and first-task figures are one vendor's own claims without a stated method.
Frequently asked questions
Is the Skales source code open?
No. The page states that Skales is proprietary and stays proprietary, and that the product is the signed application downloaded from skales.app. A v7 source snapshot stood in this repository until release 12.9.30 and was removed, because it had 138 TypeScript files against 984 in the built tree and 70 API routes against 225.
What licence is Skales released under?
With release 12.9.30 the project moved from the Business Source Licence 1.1 to its own End User Licence Agreement, stating that private use, study and teaching stay free of charge and that commercial use needed a licence under the previous terms too. Releases up to 12.9.27 keep the terms they were supplied under, and the full text ships beside the app in English and German.
What platforms does the Skales desktop app run on?
Windows, macOS and Linux natively, with separate download targets for macOS on Apple Silicon and macOS on Intel, plus Android and iOS apps. The repository carries three install guides, one each for Windows, macOS and Linux, and the app is installed by double-clicking a downloaded package.
Does the Skales desktop agent need an API key?
Not to start. A built-in trial needs no API key, and after that you can bring your own key from more than fifteen providers or run fully offline with Ollama. The page also describes a migration importer, reachable from Settings, for people switching from other named agent tools or a chat product.
How much RAM does the Skales agent use?
The page claims roughly 300 MB for the agent, against 1.5 to 3 GB and above for a typical agent, and 30 seconds to a first task against hours to days. Neither figure is given with a measurement method, a build number or a platform, and both appear in a marketing comparison table rather than in a benchmark section.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/skalesapp-skales)Star history chart for your README
[](https://hysenlabs.com/projects/skalesapp-skales)Was this useful?