Aleph Documentation
Technical documentation for Aleph — a self-hosted polymorphic AI assistant built in Rust
"This is the first time in human history, a machine's soul has been given a body." — Ghost in the Shell
Aleph is a personal AI assistant built in Rust. It fuses a high-performance Gateway control plane with multi-channel messaging, memory governance, tool execution, and a federation of local/remote executor nodes — all in a single core — so AI agents can work across your platforms on your hardware, with end-to-end visibility.
Single-Core Multi-Terminal, Shell-Core Separation; Gateway Interoperability, Access Control.
One
aleph-servercore powers every interface — desktop app, CLI, TUI, Telegram, Discord, iMessage, and more. The native desktop shell is a thin container with zero business logic; all reasoning, tools, and state live in the core. Every terminal connects through the same authenticated WebSocket gateway, whether local or remote.
Key Features
- Multi-Provider AI — Claude, GPT, Gemini, Ollama with atomic-counter failover and an atomic regen marker;
session.usageis computed in-core from a single source of pricing - Multi-Channel — Telegram, Discord, iMessage, WebChat, and the desktop app share one authenticated gateway, inbound router, session model, memory, and tool ecosystem
- Session Mode (chat / work / code) — the third twin of
exec_tierandthink_level; statically partitions the tool presentation surface; switchable at runtime viasession_set_mode - Native Performance — 100% Rust core, no interpreted languages
- Shell-Core Separation — desktop shell is pure OS integration; the core runs standalone
- Remote Core + Self-Signed TLS — connect the desktop shell to a remote
aleph-serverover Tailnet/VPN; the SAN auto-discovers the host's non-loopback interface IPs - TOFU Certificate Trust — fingerprint + SAN approval, pinned locally, surfaced in-app from the Panel
- Cluster Federation — one center core orchestrates many machines (nodes) as execution arms; node keys are Unicode-normalized (CJK node names work)
- Three-Tier Security Model — fail-closed approval / sandbox / pairing, with
exec_tier, session mode, and a capability ledger - Loop-Graph Governance Layer — team node / independent-evidence auditor (
loop-auditor) / victory-claim watchers / objective ACLs - Extensible — type-safe built-in tools, capability-gated MCP discovery, plugins, Markdown skills, and custom tools share the scoped tool service and approval path
- Self-Hosted — run on your own hardware, full control
Architecture
Terminals
┌────────────────────────────────────────────────────────────┐
│ Desktop │ CLI │ Telegram │ Discord │ iMessage │ TUI │
│(Tauri v2)│ │ │ │ │ │
└────┬─────┴────┬─────┴────┬────┴────┬────┴────┬─────┴──┬────┘
│ │ │ │ │ │
│ WebSocket (JSON-RPC 2.0, optional wss://) │
│ │ │ │ │ │
┌────▼──────────▼──────────▼─────────▼─────────▼─────────▼───┐
│ Aleph Core (aleph-server) │
│ ┌─────────────┐ ┌──────────────┐ ┌─────────────────────┐ │
│ │ Gateway │ │ Harness │ │ Tool Registry │ │
│ │ (TLS/TOFU) │ │ (Think→Act) │ │ (builtin/MCP/plugin)│ │
│ └─────────────┘ └──────────────┘ └─────────────────────┘ │
│ ┌─────────────┐ ┌──────────────┐ ┌─────────────────────┐ │
│ │ Thinker │ │ Session │ │ Memory + Loop │ │
│ │ (PromptBuilder)│ │ Service │ │ Graph (governance) │ │
│ └─────────────┘ └──────────────┘ └─────────────────────┘ │
│ ┌─────────────┐ ┌──────────────┐ ┌─────────────────────┐ │
│ │ Approval / │ │ Extension │ │ Heartbeat / Cron │ │
│ │ Guardrails │ │ / Skill │ │ Schedulers │ │
│ └─────────────┘ └──────────────┘ └─────────────────────┘ │
└────────────────────────────────────────────────────────────┘
│
│ Authenticated execution dispatch
▼
Cluster Nodes (remote executors)Shell-Core Separation. The desktop app is a thin Tauri v2 shell — window, tray, notifications, auto-update, global hotkey. It contains no business logic and no business UI. All product UI lives in the Leptos Panel (served by the core at http://127.0.0.1:18790). All reasoning, tools, and state live in aleph-server. The shell can connect to a local core or a remote one (self-signed TLS with client-side TOFU pinning).
The Third Twin: Session Mode. chat / work / code is the third user-adjustable dimension alongside exec_tier (execution approval tier) and think_level (thinking budget). It statically partitions the tool presentation surface only (progressive-disclosure core set + deferred-tool tier); permissions remain controlled by exec_tier and the approval gate. Switchable from the Panel composer pill, from Settings → Policies, or via the session_set_mode tool.
Loop-Graph Governance Layer. loop_graph adds a governance topology on top of the harness: team nodes / audit ring / objective ACLs / victory-claim watchers / built-in loop-auditor agent. It gives the four single-loop failure modes (Goodhart, reference blindness, ring conflict, measurement decay) a topological answer.
Quick Start
# Build the core from source (Rust 1.95+)
git clone https://github.com/rootazero/Aleph.git
cd Aleph
cargo build --bin aleph-server --release
# Create ~/.aleph/config.toml, then start the core
./target/release/aleph-server doctor
./target/release/aleph-server startOpen http://127.0.0.1:18790/, or connect the CLI to ws://127.0.0.1:18790/ws.
Documentation Sections
Getting Started
Installation, first-time configuration, initial setup, and deployment
Philosophy
Design philosophy, five layers of emergence, agent thinking, and redlines R1–R10
Concepts
Agent runtime, messages, model providers, skills, workspaces, extensions, memory
Architecture
Five-layer request flow across interfaces, gateway, orchestrator, harness, storage, sessions, tools, and memory
Gateway RPC
WebSocket protocol, TLS + TOFU, authentication, method families, and registration status
Interfaces
Unified adapters for Telegram, Discord, iMessage, WebChat, and desktop clients
Tools & Extensions
Type-safe built-ins, scoped permissions, MCP discovery, browser automation, and custom tools
Security
Execution approval, fail-closed policies, TLS / TOFU, pairing, signed operation ledger
Automation
Persistent cron schedules, heartbeat probes, consent-aware hooks, and gateway events
Artifacts & Deliverables
Artifact store + Deliverable: 50 MB cap, 4 origins, Panel pin + open
Voice Conversation Runtime
Streaming ASR (Deepgram / WhisperLiveKit) + TTS provider fallback + Voice-as-Context
Loop / Goal / Strategy
Three independent subsystems: in-session loop / autonomous goal (objective gate) / team or naked-loop plan (composite-keyed)
CLI Reference
Commands, gateway management, agent interaction, session mode switching
Development
Building from source (Rust 1.95+), testing, contributing, and design patterns
API Reference
Rust API and JSON-RPC API documentation
Changelog
Rolling release notes from 26.7.21 through the 26.7.22+ update stream
Terminology
Standardized terminology for Aleph concepts (EN/ZH bilingual)
Philosophy
Aleph is built on a five-layer emergence architecture:
- Sea of Knowledge — AI's pre-training foundation
- Domain Classification — Organized expertise
- Atomic Skills — Know-what to Know-how
- Functional Modules — Composable capabilities
- Polymorphic Agents — Soul gains body
The goal is not just to build a tool, but to explore a path toward AGI — when intelligence gains the ability to act.
License
Apache 2.0