Active development — unstable builds. Expect breaking changes. pre-alpha
pre-alpha · vaelora systems

Vaelora Systems

Æ T H E R   F O R G E

A fully local AI environment that grows with you.

Begin Forging
Live Demo

Command. Execute. Evolve.

Type any command or pick a preset. Watch Æther Forge reason, build, and commit.

aether-forge — forge@local
forge@local:~$ _
Presets
forge@local:~$
Status Idle
· Waiting for input...

The forge, alive.

Real-time capability monitoring. Every tool tracked. Every change versioned.

Active Tools
loading...
Git Log
loading...
Documentation

How it works.

Installation

Æther Forge runs entirely on your local machine. No cloud account, no telemetry, no subscription. You'll need Python 3.11+, a local LLM runtime (Ollama recommended), and optionally a microphone for voice mode.

The installer handles model pulling, tool registry init, and Git repo setup automatically.

# requires: python 3.11+, git, ollama git clone https://github.com/cammythekitty/aether-forge cd aether-forge && ./install.sh

⚠ Pre-alpha. Install script may require manual steps on non-Arch systems.

Architecture

Æther Forge operates as a closed loop: listen → reason → act → version. Every tool it writes is stored, sandboxed, tested, and registered. The forge grows smarter with every command you give it.

Voice / Text Input
Local LLM (Ollama)
Tool Builder
Sandbox
Test
Git Commit
Tool Registry (persistent)

System Prompt

The system prompt is Æther Forge's operating contract — what it can access, how it reasons, and how it documents changes. It's loaded fresh each session and ships with sane defaults.

Edit it to restrict capabilities to specific directories, extend it to give the forge awareness of new tools, or scope it to a particular project.

# default location ~/.aetherforge/system_prompt.md # per-project override ./aether.md ← auto-detected if present

Self-Upgrade

When Æther Forge builds a new tool, it writes source, runs a sandboxed test, and on success commits the file to your local Git repo with a descriptive message. Failed tools are logged but never registered.

Nothing broken makes it into the registry. The diff is yours — inspectable, revertable, owned.

# inspect the forge log git -C ~/.aetherforge/tools log --oneline # roll back a bad tool git -C ~/.aetherforge/tools revert HEAD

Platform Notes

Full support on Linux. Windows via WSL2 works for most tool types — native Win32 execution is in progress. macOS voice input works; system-level tool execution has known limitations on Apple Silicon.

Linux (Arch) ✓ supported but not finished Windows WSL2 x Not supported macOS (Apple Silicon) x Not supported Windows native x Not supported

Tested primarily on Arch Linux. File issues for anything that breaks elsewhere.

Download

Start forging.

One command. Fully local. No cloud, no account, no data leaves your machine.

# Linux — tested on Arch, Debian, Fedora git clone https://github.com/cammythekitty/aether-forge cd aether-forge && ./install.sh
Clone on GitHub Back to home