NeoAgent
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.
## ๐ Install
**Desktop app** โ installs and starts everything on macOS, Windows, and Linux.
No terminal, Node.js, npm, Git, or Docker needed. **Quickstart** picks safe
defaults; **Full setup** adds providers, integrations, voice, and tools.
**Standalone CLI** โ in the same releases, with its own bundled Node runtime:
```bash
neoagent
```
**npm** โ if you already have Node.js 20+:
```bash
npm install -g neoagent
neoagent setup --quick
```
Good to know:
- 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](docs/getting-started.md) before exposing the service to a network.
## โจ What makes it different
- **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](docs/memory.md).
- **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](docs/billing.md).
- **Many interfaces, one server.** Web, Android, desktop, and launcher clients, messaging bridges, and ESP32-S3 wearable firmware.
## ๐ฅ๏ธ Interfaces
| Operator interface | Memory | Remote devices |
| --- | --- | --- |
|  |  |  |
## ๐ NeoAgent, OpenClaw, and Hermes
| 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](docs/migration.md) skills, memory, and API keys
from both. The [comparison page](docs/why-neoagent.md) records the concrete
differences with sources.
## ๐งช Project status
Beta software, maintained primarily by one person โ expect breaking changes
and rough edges. Review the
[security boundaries](docs/security-boundaries.md) before connecting sensitive
accounts.
- ๐ [Documentation](https://neolabs-systems.github.io/NeoAgent/docs/)
- ๐ฌ [Discussions](https://github.com/NeoLabs-Systems/NeoAgent/discussions) for questions
- ๐ [Issues](https://github.com/NeoLabs-Systems/NeoAgent/issues) for reproducible bugs
- ๐ [SECURITY.md](SECURITY.md) for vulnerability reports
## License
[AGPL-3.0-only](LICENSE) โ the [licensing decision](docs/licensing.md)
explains why.
*Made with โค๏ธ by [Neo](https://github.com/neooriginal) ยท [NeoLabs Systems](https://github.com/NeoLabs-Systems)*