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.
NeoAgent supports macOS and Linux hosts. You need Node.js 20 or newer; the installer handles the rest of the application setup and attempts to install QEMU for the isolated browser and terminal runtime.
npm install -g neoagent
neoagent installOpen http://localhost:3333, create the first account, and configure a model.
Local models can run through Ollama; hosted providers
can be configured in the application.
Read the installation guide before exposing the service to a network.
- It is a service, not just a chat window. NeoAgent keeps tasks, integrations, memory, connected devices, and messaging channels available between sessions.
- Memory is stored as structured local data. Durable facts are separated from conversation history, scoped by user and agent, and updated when newer information replaces older information. NeoAgent can also index supported integration content with source references. See How memory works.
- It operates real devices. The agent can use an isolated browser and shell, control an Android device or emulator over ADB, or work through a paired Chrome extension and desktop companion.
- Automation can start without a message. Tasks can run on a schedule or from supported Gmail, Outlook, Slack, Teams, personal WhatsApp, and weather events. Android notifications can also start an agent run.
- Agents and users have separate state. Specialist agents can have their own memory, settings, tools, account assignments, conversations, and task history. Multi-user deployments include administrative account controls and optional email confirmation.
- The same server has several interfaces. NeoAgent includes web, Android, desktop, and Android launcher clients, messaging bridges, a Chrome extension, and firmware for a supported ESP32-S3 wearable.
| Operator interface | Memory | Remote devices |
|---|---|---|
 |
 |
 |
NeoAgent is aimed at people who want a UI-first, self-hosted agent with structured local memory, multi-user administration, automation, and direct Android control in one installation.
OpenClaw has a broader gateway and node ecosystem. Hermes is oriented around a terminal-first agent workflow. NeoAgent is a different tradeoff rather than a blanket replacement for either project.
The comparison page records the concrete differences and links to the source material used.
NeoAgent is beta software maintained primarily by one person. Expect breaking changes and rough edges. Review the security boundaries before connecting sensitive accounts or giving the agent access to a personal workstation.
Start with the documentation. Use GitHub Discussions for questions and GitHub Issues for reproducible bugs. Security reports belong in the process described by SECURITY.md.