RegentOS
The base autonomous agent runtime and mission system. It can receive goals, plan work, use tools, pause for approvals, resume, and report back.
Portable autonomous agent OS
RegentOS is the operating system for autonomous work.
RegentOS receives goals, clarifies what matters, plans the work, uses tools, delegates to specialized sub-agents, pauses for approval when needed, resumes, and reports back.
Runs as a base agent RegentOS can operate without a profile installed, then become more specialized over time.
Installs trusted modules Profiles and sub-agents are managed as first-party modules that extend the same operating system.
Autonomous, not unrestricted Side-effecting actions pass through deterministic policy gates, approvals, and audit logs.
What is RegentOS?
A base autonomous system that can be customized without rebuilding the whole agent.
RegentOS is not another chatbot or a single workflow script. It is a portable mission system for real-world work: a base agent runtime that can run on its own, install profiles, delegate to sub-agents, and operate inside configured safety boundaries.
Profiles
Installable behavior packages that shape RegentOS around workflows, tone, default tools, autonomy defaults, and domain context.
Sub-agents
Delegated specialists that add focused capabilities through Regent-controlled handoffs, tool access, policy gates, and reporting.
Installable Profiles
Profiles make RegentOS domain-specific.
Profiles modify Regent's focus, workflows, tone, default tools, autonomy defaults, and domain context.
Install the Concierge profile to turn RegentOS toward travel-agent workflows: trip intake, vendor follow-up, quote prep, itinerary support, payment and deadline reminders, and workspace organization.
Profiles are modular, first-party, and managed by RegentWorks as trusted folders and modules.
Delegated Specialists
Sub-agents extend RegentOS without operating outside it.
RegentOS controls the mission, handoffs, policies, tools, and reporting. Sub-agents add focused capability, but they do not become separate uncontrolled actors.
Regent-controlled handoffs
RegentOS decides when to delegate, what context to share, which tools are available, and how the result returns to the mission.
Courier for Gmail triage
Courier reads, summarizes, classifies, labels, drafts, detects follow-ups, and prepares sends behind approval or policy gates.
Bounded capability
Each sub-agent runs under RegentOS permissions, autonomy limits, evaluation criteria, and audit requirements.
Autonomy With Control
Built for bounded autonomy, not unrestricted AI behavior.
Every side-effecting action passes through a tool broker before it reaches Gmail, Drive, Calendar, WhatsApp, or future tools.
Tool policies define what is allowed at each autonomy level, including approval_required, limited_autopilot, and full_autonomy.
Full autonomy means policy-permitted actions under configured limits, allowlists, idempotency keys, approval rules, and audit logging.
Sensitive actions can require signed approvals, and every tool result remains auditable.
Portable Architecture
RegentOS is designed as portable source modules.
The current hosted layer runs on isolated customer environments with queues, databases, secrets, logs, and storage. The product idea stays portable: a core OS, installable profiles, and installable sub-agents.
regent_os/
The base runtime, mission loop, task state, tool routing, autonomy settings, and reporting surface.
profiles/
Installable behavior packages such as Concierge that shape RegentOS for a domain or operator.
subagents/
Installable specialists such as Courier that add delegated capabilities under RegentOS control.
Start Here
Build your autonomous operating system.
Start with RegentOS, then install the profiles and sub-agents your work requires. Concierge and Courier are the first trusted modules for Phase 1.
Start with RegentOS