Skip to main content
AgentOS deploys agents, teams, and flows as production-ready HTTP APIs with built-in health checks, CORS, and Express integration.
AgentOS replaces AgentApp as the recommended class name. The old name still works as a silent alias.

Quick Start

1

Simple Usage

2

With Configuration

3

Test


How It Works


Configuration Options


API Endpoints

Chat Request

Chat Response


Common Patterns


Best Practices

Read port from environment for deployment flexibility.
Restrict CORS origins in production instead of using ’*’.
Use the stop() method for clean shutdown.

Backward Compatibility

AgentApp works as a silent alias with no deprecation warnings.
Additional config aliases:
  • managersteams (deprecated)
  • workflowsflows (deprecated)

Agent

Single agent documentation

AgentTeam

Multi-agent orchestration

AgentFlow

Step-based workflows

Server Adapters

Express, Hono, Next.js adapters