Elidia Agent ☤

The self-improving AI agent built by AiUtils. It's the only agent with a built-in learning loop — it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions. Run it on a $5 VPS, a GPU cluster, or serverless infrastructure that costs nearly nothing when idle. It's not tied to your laptop — talk to it from Telegram while it works on a cloud VM.

Use any model you want — Elidia Portal, OpenRouter (200+ models), NovitaAI (AI-native cloud for Model API, Agent Sandbox, and GPU Cloud), NVIDIA NIM (Nemotron), Xiaomi MiMo, z.ai/GLM, Kimi/Moonshot, MiniMax, Hugging Face, OpenAI, or your own endpoint. Switch with elidia model — no code changes, no lock-in.

Quick Install

Linux, macOS, WSL2, Termux

curl -fsSL https://raw.githubusercontent.com/Elidia-Technology/elidia-agent/main/scripts/install.sh | bash

Windows (native, PowerShell)

Heads up: Native Windows runs Elidia without WSL — CLI, gateway, TUI, and tools all work natively. If you'd rather use WSL2, the Linux/macOS one-liner above works there too. Found a bug? Please file issues.

Run this in PowerShell:

iex (irm https://raw.githubusercontent.com/Elidia-Technology/elidia-agent/main/scripts/install.ps1)

The installer handles everything: uv, Python 3.11, Node.js, ripgrep, ffmpeg, and a portable Git Bash (MinGit, unpacked to %LOCALAPPDATA%\elidia\git — no admin required, completely isolated from any system Git install). Elidia uses this bundled Git Bash to run shell commands.

If you already have Git installed, the installer detects it and uses that instead. Otherwise a ~45MB MinGit download is all you need — it won't touch or interfere with any system Git.

Android / Termux: The tested manual path is documented in the Termux guide. On Termux, Elidia installs a curated .[termux] extra because the full .[all] extra currently pulls Android-incompatible voice dependencies.

Windows: Native Windows is fully supported — the PowerShell one-liner above installs everything. If you'd rather use WSL2, the Linux command works there too. Native Windows install lives under %LOCALAPPDATA%\elidia; WSL2 installs under ~/.elidia as on Linux. The only Elidia feature that currently needs WSL2 specifically is the browser-based dashboard chat pane (it uses a POSIX PTY — classic CLI and gateway both run natively).

After installation:

source ~/.bashrc    # reload shell (or: source ~/.zshrc)
elidia              # start chatting!

Getting Started

elidia              # Interactive CLI — start a conversation
elidia model        # Choose your LLM provider and model
elidia tools        # Configure which tools are enabled
elidia config set   # Set individual config values
elidia gateway      # Start the messaging gateway (Telegram, Discord, etc.)
elidia setup        # Run the full setup wizard (configures everything at once)
elidia claw migrate # Migrate from OpenClaw (if coming from OpenClaw)
elidia update       # Update to the latest version
elidia doctor       # Diagnose any issues

📖 Full documentation →

Skip the API-key collection — Elidia Portal

Elidia works with whatever provider you want — that's not changing. But if you'd rather not collect five separate API keys for the model, web search, image generation, TTS, and a cloud browser, Elidia Portal covers all of them under one subscription:

• 300+ models — pick any of them with /model <name>
• Tool Gateway — web search (Firecrawl), image generation (FAL), text-to-speech (OpenAI), cloud browser (Browser Use), all routed through your sub. No extra accounts.

One command from a fresh install:

elidia setup --portal

That logs you in via OAuth, sets Elidia as your provider, and turns on the Tool Gateway. Check what's wired up any time with elidia portal info. Full details on the Tool Gateway docs page.

You can still bring your own keys per-tool whenever you want — the gateway is per-backend, not all-or-nothing.

CLI vs Messaging Quick Reference

Elidia has two entry points: start the terminal UI with elidia, or run the gateway and talk to it from Telegram, Discord, Slack, WhatsApp, Signal, or Email. Once you're in a conversation, many slash commands are shared across both interfaces.

For the full command lists, see the CLI guide and the Messaging Gateway guide.

Documentation

All documentation lives at aiutils.io/docs:

Migrating from OpenClaw

If you're coming from OpenClaw, Elidia can automatically import your settings, memories, skills, and API keys.

During first-time setup: The setup wizard (elidia setup) automatically detects ~/.openclaw and offers to migrate before configuration begins.

Anytime after install:

elidia claw migrate              # Interactive migration (full preset)
elidia claw migrate --dry-run    # Preview what would be migrated
elidia claw migrate --preset user-data   # Migrate without secrets
elidia claw migrate --overwrite  # Overwrite existing conflicts

What gets imported:

• SOUL.md — persona file
• Memories — MEMORY.md and USER.md entries
• Skills — user-created skills → ~/.elidia/skills/openclaw-imports/
• Command allowlist — approval patterns
• Messaging settings — platform configs, allowed users, working directory
• API keys — allowlisted secrets (Telegram, OpenRouter, OpenAI, Anthropic, ElevenLabs)
• TTS assets — workspace audio files
• Workspace instructions — AGENTS.md (with --workspace-target)

See elidia claw migrate --help for all options, or use the openclaw-migration skill for an interactive agent-guided migration with dry-run previews.

Contributing

We welcome contributions! See the Contributing Guide for development setup, code style, and PR process.

Quick start for contributors — clone and go with setup-elidia.sh:

git clone https://github.com/Elidia-Technology/elidia-agent.git
cd elidia-agent
./setup-elidia.sh     # installs uv, creates venv, installs .[all], symlinks ~/.local/bin/elidia
./elidia              # auto-detects the venv, no need to `source` first

Manual path (equivalent to the above):

curl -LsSf https://astral.sh/uv/install.sh | sh
uv venv .venv --python 3.11
source .venv/bin/activate
uv pip install -e ".[all,dev]"
scripts/run_tests.sh

Community

• 💬 Discord
• 📚 Skills Hub
• 🐛 Issues
• 🔌 computer-use-linux — Linux desktop-control MCP server for Elidia and other MCP hosts, with AT-SPI accessibility trees, Wayland/X11 input, screenshots, and compositor window targeting.
• 🔌 ElidiaClaw — Community WeChat bridge: Run Elidia Agent and OpenClaw on the same WeChat account.

License

MIT — see LICENSE.

Built by AiUtils.