Model or dataset
Zhou-Shilin/Aether avatar
Zhou-Shilin/Aether

Aether: a Kotlin agent host with a built-in Alpine VM and a zip extension importer

Aether — a stunning, localized, general-purpose AI agent for Android, iOS and Mac.

784 stars65 forksKotlinGPL-3.0

At a glance

What is it?
Aether wraps the Pi agent runtime for Android, iOS and macOS, ships an Alpine Linux environment inside the app, and takes extensions as zip packages. The extension API, the Android file bridge and the Shizuku path are documented in detail; the install story is not.
Who is it for?
Judgment: Aether reads as an extension host first and a documented product second. The zip import path, the proot backed Alpine bridge and the three adapted extensions are the parts with real detail, and those are the parts worth reading before installing anything.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 14 days ago.
What is it written in?
Mainly Kotlin, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 20, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Zhou-Shilin/Aether784 ★ · +186
Star history
Repository2026-09-112026-11-20
Zhou-Shilin/Aether598784

186 Stars in the last 70 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Pi extensions load as zip packages, and the API they target is documented off repo

Aether loads standard Pi Extensions, the format published at github.com/earendil-works/pi, and adapts extensions written for terminal UIs to a phone touchscreen. The bridging layer is its own Extension API, and it names five injection points: custom settings cards, interactive composer widgets, overlay transcript viewers, prompt interceptors, and semantic tool titles. Installing one is a zip import through Settings, then Extensions, then Import extension, so no package manager sits in the path. The development guide is where the detail stops. It lives at aether.baimoqilin.com/docs/extensions/overview.md, an address on a separate documentation site, even though the source tree carries its own docs/ directory. Nothing says whether the two hold the same content or whether docs/ is where the website is built from. An extension author therefore ends up reading a web page to write code against a checkout they already have on disk.

Three extensions carry an asterisk that means the Aether team adapted them

The extension table lists Pi Web Access, Pi MCP Adapter, and Pi Subagents, and each name carries an asterisk. The footnote ties that asterisk to a single fact: they are official extensions adapted by the Aether team, not third party submissions. A fourth row appears through a pull request. All three live in separate repositories under the AetherExtensions organisation, so the host and its extensions version independently of each other. Pi MCP Adapter turns the app into a Model Context Protocol gateway over Stdio, Streamable HTTP, SSE, and Unix domain sockets, with lazy loading, tool discovery that saves tokens, interactive OAuth authentication, and a visual server management GUI. Pi Subagents adds autonomous sub agents with parallel background execution, steering while a run is still in flight, live widgets above the composer, an overlay transcript viewer, and @handle mentions typed into the prompt.

Android's file picker only sees the Alpine VM after it is initialised

The app carries an automatically installed Alpine Linux environment for running shell commands and tools, backed by proot. On Android that environment is surfaced through the system file managers, and the order of operations matters. You initialise Alpine first, then choose Aether (Alpine) in the Files app or in the SAF document picker sidebar. From there you browse the environment and /workspace, and create, edit, rename, delete, or copy files between Alpine and device storage. Writes land directly on the files proot uses rather than on a copy that gets merged later, so a mistake in the picker is a mistake in the running environment. System mounts such as /dev, /proc, and /sys are held out of the view. What stays unstated is the other half: no Android version requirement for the sidebar entry, no behaviour for a file both sides edit, and no stated equivalent on iOS or macOS.

Shizuku and Termux are the only named route to the device, and only on Android

Device level control comes from two optional integrations, Shizuku and Termux, and the line carrying them is marked Android only. That is the whole host control surface as described: a route into an existing Android privilege model rather than something the app implements on its own. Nothing says which of the two carries the permission side and which carries the shell and package side, so anyone planning automation has to settle that before assuming a capability exists. The asymmetry matters more than the ambiguity. All three platforms get a Linux environment through proot, but only one gets a documented path to the device itself, which leaves the iOS and macOS builds differing from the Android one in a way the project has not explained.

No install command anywhere, only a docs link and two store badges

