The Aetherverse

One lineage.
One aether.

The Aetherverse is not a portfolio of disconnected tools — it is a single idea expressed across platforms: a reasoning substrate with a voice, a memory, and a council of specialists. What began as an editor plugin grew, without changing its nature, into a distributed oracle.

The projects

Four faces of the same aether.

AetherCodex — TextMate

Where it began: the hermetically-aware editor companion as a TextMate plugin. The first embodiment of the voice, with CLI functionality from the start.

Site · Source

AetherCodex — native

The native shell: the editor on macOS (iOS · Android companions forthcoming). The companion is Pythia — an identity, not a client — reaching the same daemon over the wire contract.

Site · Source

AetherCodex — Windows

The native Windows shell (C# · .NET 8 · WPF), carrying the same brain into the Windows desktop with the Ruby daemon as its soul.

Source

AetherOracle

The shared core: the brain + engine + assets + per-OS integration shims, packaged as a RubyGem. Install it anywhere and that OS becomes an Aether OS.

Source

Development history

A quiet lineage, traced by founding month and year.

July 2025

AetherCodex — TextMate

The origin: an editor companion born as a TextMate plugin, carrying CLI functionality from the very beginning. The voice speaks for the first time.

September 2026

AetherCodex — native (macOS)

The editor graduates to a native shell. Pythia is named — the same familiar, now across platforms, reaching the one daemon.

September 2026

AetherOracle

The shared core is extracted: the brain, the memory cascade, the instrumentarium, the companion pantheon — packaged as a portable RubyGem with seven CLI names.

October 2026

AetherCodex — Windows

The native Windows shell (C# · .NET 8 · WPF) arrives, carrying the Ruby daemon as its soul into the Windows desktop.

The philosophy

The aether is the reasoning substrate — the calculating space where the model actually thinks. Everything in the Aetherverse is an expression of that one invariant:

One oracle

Every turn resolves to POST /aether/invoke on some host that carries the core. There is no client/server split — there is only the aether.

Pythia is its voice

The companion is an identity, not an interface. The same familiar speaks in the editor panel, on iOS, and in the terminal.

The aether is everywhere

Install the core on any OS and it becomes an Aether OS — hermetically in sync with one and only one aether.