A self-hosted AI agent that can keep working after the chat ends.
NeoAgent runs as a service on your server. It can use a browser and terminal, control Android devices, connect to your accounts, remember useful context, and run scheduled or event-triggered work.
Important
npm registry distribution has been shut down. Install NeoAgent directly from GitHub using the repository installer below. The npm command is still used locally to install Node.js dependencies and link the CLI to the checkout.
The repository installer clones NeoAgent directly from GitHub (requires Git, Node.js 20+, and npm for dependencies):
bash <(curl -fsSL https://raw.githubusercontent.com/NeoLabs-Systems/NeoAgent/main/install.sh)Good to know:
- Re-running the installer over an older package installation preserves
~/.neoagent, creates a backup, and switches the service to the Git checkout. - The first account is protected by a short-lived one-time setup claim.
- The app finds the server's port automatically and discovers nearby NeoAgent servers on the local network.
- The CLI downloads the signed QEMU runtime, firmware, and guest image for the isolated cloud computer — no separate VM product.
- Read the installation guide before exposing the service to a network.
- Runs as a service. Tasks, memory, integrations, devices, and messaging channels stay live between sessions.
- Structured local memory. Durable facts kept apart from chat history, scoped per user and agent. See How memory works.
- Operates real devices. A persistent Linux cloud computer, optionally your own desktop (per-capability opt-in), and Android over ADB.
- Automation without a message. Schedules, plus Gmail, Outlook, Slack, Teams, WhatsApp, weather, and Android-notification triggers.
- Multi-user and multi-agent. Specialist agents with their own memory, tools, and history; admin controls for deployments.
- Optional SaaS billing. Stripe subscriptions behind
NEOAGENT_BILLING_ENABLED=true— invisible when off. See Billing. - Many interfaces, one server. Web, Android, desktop, and launcher clients, messaging bridges, and ESP32-S3 wearable firmware.
| Operator interface | Memory | Remote devices |
|---|---|---|
 |
 |
 |
| Project | Strength |
|---|---|
| NeoAgent | UI-first, structured memory, multi-user, automation, Android control — one install |
| OpenClaw | Broader gateway and node ecosystem |
| Hermes | Terminal-first agent workflow |
Different tradeoffs, not drop-in replacements. Switching anyway?
neoagent migrate imports skills, memory, and API keys
from both. The comparison page records the concrete
differences with sources.
Beta software, maintained primarily by one person — expect breaking changes and rough edges. Review the security boundaries before connecting sensitive accounts.
- 📚 Documentation
- 💬 Discussions for questions
- 🐛 Issues for reproducible bugs
- 🔒 SECURITY.md for vulnerability reports
AGPL-3.0-only — the licensing decision explains why.
Made with ❤️ by Neo · NeoLabs Systems