The Quick Start section is a single link to aether.baimoqilin.com/docs/quickstart. There is no command to copy, no package name, no clone step, and no build instruction anywhere in the README. Distribution runs through two badges instead: an App Store listing at apps.apple.com/app/id6793855391, and the project's GitHub releases page. The macOS artefact is not named separately in that pair, so which download serves a desktop user is left to the releases listing. For an app shipped through stores this is ordinary practice, and it also means anyone evaluating the project has to leave the repository to learn how the thing starts, with nothing in the tree pinning a version to the documentation it links.

The tree carries two example extensions the README never names

The Kotlin build sits in a tree broader than the README describes: app/, iosApp/, shared/, packages/, pi-bridge/, extensions/, public/, scripts/, docs/, and third_party/, wired together by settings.gradle.kts, build.gradle.kts, gradle.properties, and a Gradle wrapper in both gradlew and gradlew.bat form. Two example projects ship as directories, examples/aether-extension/ and examples/global-skills-mod/, and neither name appears in the README. The second one matters: global skills mod points at a capability layer that the Core Features list never describes. Whether these directories are the supported starting point for new work or leftovers from an earlier layout is not stated anywhere, and the extension guide that would settle it sits on the website rather than in the checkout.

GPL-3.0 alongside a notices file, a submodules file and third_party

The license is GPL-3.0, and the same tree also holds THIRD_PARTY_NOTICES.md, a third_party/ directory, and .gitmodules. Three separate places record code that is not the project's own, and the README connects none of them to the main license or to each other. A submodules file also means the checkout is not self contained: some directories arrive as references rather than vendored copies, so anyone auditing what actually ships has to resolve them first. On top of that the project states it is being built sporadically by a 15 year old student in spare time, with donation links on Ko-fi and Aifidian, which is the honest context for how quickly any of this changes between one tag and the next.

Two releases two days apart in August, then nothing since 4 September

Tagged builds arrived as 2.1.4 on 21 August 2026, 2.1.5 on 23 August 2026, and 2.1.6 on 4 September 2026, so the gap went from two days to twelve inside a single burst. Code was pushed on 1 October 2026, nearly a month after the newest tag, which means the tagged line is not the whole state of the project, but nothing has been tagged since. The counters sit at 713 stars, 54 forks, and 13 open issues. A single maintainer working in spare time produces exactly this shape, dense bursts on whatever was being built that month and quiet stretches afterwards. Which of those two patterns a given month lands in cannot be read off the release list, so anyone depending on a specific version should pin the tag rather than track the default branch.

Editorial conclusion

Judgment: Aether reads as an extension host first and a documented product second. The zip import path, the proot backed Alpine bridge and the three adapted extensions are the parts with real detail, and those are the parts worth reading before installing anything. The empty spots are the install instructions, the Shizuku and Termux split, and the two example directories the README never names. Check the docs site against the tag you build, and read THIRD_PARTY_NOTICES.md, .gitmodules and third_party/ together before assuming a checkout tells you what ships in the binary.

Frequently asked questions

Which platforms does Aether run on, and what is it written in?

Android, iOS and macOS, with Kotlin as the primary language. The checkout carries app/, iosApp/, shared/ and packages/ directories, plus a Gradle wrapper in both gradlew and gradlew.bat form.

How do you install an extension in Aether?

As a zip package, through Settings, then Extensions, then Import extension. The app loads standard Pi Extensions and adds an Extension API for settings cards, composer widgets, overlay transcript viewers, prompt interceptors and semantic tool titles.

Does Aether ship a Linux environment?

Yes. An automatically installed Alpine Linux environment runs shell commands and tools out of the box, backed by proot. On Android, Aether (Alpine) then appears in the system Files app and in the SAF document picker sidebar.

What license does Aether use?

GPL-3.0. The tree also holds THIRD_PARTY_NOTICES.md, a third_party/ directory and .gitmodules, none of which the README connects to the main license or to each other.

What does the Pi Web Access extension add to Aether?

Web lookup across more than 20 providers (OpenAI, Brave, Exa, Tavily, Perplexity, Gemini, SearXNG), GitHub repository cloning, PDF extraction, and video understanding, with native settings and transcript cards.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. README
  4. Releases
  5. Zhou-Shilin/Aether on GitHub
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/zhou-shilin-aether.svg)](https://hysenlabs.com/projects/zhou-shilin-aether)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/zhou-shilin-aether.svg)](https://hysenlabs.com/projects/zhou-shilin-aether)

Was this useful?