Skip to main content
GenosOS supports multiple AI agents running simultaneously. Every agent is fully isolated — its own memory, workspace files, channel routing, and identity — yet all agents share the same gateway and the same set of connected channels. You never need to edit config files to create or manage agents. Every operation happens through conversation.

​
What an agent is

An agent is a named, isolated execution context. Each one has:
  • UUID directory — the agent’s state lives at ~/.genosv1/agents/{8-char-hex}/. The directory name is an opaque UUID, not the agent’s display name. This decouples identity from the filesystem.
  • Main session key — agent:{agentId}:main is always present and is the default entry point for that agent.
  • Tool profile — inferred automatically from the agent’s name. Possible profiles: coding, messaging, minimal, full.
  • Smart model routing — the boost tool auto-escalates the agent to the advanced model (Opus, o3, or Gemini 3 Pro) when importance or urgency is detected. No manual switching required.
  • Encrypted workspace — workspace files (SOUL.md, IDENTITY.md, AGENTS.md, and others) are stored with NYXENC1 encryption. The agent never sees the encryption layer.

​
Creating an agent

Tell your assistant what you want: 
"Create an agent called Lumina for customer support"
GenosOS creates the agent, assigns a UUID directory, infers a tool profile from the name, and seeds the workspace. No follow-up configuration required. To create a specialized business agent from a template, say what your business does: 
"I want an assistant for my dental clinic"
The guided flow takes over from there. See agent templates for the full list of pre-built templates.

​
Switching between agents

Control UI: Use the sidebar. Agents are listed in the left panel; click to switch. The active session tree updates in real time. TUI: Press Ctrl+G to open the agent picker, or prefix a message with @agentname to route directly to that agent without switching your current session.

​
Renaming an agent

Renaming is a zero-filesystem operation. Only two things change: the display name in config and the session key alias. The UUID directory, all session transcripts, and all workspace files remain untouched. 
"Rename Lumina to Aria"

​
Agent isolation

Agents are isolated at every layer:
  • Memory — each agent has its own memory store. One agent cannot read another’s conversations.
  • Workspace — SOUL.md and IDENTITY.md are per-agent. Overwriting one agent’s identity does not affect others.
  • Tool access — each agent has its own tool profile and allow/deny list.
  • Channel routing — inbound messages are routed to the correct agent based on session key resolution.
Channels are gateway-level infrastructure, not per-agent. If WhatsApp is connected, all agents that are configured to receive WhatsApp messages can use it.

​
Explore further

Multi-agent system

How agents delegate to each other via A2A communication.

Agent templates

12 pre-built templates for business and operations use cases.

Skills

Local knowledge files that teach agents how to use external services.

Security

Encryption, audit log, and channel tool restrictions.