Elitza
A desktop setup, launcher, diagnostics, and repair layer that makes a local personal AI agent easier to install and operate. Powered by OpenClaw under the hood.
What Elitza Is
Elitza is the user-facing layer around a local personal agent. OpenClaw provides the agent engine. Elitza focuses on the parts that normal users should not have to fight: setup, provider configuration, native channel guidance, gateway diagnostics, profile generation, backups, and redacted diagnostics export.
The product thesis is simple: a personal AI agent should feel like a reliable desktop utility, not a weekend of terminal archaeology. Elitza keeps the installation path calm, visible, and repairable.
Core Product Layers
🧭 Setup Wizard
Guides the user through profile creation, provider setup, engine installation, local gateway checks, and final readiness without pretending unfinished steps are complete.
🔐 Provider Setup
Helps users configure their own model provider keys safely. Secrets are written to local OpenClaw configuration paths and are never displayed back in the interface.
⚙️ OpenClaw Engine Control
Installs and launches the local OpenClaw runtime in user space, then checks whether the gateway, profile files, and command-line tools are reachable.
🛡️ Diagnostics and Repair
Surfaces gateway, service, provider, and workspace problems in plain language. Advanced repair paths explain exactly what will happen before anything sensitive runs.
💬 Native Channel Guidance
Guides Telegram and WhatsApp setup through OpenClaw-native channels instead of rebuilding fragile custom messaging protocols.
Technical Architecture
System Design
Installer Architecture
- Engine: OpenClaw, installed locally and credited transparently.
- Default install mode: user-space install under
~/.openclaw, no sudo by default. - Gateway: local loopback service on a high port, with diagnostics that do not fake success.
- Profiles: local agent profile files generated from user preferences and copied into the resolved OpenClaw workspace.
- Packaging path: Linux/source beta first, Windows installer next, signed production installers later.
Why Elitza Exists
Power users can tolerate broken setup instructions, mystery config files, and CLI repair rituals. Most people cannot. That is the gap Elitza targets: the trust layer between a powerful local agent engine and a user who just wants their computer to become more capable.
Elitza does not try to hide OpenClaw. It makes OpenClaw approachable by wrapping the operational surface area: installation, credentials, profile files, native channel setup, diagnostics, and recovery.
Design Principles
- No fake green: if a probe fails, the UI says exactly what is known and what is unverified.
- No silent escalation: Elitza should not require root access for the normal install path.
- No secret leakage: provider keys are handled locally and never rendered back to the user.
- No protocol cosplay: native Telegram and WhatsApp setup should use OpenClaw channels instead of brittle custom clones.
Current Beta Scope
The current beta candidate is focused on making the setup path testable and honest: system check, OpenClaw install detection, profile source generation, provider setup, gateway diagnostics, diagnostics export, and release readiness checks.
Production blockers remain explicit: signed installers, AppImage or native installers, Windows QA, production auto-update, restore flows, and provider probe verification across OpenClaw versions.
Real Capabilities
Elitza currently focuses on the installer and control surface around the local agent:
- OpenClaw setup: detects local installs and guides user-space installation where possible.
- Agent profile generation: creates local profile source files for identity, preferences, boundaries, tools, and routines.
- Provider setup: writes provider configuration locally while avoiding secret exposure in the UI.
- Gateway diagnostics: checks whether the local gateway appears active and explains blocked probes without pretending they passed.
- Redacted export: creates bounded diagnostic bundles that can be shared without dumping private keys.
The long-term goal is bigger than setup: every serious operator should have a personal AI agent that follows them across contexts and massively increases what they can execute alone.
Follow the Beta
Elitza is moving from local beta candidate toward packaged installers and a clearer public onboarding path.
Visit Elitza →