NeoAgent separates two concepts:
The main agent is created automatically. Additional agents are managed in the operator interface and can be used as specialists.
Each agent has its own conversations, memory, model settings, integrations, messaging assignments, tasks, and run history. This separation lets one user maintain, for example, a personal agent and a work agent without merging their context.
Agents can also be marked for orchestrator use. An orchestrator can delegate work to other agents; a normal specialist is intended to complete its assigned run directly.
Self-hosted installations can support more than one account. Administrative controls include account management, provider configuration, logs, and runtime updates.
Optional SMTP configuration enables:
See Configuration for the server variables.
Application data is scoped by user and, where applicable, agent. The default browser and terminal runtime is created per user. Official integration credentials remain server-side and are assigned to a particular user and agent.
This is application and runtime isolation, not a promise that every capability runs inside a VM. Android commands run through ADB on the NeoAgent host, and a paired desktop or Chrome profile grants access to that paired machine. Read Security boundaries before hosting untrusted users.